Skip to content
System Designer

Business · 3 minutes

Proof built in

Auditors want proof: who did what, who can see what, and that data is protected.

Open this lesson
Auditors want proof: who did what, who can see what, and that data is protected.

Prove it, do not promise it

Handling health, money or personal data comes with rules. An audit asks for evidence, not promises: a log nobody can edit, encryption with managed keys, one controlled place for personal data, tested backups, and a sign-in for every action.

Least privilege

A reporting service needs one capability. Try a leaked credential before and after restricting its permissions, and keep an audit trail of allowed actions.

Try the idea

An audit lands at noon. Add what the auditors will ask for.

Key numbers

Keep an audit log
≈ 1 to 7 years. depends on the rule, approx.
Test a backup restore
≈ every quarter. an untested backup is a hope, approx.
Rotate keys
≈ every 90 days. approx.

Check your reasoning

Think through these questions before opening the lesson. In the game you can test the idea and compare your reasoning.

  • What does an auditor ask for?
  • Where do secrets belong?
  • What is least privilege?

The key point

Build the proof in from the start; adding it after the audit is far harder.

Practise this idea

Continue through the lesson tracks