EvidenceSheet

BR-2 Protect backup and recovery data

Protect backup data with encryption, immutability, soft delete, and multi-user authorisation against ransomware and insider threats.

Source: Azure Security Benchmark v3 (renamed Microsoft cloud security benchmark), BR-2. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open Azure Security Benchmark v3 (renamed Microsoft cloud security benchmark) in the compliance library.

4
artefacts
4
held by a system
0
at each review
easy
to go live
Backup / DR tooling
where the evidence lives
teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

  • Immutable vault configuration · Backup / DR tooling
  • Soft delete settings · Backup / DR tooling
  • MUA configuration · Backup / DR tooling
  • Backup access audit log · Backup / DR tooling

periodic reviewEvidence produced at each review

none for this control

governing documentDocuments that govern the control

none for this control

First move

Automate the pull from your Backup / DR tooling. Backup job success history and restore-test logs from the backup platform.

Common gaps auditors find

Do this for your whole sheet

Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.

Build my evidence sheet

BR-1 Ensure regular automated backups · BR-3 Monitor backups