main logo icon

Cloud Penetration Testing

Stingrai's penetration testers test AWS, Azure and Google Cloud environments the way real adversaries do: from an exposed bucket or leaked key to IAM privilege escalation, cross-account trust abuse, Kubernetes and serverless compromise and control plane takeover. The result is a set of validated attack paths, not a list of misconfigurations.

Cloud Penetration Testing
ellipse

Our Approach to Cloud Penetration Testing

ellipse

Step 1

Scoping and Rules of Engagement

We inventory the accounts, subscriptions and projects in scope, the clusters, serverless functions and data stores that matter most, and the identity sources behind them. The engagement is scoped within each provider's penetration testing policy, with written authorization from the resource owner and a black box, gray box or white box starting point agreed in advance.

Benefits of Cloud Penetration Testing

A CSPM or CNAPP enumerates misconfigurations. It cannot tell you which of them chain into a breach, how far an attacker can progress from a single leaked credential, or whether your production data is actually reachable. Cloud penetration testing proves exploitability: an object store leaked a key, the key assumed a role, and the role read the customer database.

Our team tests the cloud control plane, identity and the workloads running on it as a single engagement, and delivers a detailed report with reproducible attack paths, severity ratings and remediation guidance mapped to your provider's services.

By completing this assessment, you significantly reduce your risk of:

check icon

Public or misconfigured storage exposing customer data

check icon

IAM privilege escalation, role assumption abuse and cross-account trust exploitation

check icon

Leaked credentials and secrets in code, user data, CI pipelines and container images

check icon

Exposed management interfaces, metadata service abuse and network segmentation failures

check icon

Kubernetes RBAC over-permissioning, container breakout and serverless function abuse

AWS, Azure and Google Cloud Penetration Testing

AWS Penetration Testing

AWS Penetration Testing

Accounts, roles and trust policies: cross-account role assumption, over-broad resource and bucket policies, instance profile and metadata abuse, confused deputy conditions, Lambda and API Gateway, EKS, and the AWS services your applications depend on. Scoped within the AWS customer penetration testing policy.

Azure and Entra ID Penetration Testing

Azure and Entra ID Penetration Testing

Subscriptions, management groups and, above all, identity: application registrations, service principals and consent grants, Conditional Access gaps, hybrid-join and on-premises trust relationships, storage accounts, Key Vault, AKS and Azure Functions. Scoped within Microsoft's penetration testing rules of engagement.

Google Cloud Penetration Testing

Google Cloud Penetration Testing

Projects, folders and the organization node: service account impersonation chains, IAM Conditions, Workspace identity, Cloud Storage and BigQuery access, GKE, Cloud Run and Cloud Functions, and the attack paths that most often surprise teams migrating from AWS. Testing is confined to your own projects.

Control Plane to Workload Coverage

Identity, IAM and Control Plane

Identity, IAM and Control Plane

  • check icon

    Privilege escalation paths through roles, policies, service accounts and trust relationships.

  • check icon

    Credential and secret exposure across code, CI/CD, user data, snapshots and container images.

  • check icon

    Management plane access from compromised workloads, metadata services and CI runners.

  • check icon

    Logging, monitoring and detection gaps observed while the attack paths are executed.

Workloads, Kubernetes and Data

Workloads, Kubernetes and Data

  • check icon

    Kubernetes control plane exposure, RBAC, network policies, secrets handling and container breakout.

  • check icon

    Serverless and managed services: function permissions, event injection and insecure defaults.

  • check icon

    Object storage, databases, queues and encryption at rest and in transit.

  • check icon

    Applications and APIs hosted in the environment, where they are agreed in scope.

What Stingrai tests in a cloud environment

Cloud engagements are human-led: Stingrai's penetration testers work from identity and the control plane down to workloads and data, within each provider's testing policy. Exact coverage is confirmed at scoping and stated in the report.

Identity and IAM

  • Privilege escalation through roles, policies and permission boundaries
  • Cross-account, cross-subscription and cross-project trust
  • Service accounts, service principals and workload identities
  • Federation, SSO and Conditional Access gaps

Control plane and configuration

  • Management plane access from compromised workloads
  • Resource and bucket policies, public exposure and sharing
  • Configuration measured against the CIS Benchmarks for each provider
  • Logging and alerting gaps observed while attack paths run

Secrets and credentials

  • Keys and secrets in code, CI/CD, images and user data
  • Instance metadata service abuse
  • Key Vault, Secrets Manager and Secret Manager access
  • CI runners and deployment pipelines holding cloud credentials

Kubernetes and containers

  • EKS, AKS and GKE control plane exposure
  • RBAC, service account tokens and admission controls
  • Network policies and pod-to-pod reachability
  • Container breakout and node compromise

Serverless and managed services

  • Lambda, Azure Functions, Cloud Run and Cloud Functions permissions
  • Event source and trigger injection
  • API Gateway, queue and topic configuration
  • Insecure defaults in managed databases and caches

Data and network exposure

  • Object storage, databases and queues reachable from a foothold
  • Encryption at rest and in transit
  • Security groups, firewall rules and segmentation
  • Internet-facing services and management interfaces

Methodology and standards

The starting point is agreed at scoping: an external, black-box view of what is exposed; an assumed-breach foothold such as a leaked key or a compromised workload; or a read-only reviewer role for configuration review. Most engagements combine a foothold with configuration review, which shows both what is misconfigured and what an attacker can reach from it.

From the foothold, Stingrai's penetration testers chain identity, configuration and workload weaknesses into attack paths toward production data and the control plane, and document every step with the evidence needed to reproduce it.

Every engagement is scoped within the provider's own penetration testing policy, with written authorization from the resource owner. Denial-of-service testing is excluded.

What you receive

Evidence for customers and auditors, priorities for leadership and provider-specific detail for engineering.

For engineering

Findings in the PTaaS portal

Each attack path is posted as soon as it is confirmed, with step-by-step evidence and remediation mapped to the services and policies involved.

For leadership

Executive summary

A plain-language view of what an attacker could reach, the blast radius and the fixes to prioritize first.

For security teams

Full technical report

Methodology, coverage, every attack path with the commands to reproduce it, and CIS-mapped configuration findings, as a redactable PDF.

For engineering

Retesting included

Fixed findings are retested on request, and their status is updated in the portal and the report.

For customers and auditors

Attestation letter

Issued with every human-led cloud engagement, stating scope and testing dates, ready to share.

For the project team

Integrations and direct chat

Jira, Slack and GitHub integration, and direct chat with the assigned penetration testers throughout the test.

Sample Pentest Report

Explore how we structure executive summaries, prioritized findings, evidence, reproduction steps, and remediation guidance, tailored to SOC 2, ISO 27001, PCI DSS, and HIPAA compliance.

PDF, 4 MB. No email address required.

Timeline

Typical durations. The schedule for each engagement is fixed in writing at scoping.

ScopingPricing within 24 hours
Submit the Get a Quote form and receive pricing within 24 hours, or book a 30-minute discovery call to review accounts, clusters and starting points first.
Configuration reviewTypically 3 to 5 testing days
A read-only review of one account, subscription or project against the CIS Benchmarks and the provider's security guidance.
Attack path testing
Driven by the number of accounts and projects, clusters, IAM complexity and whether the engagement starts external, from a foothold or both.
FindingsAs they are confirmed
Every attack path reaches the PTaaS portal when it is confirmed, so remediation starts during the test.
ReportAt the close of testing
The executive summary, full technical report and attestation letter are issued when the testing window closes.
RetestOn request, included
Once fixes are deployed, a retest is requested from the portal and the status of every finding is updated.

Pricing and what drives cost

Cloud engagements are quoted to scope; there is no package price. These factors set the number of testing days:

Accounts, subscriptions and projects
Each account, subscription or project in scope, and how they trust each other.
Providers
One provider, or a multi-cloud estate across AWS, Azure and Google Cloud.
Clusters and workloads
Kubernetes cluster count and size, serverless functions and managed services in scope.
IAM complexity
The number of roles, policies, identities and federation paths to analyze.
Starting point
External only, an assumed-breach foothold, configuration review, or a combination.
Cadence
A one-time assessment or a continuous program that retests as the environment changes.

Submit the Get a Quote form and receive pricing within 24 hours. Every quote includes the retest. Market ranges and quote comparisons are in the cloud and Kubernetes scoping and cost guide.

Compliance evidence

One cloud penetration test and its retest results produce evidence for several programs at once.

SOC 2
Evidence for the separate evaluations described in CC4.1, and supporting evidence for vulnerability identification under CC7.1 alongside scan output.
PCI DSS v4.0.1
Requirement 11.4: internal and external penetration testing of a cloud-hosted cardholder data environment, plus segmentation validation under 11.4.5.
ISO/IEC 27001:2022
Evidence for Annex A 8.8, management of technical vulnerabilities, and 8.9, configuration management, for cloud services in scope.
HIPAA Security Rule
Evidence for the risk analysis at 45 CFR 164.308(a)(1)(ii)(A) and the periodic technical evaluation at 164.308(a)(8) for cloud systems holding ePHI.
CMMC Level 2
Evidence for periodic security control assessment (CA.L2-3.12.1) and vulnerability identification (RA.L2-3.11.2) in cloud environments that handle CUI.

Why Stingrai

check icon

CREST-Accredited Firm

Stingrai Inc. is a CREST-accredited penetration testing provider, founded in Toronto in 2021 with an office in London. The company itself is accredited by CREST for Penetration Testing and for AI-Enabled Penetration Testing, which assesses its responsible use of AI in testing.

check icon

Named Penetration Testers

Every cloud engagement is human-led by two named penetration testers from a team holding OSCE³, OSWE, OSEP, CREST CRT and CISSP certifications, and every report is reviewed by the team lead and an engagement partner.

check icon

Published Research

Stingrai's researchers have published 18 CVEs, and team members appear in the Halls of Fame of Apple, Google, Facebook and the US Department of Defense.

check icon

Provider-Aware Rules of Engagement

Every engagement is scoped within the AWS customer penetration testing policy, Microsoft's penetration testing rules of engagement and Google Cloud's policies, with written authorization from the resource owner before any testing begins.

check icon

One-Time or Continuous

A one-time cloud penetration test fits an audit, a migration or a new environment; a continuous program retests as accounts, clusters and services change. Many clients begin with a one-time assessment and move to a continuous program.

check icon

Rated 5.0 on Clutch

Stingrai holds a 5.0 rating across 20 verified Clutch reviews and 4.9 on G2, from clients ranging from startups to enterprises in healthcare, financial services and SaaS.

Trusted by Industry Leaders

quote icon

Rigorous, genuinely hands-on pentest partner that behaves like part of your team. The technical depth is well beyond what we expected at this price point, and they traced issues to specific code paths.

Elia R., Mesh ID (G2 review)

quote icon

Simplifies the pentesting process by giving us one place to request, manage, and track security testing. We spent WAY less time coordinating and more time improving security.

Riley D., Frontend Developer, TPH (G2 review)

Frequently asked questions about cloud penetration testing

An authorized assessment that proves which misconfigurations, identity relationships and exposed services in your AWS, Azure or Google Cloud environment an attacker can chain into real impact. It covers six layers: identity and IAM, configuration and posture, external network exposure, workloads and Kubernetes, serverless and managed services, and data stores and secrets. The primary attack surface is the cloud control plane rather than the perimeter, so the work centers on role assumption, trust policies and resource permissions.

Prove Which Cloud Misconfigurations Are Actually Exploitable

Our cloud penetration tests chain real attack paths across AWS, Azure and Google Cloud, from an exposed credential to the control plane and your production data. Every path includes step-by-step evidence, provider-specific remediation guidance and a complimentary retest, delivered as a one-time assessment or a continuous program.