Skip to content

The Atarus series

Cloud Penetration Testing: the captures.

Every command output in Cloud Penetration Testing will be a captured run from our lab accounts. The volume is in production; this page lists those runs once the first PDF is published.

Front cover of Cloud Penetration Testing, in the Atarus series: AWS, Azure, Google Cloud and Oracle Cloud from the first hour to the report.

What a capture is

A real run, printed in full.

A capture is one command run on the bench edition the chapter names, in the order the chapter gives, with its complete output recorded by the harness. The book prints that output with a run id beneath it. Nothing in a printed output was typed by hand.

Before a block is printed, addresses and keys are replaced with fixed placeholders. The raw run stays on the capture host and is never published. When a correction changes an output, we run the capture again; we never edit an output by hand.

Run ids and hashes

How a block is named and checked.

Run id

r-20261031-ch01-03

The letter r, the date of the run, the chapter and the step within it. The id above is chapter 1, step 3, run on 31 Oct 2026.

Raw hash
SHA-256 of the output as the terminal produced it, before any placeholder went in. It proves the run existed without publishing it.
Printed hash
SHA-256 of the block exactly as the book prints it, header line included. This is the one to check a printed block against.
Each entry also records
The command, its exit code, the UTC time of the run, the bench edition, the host architecture and hypervisor, and the terminal width. No entry carries raw output.

The manifest

The public manifest for Cloud Penetration Testing.

Published on this page as captures.json, generated from the same capture records the book build reads, so the two cannot drift.

Not yet published

The manifest publishes with the 0.9 PDF, and the table of runs appears here.

Lab kit

The lab kit, coming with the PDF.

Cloud runs in sandbox accounts you own. Each chapter names the resources its exercises need and how to tear them down, and the kit that builds them ships as CloudFormation, Bicep and OpenTofu. The kit and its checksums are published here with the 0.9 PDF, which is in development.