Skip to content

The Atarus series

Cloud Penetration Testing: errata.

Corrections to Cloud Penetration Testing are listed here once the first PDF is published. The volume is in production.

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

How errata work

A correction is a new run, not an edit.

  • Each correction records the chapter, the page, the wrong text, the fix, the date, and whether a captured output changed.
  • A changed output is captured again from a fresh run and gets a new run id in the manifest. It is never edited by hand.
  • The PDF is republished with each batch of corrections and a changelog.
  • Printed copies take the corrections at the next point edition, numbered 1.1, 1.2 and so on, with the edition and date on the title page.

Page numbers refer to the edition on your copyright page. Check that edition against the table before you report.

Corrections

Errata for Cloud Penetration Testing.

Confirmed corrections to Cloud Penetration Testing
ChapterPageWrong textFixDateCapture changed
No corrections yet. The table fills from the 0.9 PDF.

Report an error

The form opens with the first PDF.

There is no edition of Cloud Penetration Testing to correct yet. The report form appears on this page with the 0.9 PDF. Errors in Foundations go through the form on its errata page.

What happens to a report

  • We check it against the manuscript and the capture records.
  • A confirmed error goes in the table above with the date, and into the next PDF.
  • If the fix changes an output, the capture is run again and the manifest updated.

A security issue in an Atarus website or service is not an erratum. See the disclosure policy.