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
- In development
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.
-
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.
-
Part II. Identity enumeration and access mapping
The first hour in AWS, Entra ID, Google Cloud and Oracle Cloud, then standing privilege.
-
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.
-
Part IV. Secrets, storage and exposure
Secrets in configuration, who can read the secrets, storage exposure and the metadata endpoint from the application side.
-
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.
-
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.
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.
How it publishes
The steps, in order.
In development. The book publishes in the order below.