Penetration Testing/Cloud Penetration Testing
Cloud Penetration Testing

Cloud penetration testing that follows one key to your data

Hands-on testing of your AWS, Azure and Google Cloud environments: identities, exposed services, storage, containers and serverless. Every finding comes with a reproducible proof of concept and a fix your engineers can ship.

  • IAM privilege escalation and cross-account access
  • Exposed storage, databases and management interfaces
  • Kubernetes, containers and serverless functions
  • Configuration review against CIS Benchmarks
The credentials behind every engagement
CREST-accredited for penetration testingISO/IEC 27001 certifiedSOC 2 Type 2 attested
2026 CyberSecurity Breakthrough Awards winnerG2 High Performer, Fall 2026
Penetration Testing Solution of the Year2026 CyberSecurity Breakthrough Awards

Reviewed by Omair Manzoor, Founder & CEO, ioSENTRIX · Updated

Key terms: What is a cloud misconfiguration? · What is CSPM?

Trusted by security teams at
See it in action

One leaked key. Every customer bucket.

We start where an attacker would, follow the permissions as far as they go, then prove the fix with least privilege and a guardrail.

Swipe to see the full exhibit →

A scanner lists three items

A public bucket, a leaked key, a broad role: three findings. Chained, one path to your data.

Permissions are the perimeter

In the cloud, how far one credential goes depends on what its role is allowed to do.

Least privilege, then a guardrail

The role is narrowed to one bucket, a guardrail blocks the escalation, and the retest proves it.

Read this exhibit as text
  1. We agree one objective with you: production data, starting from the internet.
  2. Discovery: a public storage bucket lists an old backup file (MITRE ATT&CK T1619, cloud storage object discovery).
  3. Credential access: a valid access key is found inside the backup (T1552.001, credentials in files).
  4. Initial access: the key is used to act as the deploy role (T1078.004, cloud accounts). Its policy allows every storage and function action, plus assigning roles, on every resource.
  5. Privilege escalation: the deploy role passes an admin role to a new function (T1548.005, temporary elevated cloud access) and gains account admin.
  6. Collection: every customer upload in 14 buckets is read (T1530, data from cloud storage). The objective is reached on day 3.
  7. Report and walkthrough, day 8: revoke the key, narrow the deploy role to its one bucket with read and write only, and add an organization-wide guardrail that blocks granting admin roles.
  8. Retest, day 20: each step is retested from the agreed starting points. Public access is blocked, the key is revoked, the role reaches only its own bucket and the escalation is denied by the guardrail. The path to production data is closed.

Source: ioSENTRIX cloud testing methodology; MITRE ATT&CK Enterprise (IaaS); CIS Foundations Benchmarks for AWS, Azure and Google Cloud. Illustrative attack path at a fictional company, not client data.

The short answer

What is cloud penetration testing?

Cloud penetration testing is a hands-on security test of the applications, identities and services you run on a cloud platform such as AWS, Azure or Google Cloud. Testers try to reach data or gain control by abusing permissions, exposed services and misconfigurations, and prove each path with a reproducible proof of concept.

A cloud security assessment checks settings against a benchmark. A cloud pentest goes further: it chains a leaked key, an over-broad role and an exposed bucket into one attack path, which a configuration scanner reports as three separate items. We do both, so you get the checklist and the proof.

At ioSENTRIX, cloud penetration testing is carried out by hand by certified testers at a CREST-accredited firm, with findings mapped to the CIS Foundations Benchmarks for AWS, Azure and Google Cloud and the MITRE ATT&CK Cloud Matrix and a free retest of every fix.

You need a cloud pentest if

  • You run production workloads on AWS, Azure or Google Cloud
  • You use several accounts, subscriptions or projects with shared roles
  • A customer, auditor or SOC 2 report needs cloud test evidence
  • You moved to containers, Kubernetes or serverless since the last test
What we test

Four layers, tested by hand

Scope follows your cloud footprint. Most cloud penetration tests cover these four areas.

Layer 1

Identity & access

Who and what can do what, and how far one stolen credential goes.

  • IAM role & policy review
  • Privilege escalation paths
  • Cross-account & cross-tenant trust
  • Federation, SSO & service accounts
Layer 2

Exposed services & network

What an attacker can reach from the internet.

  • Public storage & databases
  • Security groups & firewall rules
  • Management interfaces & APIs
  • Internet-facing hosts & load balancers
Layer 3

Workloads

The compute you run, from virtual machines to functions.

  • Kubernetes & container security
  • Serverless function permissions
  • Instance metadata & credential exposure
  • Secrets in code, images & environment variables
Layer 4

Configuration & logging

How the platform is set up, and whether you would see an attack.

  • CIS Foundations Benchmark review
  • Encryption & key management
  • Logging & alerting coverage
  • Infrastructure as code review
Methodology

How we test: example test cases

A sample of the manual test cases in a typical cloud penetration test. Your scope decides the full list.

CLD-01

Privilege escalation from a low-privilege role

Starting from a developer or CI role, we look for permissions that let us create policies, pass roles or assume more powerful identities.

CLD-02

Instance metadata credential theft

Through server-side request forgery or command injection in a hosted app, we test whether workload credentials can be read from the metadata service.

CLD-03

Public storage and snapshots

We check buckets, blobs, snapshots and database backups for public or cross-account access to sensitive data.

CLD-04

Cross-account trust

We test whether roles trusted by other accounts, vendors or CI systems can be assumed by someone who should not have them.

CLD-05

Kubernetes escape and lateral movement

From a compromised pod, we test service account tokens, RBAC and node access to see how far an attacker can move.

CLD-06

Secrets in pipelines and images

We search container images, function settings and CI/CD variables for keys and passwords.

Sample finding

What a finding looks like in our report

An illustrative example in our report format. Not client data.

Finding 01 · IllustrativeCritical

SSRF in an image service gives read access to every customer upload bucket

CWE-918 Server-Side Request Forgery (SSRF) · MITRE ATT&CK T1552.005 Cloud Instance Metadata API

What we found

An image resizing endpoint fetched any URL it was given. We pointed it at the instance metadata service, which returned temporary credentials for the workload's role. That role could read every storage bucket in the account, including customer uploads.

Impact

An unauthenticated attacker can download files uploaded by any customer.

How to fix it

Allow-list the hosts the image service may fetch from, and require the token-based metadata service (IMDSv2 on AWS). Limit the workload role to the one bucket it needs, and alert when its credentials are used from outside your network.

What you get

What you get from every cloud pentest

Not a list of misconfigurations. Proven attack paths and fixes your engineers can act on.

1

Attack paths with proof, ranked by exploitability

Each finding has a severity, a reproducible proof of concept and remediation guidance, with chained issues shown as one path.

2

Configuration review mapped to CIS Benchmarks

Configuration findings map to the CIS Foundations Benchmark for your provider, in a report your auditors and customers can read.

3

Walkthrough, then retesting

The tester who found each issue walks your engineers through it, and retesting is available once fixes land.

ioSENTRIX sample penetration test report cover

See how we write findings before you talk to us

A redacted sample penetration test report (web application): finding write-ups, proof-of-concept evidence and remediation. No form required.

Download the sample report (PDF) →
Verified reviews

What security leaders say about working with us

★★★★★
“Unlike other providers, Omair and his team truly dive deep into our infrastructure, delivering findings that go well beyond the surface level. Communication is direct and seamless.”
Jesus B.
Cybersecurity Manager, Banking
Verified G2 review ↗
★★★★★
“We were impressed with ioSENTRIX’s ability to independently validate the security of our customer-facing product.”
Zeehasham R.
Data Scientist, Security Operations · Fortune 500 insurer
Verified Clutch review ↗
★★★★★
“The team at ioSENTRIX is professional and highly skilled at their craft.”
Awwab A.
SVP, Chief Information Security Officer
Verified G2 review ↗
How it works

How does a cloud penetration test work?

Four steps, so you know what happens and what you get.

01

Scope and access

We agree the accounts, subscriptions or projects in scope, the provider's testing rules, and the access we need.

Start
02

Testing and review

Testers attack exposed services and identities, then review configuration against CIS Benchmarks.

Most of the engagement
03

Report

Each finding has a severity, a reproducible proof of concept and remediation guidance.

At close
04

Remediation support

We walk your engineers through the findings, and retesting is available once fixes land.

After fixes
Reply in under an hour → scoping call → fixed quote in writing → testing, by scope → report, walkthrough and retest
How we compare

How is a cloud pentest different from a configuration scanner?

What a cloud pentest covers compared with the usual alternatives.

ioSENTRIX cloud pentest
Cloud configuration scanner (CSPM)
External network scan
What is tested
Identities, exposed services, workloads and configuration
Settings against a rule set
Public IPs and open ports
Attack paths
Chained by hand and proven
Listed as separate findings
Not tested
IAM privilege escalation
Tested from real starting roles
Partly flagged
Not tested
Evidence
Reproducible proof of concept and a fix
Rule violations to triage
Finding list
Standards
CIS Benchmarks, MITRE ATT&CK, CSA CCM
CIS Benchmarks
Varies by tool
Scope and price

What affects the scope and price of a cloud pentest?

Cloud tests are priced on effort, not on your cloud bill. These are the decisions that move the quote.

What moves the quote

  1. 01How many accounts, subscriptions or projects are in scope
  2. 02Which providers: AWS, Azure, Google Cloud or a mix
  3. 03Kubernetes clusters, containers and serverless functions
  4. 04Whether hosted applications and APIs are tested in the same engagement
  5. 05Configuration review, penetration test, or both
  6. 06Retesting windows and the evidence your auditors expect
Read: Cloud Penetration Testing: Methodology, Tools and Services for AWS, Azure and GCP →

What we need from you to start

  • A list of the accounts, subscriptions or projects in scope
  • A read-only audit role for the configuration review
  • Test credentials for the starting points we agree, such as a developer role
  • Any production assets or actions that are off limits
  • A technical contact for questions during testing
Scope my cloud test
Track record

Numbers you can check

Ratings you can verify on G2 and Clutch.

G2
4.9 / 5
on G2 from 12 verified reviews
Clutch
5.0 / 5
on Clutch, Premier Verified
CREST-accredited for penetration testing
2017
founded; CREST-accredited, ISO 27001 certified, SOC 2 Type 2 attested
Independently verified

Credentials held by the firm

Every engagement runs inside a company whose methods and own security are checked by outside bodies.

CREST-accredited for penetration testing

CREST-accredited for penetration testing

CREST assesses the firm's testing methodology, quality assurance and handling of client data.

View our CREST listing →
SOC 2 Type 2 attested

SOC 2 Type 2 attested

An independent auditor tested our own security controls over time.

Request the SOC 2 report →
ISO/IEC 27001 certified

ISO/IEC 27001 certified

Our information security management system is certified to ISO/IEC 27001.

View in our trust center →
2026 CyberSecurity Breakthrough Awards winnerG2 High Performer, Fall 2026

Recognized independently

Penetration Testing Solution of the Year, 2026 CyberSecurity Breakthrough Awards. G2 High Performer, Fall 2026.

Founded in 2017.

Our commitments

What you can count on

Four promises we make on every testing engagement.

  • Free retest of every fixOnce your team fixes a finding, we test it again at no extra cost and update the report.
  • A fixed priceThe quote you sign is what you pay. The price only changes if you change the scope.
  • A report your auditor acceptsIf your auditor has questions about the report, we answer them and update it until it is accepted.
  • A reply in under an hourSend the form and we reply within an hour during US business hours.
For your buying team

Everything your reviewers will ask for

Security, finance and procurement each need something different. Forward this page, or pull what each reviewer needs.

For security

Sample report

See exactly what you get: findings, proof of concept, fixes and retest results.

Download the sample report (PDF) →
For vendor risk

Trust center

Our SOC 2 Type 2 report and security documentation for your vendor review.

Open the trust center →
For procurement

Procurement pack

Master services agreement, sample statement of work, certificate of insurance and W-9.

Request the procurement pack →
For your team

Share this page

Send the link to the people who need to sign off.

Who you work with

Who does the work

Senior security engineers do the hands-on work and write up the results, so the person who found an issue explains it to your team.

Certified engineers

Each engineer holds one or more of OSCP, OSWE, OSCE, CISSP, CISA or AWS security certifications.

Accredited firm

ioSENTRIX is CREST-accredited for penetration testing, ISO/IEC 27001 certified and SOC 2 Type 2 attested.

Since 2017

Founded in 2017, with security work for Fortune 100, financial services, insurance and SaaS companies.

Ready to see how far one leaked key goes in your cloud?

We reply in under an hour · no sales pitch

Scope my cloud test
Standards

Frameworks we test and map to

◆CIS Amazon Web Services Foundations Benchmark◆CIS Microsoft Azure Foundations Benchmark◆CIS Google Cloud Platform Foundation Benchmark◆CIS Kubernetes Benchmark◆MITRE ATT&CK Cloud Matrix◆CSA Cloud Controls Matrix (CCM)◆NIST SP 800-115
FAQ

Frequently asked questions

Do we need permission from AWS, Azure or Google to run a cloud pentest?

Usually not, but each provider sets rules. AWS allows testing of a listed set of services without prior approval, Microsoft does not require notice for Azure but requires its Rules of Engagement to be followed, and Google does not require notice if you follow its Acceptable Use Policy and Terms of Service. We work within those rules, which, for example, prohibit denial-of-service testing on AWS and Azure.

What is the shared responsibility model?

Cloud providers secure the underlying infrastructure, and you secure what you build and configure on it: identities, data, network rules and workloads. A cloud pentest tests your side of that line. Read more on the shared responsibility model.

Do you test Kubernetes and containers?

Yes. We test cluster access, RBAC, service account tokens, network policies and container images, whether you run managed Kubernetes or your own clusters.

Do you need access to our cloud console?

For the configuration review, we ask for a read-only audit role. For the penetration test, we start from agreed points, such as the internet, a leaked developer key or a compromised workload, to show what an attacker could do from there.

How long does a cloud pentest take?

Most cloud tests run days to weeks, depending on the number of accounts, providers and workloads in scope. We reply in under an hour during US business hours, and the scope, timeline and fixed quote follow the scoping call.

Ready when you are

Find your cloud attack paths before an attacker does

Tell us which providers and accounts you run. We will scope a test and send a fixed quote based on effort.

We reply in under an hour · Fixed quote in writing before work starts · Your details are never shared