Skip to content

The Atarus series

Cloud Penetration Testing.

AWS, Azure, Google Cloud and Oracle Cloud from the first hour to the report. A cloud assessment in the order it is run, with every output a captured run from our lab accounts. In production.

Status
In production
0.9 PDF
In development
Print
In development
Front cover of Cloud Penetration Testing, in the Atarus series: AWS, Azure, Google Cloud and Oracle Cloud from the first hour to the report.

Who it is for

Testers, and the engineers who run the accounts.

Cloud starts at the first hour of an engagement and assumes what the three volumes of Foundations teach. It is for people who test cloud accounts for a living, and for the engineers and detection teams who want to know what a test finds, how it proves it and what the fix looks like in policy.

The parts follow the modules of the AOCP in assessment order. The lab account in every chapter belongs to Wrexby Outfitters, the company that runs through the whole series.

The parts

Six parts, twenty-six chapters.

  1. Part I. Before the first call

    What a cloud test is and is not, the operator log and the evidence package, and how IAM policy evaluation combines allow, deny and boundaries.

  2. Part II. Identity enumeration and access mapping

    The first hour in AWS, Entra ID, Google Cloud and Oracle Cloud, then standing privilege.

  3. Part III. Privilege escalation paths

    IAM path families, trust policies and cross-account reach, resource policies, CI pipelines and OIDC trust, managed identities, service account impersonation and Kubernetes.

  4. Part IV. Secrets, storage and exposure

    Secrets in configuration, who can read the secrets, storage exposure and the metadata endpoint from the application side.

  5. Part V. Guardrails, logging and the defender's view

    CloudTrail and GuardDuty, organization policy, Entra sign-in and audit logs, and password spraying as a detection problem.

  6. Part VI. Persistence, impact and the report

    Footholds found without removing them, reach proved without damage, and the finding and the report around it.

What a chapter carries

More than the Learn page it extends.

Each chapter extends one or more of the free Cloud pages on Learn, which stay canonical on the web. The chapter adds the reasoning behind the order of the checks and these three things.

  • Captured runs end to end.

    Two to four full runs per chapter: the command, the complete output, the operator log line, and the CloudTrail or sign-in event it produced.

  • The defender's view beside every step.

    Which event fires, which service raises it, and what the clean account shows, so a reader on either side of the test can use the chapter.

  • Exercises with the clean result stated.

    From saying what a policy allows to finding the escalation path in a layout, with the sandbox resources each exercise needs and how to tear them down.

The Learn library

Chapter by chapter

The Learn page behind each chapter.

Each chapter names the page it extends in its last lines. The chapter adds what the page leaves out.

The Learn pages behind the chapters of Cloud Penetration Testing
Chapter Learn pages
1. What a cloud test is and is not Scoping a cloud penetration test
2. The operator log and the evidence package Cloud evidence package and operator log
3. IAM policy evaluation AWS IAM policy evaluation logic
4. The AWS first hour Cloud pentest: AWS and Azure IAM enumeration
5. The Entra ID first hour Entra ID enumeration from one user account ; Cloud pentest: AWS and Azure IAM enumeration (in part)
6. The Google Cloud and Oracle Cloud first hours GCP pentest: project and IAM enumeration ; OCI pentest: tenancy and IAM enumeration
7. Standing privilege and PIM Entra PIM and privileged role review
8. The four AWS IAM path families AWS IAM privilege escalation checks
9. Trust policies and cross-account reach AWS cross-account role trust policy review
10. Resource policies that grant access from outside AWS resource policy review: external access
11. CI pipelines and OIDC trust CI pipeline secrets and OIDC trust review
12. Azure managed identities and RBAC assignments Azure managed identity and automation review ; Azure RBAC role assignment review
13. Service account impersonation in Google Cloud GCP service account impersonation review
14. Kubernetes from a read-only kubeconfig Kubernetes pentest: RBAC, secrets, admission
15. Secrets in configuration: functions, user data, parameters AWS secrets in Lambda config and user data
16. Who can read the secrets: Secrets Manager, KMS key policies and grants AWS secrets and KMS key policy review
17. Storage exposure: buckets, SAS links, snapshots, function URLs, registries Public bucket checks: S3, Azure Blob, GCS ; Azure Storage SAS token and account review ; Container registry and image security review ; AWS public exposure: snapshots, AMIs, URLs (in part)
18. The metadata endpoint from the application side SSRF and cloud metadata exposure review
19. CloudTrail and GuardDuty: what the test produced and whether anyone saw it AWS CloudTrail and GuardDuty evidence review
20. Organizations, SCPs and org policy AWS Organizations and SCP guardrail review ; GCP organization policy and IAM review
21. Entra sign-in and audit logs, Conditional Access, device code and consent Entra Conditional Access and MFA gap review ; Entra sign-in and audit log review ; Azure Activity Log review ; Device code and app consent controls review
22. Password spraying and MFA fatigue as detection and policy problems Password spraying and MFA fatigue testing
23. Finding footholds without removing them Cloud persistence audit: AWS and Entra ID
24. Proving reach without damage Prove cloud impact without causing damage ; Stolen token response: M365, Google, Okta (in part)
25. Writing the cloud finding How to write up a cloud finding ; How to write a pentest finding (in part)
26. The report around the findings: summary, scope, coverage, retest plan Cloud pentest report: scope and coverage ; Cloud evidence package and operator log (in part)

How it publishes

The steps, in order.

In development. The book publishes in the order below.

  1. Draft 0.9 PDF

    The whole book in draft, read by outside reviewers and the founding cohort before edition 1.0.

  2. Print edition

    Edition 1.0 in print and ebook, with the capture manifest and the errata page.