Services · Cloud

Cloud penetration testing: what your provider protects and what you control

A cloud penetration test is a controlled attack on your AWS, Azure or Google Cloud environment that looks for weaknesses in identities, permissions and service configuration that could expose your data.

What it is

What is cloud penetration testing?

“We are in the cloud, so the provider takes care of security.” That is only part of the picture. The provider protects its data centres, hardware and network. You still control who can access what, how services are configured and what is exposed to the internet. This is the shared responsibility model, described in similar terms by the major providers.

We therefore focus on the areas you control:

01

Identities and permissions

accounts and roles with excessive permissions, old access keys and missing multi-factor authentication (MFA).

02

Service configuration

storage or databases exposed to the internet, disabled logging and overly permissive network rules.

03

External exposure

administration interfaces, APIs and forgotten test environments.

04

Connections to your network

synchronised accounts and VPNs through which an attack could move between your cloud and internal systems (see infrastructure penetration testing).

Patrik Žák holds the CCPenX-AWS certification (Certified Cloud Pentesting eXpert – AWS). See our penetration testing overview for web application and infrastructure testing.

Why you need it

Why test your cloud environment?

Cloud configuration changes quickly, often under delivery pressure. A single incorrect permission can open a path to production data and go unnoticed because everyone assumes the provider is handling security.

Testing makes sense:

01

during or after a cloud migration;

02

when you run applications that handle customer data in the cloud;

03

when multiple accounts, subscriptions or projects make permissions difficult to track;

04

when you connect the cloud to your own network and Active Directory.

Our penetration testing overview covers the different types of test.

What you receive

What you receive

01

Executive summary

the state of your cloud environment and what it means for your business.

02

Technical report

findings with descriptions, evidence and specific fixes for your DevOps or IT team.

03

Attack paths

how smaller configuration weaknesses combine to provide access to data.

04

Severity assessment

CVSS scoring and an assessment of what an attacker could reach through each finding in your environment, establishing remediation priorities.

05

Optional retest

after remediation, we check that the findings have been resolved. The retest is priced separately, from 1 person-day for all findings.

How it works

How cloud penetration testing works

01

Scope

We agree which accounts, subscriptions or projects to test and what is excluded.

02

NDA and rules

We sign an NDA before every project, together with a contract and testing rules. Cloud providers have their own penetration testing rules, which the test must follow.

03

Testing

We start with read-only audit access to review the configuration. To validate what an attacker could reach, we agree elevated permissions or test accounts within the precise scope you approve.

04

Report and presentation

We review the findings with your technical team and management.

05

Retest

If requested, we check that the findings have been resolved after remediation.

The duration depends on the scope of your environment. We confirm the schedule in our proposal.

How it compares

Why automated configuration checks are not enough

Configuration checking tools are useful and make sense as an ongoing measure. They identify individual weaknesses, but do not establish how they fit together. During a penetration test, we combine weaknesses into attack paths and validate what they actually allow. Three medium-severity findings can together provide access to production data.

Cloud penetration testing FAQs

What is a cloud penetration test?

It is a controlled attack on your AWS, Azure or Google Cloud environment. We look for weaknesses in identities, permissions and service configuration and show you how to fix them.

What is the provider responsible for, and what are we responsible for?

The provider secures the cloud infrastructure: data centres, hardware and the network. You are responsible for what you run in the cloud, particularly identities, permissions, service configuration and data.

Which cloud platforms do you test?

AWS, Microsoft Azure and Google Cloud.

Do we need the cloud provider's approval before testing?

Under current AWS, Azure and Google Cloud policies, standard penetration testing of your own resources does not require prior approval, but each provider sets rules on what may be tested. We review them before testing and adapt the test accordingly.

What access do you need from us?

There are two stages. First, we review configuration with read-only audit access, for example AWS SecurityAudit and ViewOnlyAccess, Azure Reader and Security Reader with access to read Entra ID, or read-only roles in Google Cloud. We then validate what an attacker could reach using elevated permissions or test accounts. You approve the scope of both stages.

How long does cloud testing take?

It depends on scope and objectives. We will propose a schedule in our proposal after the initial conversation.

Is the retest included in the price?

No. The retest is priced separately, from 1 person-day for all findings.

What can we improve before the test?

Review accounts with the highest permissions and check that they need them. Enable multi-factor authentication for all human user accounts and replace old access keys with temporary credentials.

Services
Contact

Check whether your cloud configuration works as intended.

Tell us which cloud you use and what you run there. We will propose the scope of the test.

Request a test →