Black Friday Our software, PenTest Project: Slate Enterprise at €53 instead of €173 per user a month, and Flint free for 12 months. Until 30 November. See the offer →
PenTest Hub logo

Objective-based · Covert · Identity-led

Cloud Red Teaming

Would you notice an attacker moving through your cloud? We simulate advanced, targeted attacks on your AWS, Azure and Google Cloud environments and test whether your detection and response would stop them, without disrupting your services.

  • Identity and IAM attack paths
  • Detection and response tested
  • CARTE-certified operators
Sample attack path · Cloud red teamSample
STEP 1Access key found in a public code repositoryBelonged to a build pipeline
UNSEENPrivilege escalation through a misconfigured roleThe pipeline role could edit its own policy
UNSEENLateral movement into the production accountThrough a cross-account trust
REACHEDObjective: customer database snapshot copiedNo alert reached the security team
Every step mapped to MITRE ATT&CK, with the detection that was missedSample engagement

In one sentence

What is cloud red teaming?

Cloud red teaming is an objective-based, covert simulation of an advanced attack on your cloud environment, exploiting real attack paths such as identity privilege escalation, insecure APIs and lateral movement, to test whether your detection and response would stop it.

Where a cloud assessment lists weaknesses, a cloud red team shows what a determined attacker could achieve with them, and whether anyone would notice. It is carried out without disrupting your services.

Typical objectives

  • Reach customer data in a production account
  • Take control of a critical subscription or project
  • Move from a developer account to production
  • Stay undetected for a set period

Scope

What a cloud red team covers

The routes real attackers take through cloud environments.

Initial access

Leaked credentials, exposed services and identity-based entry points, as agreed in the rules of engagement.

  • Leaked keys
  • Identity
  • Exposed services

Privilege escalation

Abusing roles, policies and managed identities to gain more control.

  • IAM
  • Managed identities
  • Policies

Lateral movement

Moving between accounts, subscriptions, projects and on-premises systems.

  • Cross-account
  • Hybrid
  • Federation

Detection and response

Whether your cloud monitoring raises alerts, and whether your team acts on them.

  • Alerts
  • SOC
  • Response

Engagement types

Choose the engagement that fits

From a full covert operation to a collaborative exercise with your defenders.

Most realistic

Full cloud red team

Covert operations from initial access to objective, testing detection and response end to end.

Fast and focused

Assumed breach

We start with a compromised identity or workload to test what happens next.

Collaborative

Cloud purple teaming

We replay cloud attack techniques with your defenders to tune detections in real time.

Engagement

How we work with you

  1. Scope online

    Describe what you need in Flint, our scoping platform. Answer only the questions that apply.

  2. Proposal, signed online

    Effort, price and the statement of work are built from your answers.

  3. Ready for day one

    Authorisation, test accounts and rules of engagement are agreed before testing starts.

  4. Senior-led testing

    Certified consultants lead the test. Our own AI framework, Striker AI, takes on the repetitive work.

  5. Report and retest

    Your report is ready in Slate, our client portal, within 48 hours of testing ending.

What you receive

Everything stays in one place, in your own client portal.

  • An attack narrative from first access to objective
  • A MITRE ATT&CK mapping of every technique
  • Detection gaps rated by risk
  • An executive briefing
  • A replay session with your defenders
  • Your report in Slate within 48 hours of testing ending

Standards

Frameworks we follow

So results can be compared over time and support your regulatory requirements.

  • MITRE ATT&CK for Cloud
  • CREST guidance
  • TIBER-EU red teaming approach
  • DORA
  • NIS2

FAQ

Frequently asked questions

Can't find yours? Ask a senior tester and we'll reply directly.

What is the difference between a cloud assessment and a cloud red team?
An assessment reviews configuration in depth and lists weaknesses. A cloud red team pursues objectives covertly to show what an attacker could achieve and whether you would detect it.
Will a cloud red team disrupt our services?
No. It runs under agreed rules of engagement, with a contact who can pause testing at any time, and avoids actions that affect availability.
Which clouds do you cover?
AWS, Microsoft Azure, Google Cloud and hybrid identity such as Entra ID and Okta, led by CARTE-certified operators.
Do we need permission from the cloud provider?
Generally not for your own resources, as long as testing follows the provider's policies. We confirm the details during scoping.
When will we receive the report?
Within 48 hours of testing ending, in Slate, our client portal, followed by a replay session with your defenders.

Contact

Tell us what you need to test

A senior tester reads every message and replies directly.