11.3 Protect Recovery Data
Protect recovery data to the same standard as the original, using encryption or separation as the requirements dictate. Implementation Groups: IG1, IG2 and IG3 (part of the IG1 essential cyber hygiene baseline, so every enterprise applies it). Asset type: Data. Security function: Protect.
Source: CIS Controls v8.1, 11.3. 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 CIS Controls v8.1 in the compliance library.
Each safeguard shows its Implementation Groups. IG1 is the essential baseline for every enterprise, IG2 adds to it, IG3 is all 153. Version 8.1 adds the Govern security function and asks for more processes to be documented; numbering is unchanged from v8.
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
- Backup encryption settings and key management · Key management / PKI
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Access control lists on backup repositories · Policy repository / GRC workspace
- Separation of backup administration credentials · Policy repository / GRC workspace
First move
Common gaps auditors find
- Backups readable by general domain admins
- Unencrypted backup media
- Same credentials for production and backup
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 sheet11.2 Perform Automated Backups · 11.4 Establish and Maintain an Isolated Instance of Recovery Data