What an auditor actually wants to see

Two cloud engineers at a dark wall display, one pointing at a magenta branch of a storage graph

Auditors do not want a screenshot of a dashboard. They want a clear answer to a simple question: who could read this, on what date, and who approved it?

I spent six years answering that by hand, one bucket at a time. Each answer took a week, because the facts lived in four different consoles.

What makes good evidence

  • A dated record of who could reach each data store.
  • The change that altered it, with its reviewer.
  • A list of exceptions, each with an owner.
  • The control it maps to, in CIS, SOC 2 or ISO/IEC 27001.

If the answer takes a week, the control is not really working.

Keep it boring

A good audit is dull. Export the same report every month, keep it with your pull requests, and the auditor reads a history in place of a story written the week before.

About the author

Mara co-founded Wardline after six years of answering the same audit question by hand. She still reads the first map of most new customers. Fictional author, demo content.

Related cloud notes