# CIS Controls v8 11.2 — Perform Automated Backups - Source: https://support.icompaas.com/compliance/cis-controls-v8/11-2-perform-automated-backups - Section: [Compliance](https://support.icompaas.com/compliance) › [CIS Critical Security Controls v8](https://support.icompaas.com/compliance/cis-controls-v8) › Control 11 — Data Recovery - Last updated: 2026-06-05 - Publisher: iCompaas, Inc. (https://www.icompaas.com) **CIS Controls v8**·Control `11.2`·critical·Component: **Recover** ## What this control requires > Perform automated backups of in-scope enterprise assets. Run backups weekly, or more frequently, based on the sensitivity of the data. > > — CIS Controls v8, Control 11.2 ### In plain English Perform automated backups of in-scope enterprise assets. In practice, this means you can prove you perform data-level controls on a defined cadence. ## Why it matters The CIS Controls are an industry-vetted, prioritised defence: skipping a safeguard widens the attack surface that the safeguards above and below it assume is closed. Audit frameworks (FedRAMP, PCI DSS, HIPAA) all cite CIS as evidence of due care. This control is rated **critical** in the source catalogue. Treat gaps here as production incidents in the risk register, not housekeeping. ## What an auditor looks for A CIS-aligned reviewer wants to see (a) which Implementation Group you are targeting, (b) a documented owner for the safeguard, and (c) a tooling or process artefact (config, scan output, ticket) that proves the safeguard runs on the cadence the control demands. Within **Recover**, the assessor will trace your implementation back to the catalogue reference (Control 11.2) and look for objective evidence on the latest two assessment cycles. ## How to implement #### Incident Response **Runbook.** Maintain a runbook keyed by incident type with named roles (IC, comms, scribe), an out-of-band comms channel, and a 72-hour timeline for external notification. **Tabletop.** Run a quarterly tabletop exercise (ransomware, insider, supply-chain) and feed gaps back into the runbook. ### Operational checklist - **Perform.** Document the trigger, the owner and the cadence. - **Scope:** data, response, enterprise. ## Evidence to collect - **Ticketing Workflow.** `ticketing_workflow` evidence - **Infra Scan.** Continuous infrastructure-posture telemetry — AWS Config, Azure Policy compliance, GCP Organisation Policy, Wiz / Prisma findings. Workflow metrics (ServiceNow, Jira) show approvals and remediation. Focus: Perform Automated Backups. ## Common pitfalls - Runbooks that name a role but no person, or list a paging channel that no longer exists. ## How it maps to other frameworks Computed from shared tags, control component and key-operation subjects — handy when you are reconciling controls across an audit. - [**GDPR Article 49** — Derogations for specific situations](https://support.icompaas.com/compliance/gdpr/article-49-derogations-for-specific-situations) - [**BSI C5:2020 AM-04** — Decommissioning of Hardware](https://support.icompaas.com/compliance/bsi-c5-2020/am-04-decommissioning-of-hardware) - [**SOC 2 (2017 TSC) CC7.4** — Incident Response](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/cc7-4-incident-response) - [**ISO/IEC 27001:2022 A.5.8** — Information security in project management](https://support.icompaas.com/compliance/iso-27001-2022/a-5-8-information-security-in-project-management) - [**NIST SP 800-171 Rev. 3 3.3.6** — Audit Record Reduction and Report Generation](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-3-6-audit-record-reduction-and-report-generation) ## Related controls in CIS Controls v8 - [**Control 11.5** — Test Data Recovery](https://support.icompaas.com/compliance/cis-controls-v8/11-5-test-data-recovery) - [**Control 17.9** — Establish and Maintain Security Incident Thresholds](https://support.icompaas.com/compliance/cis-controls-v8/17-9-establish-and-maintain-security-incident-thresholds) - [**Control 17.4** — Establish and Maintain an Incident Response Process](https://support.icompaas.com/compliance/cis-controls-v8/17-4-establish-and-maintain-an-incident-response-process) - [**Control 5.3** — Disable Dormant Accounts](https://support.icompaas.com/compliance/cis-controls-v8/5-3-disable-dormant-accounts) - [**Control 17.8** — Conduct Post-Incident Reviews](https://support.icompaas.com/compliance/cis-controls-v8/17-8-conduct-post-incident-reviews) - [**Control 17.7** — Conduct Routine Incident Response Exercises](https://support.icompaas.com/compliance/cis-controls-v8/17-7-conduct-routine-incident-response-exercises) ## References - [Center for Internet Security — CIS Controls v8](https://www.cisecurity.org/controls/v8) - Catalogue identifier: `Control 11.2` Topics: governance riskchange managementincident response ## Related compliance guidance - [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Configuration checks like this one are the technical half of a SOC 2 / ISO 27001 programme — the guide shows where they fit, what else an auditor expects, and how to evidence them. - [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): ISO 27001 Annex A.8 (technological controls) is where cloud hardening evidence lands; the guide shows how to run the ISMS around it.