# CIS 7.2 — Establish and Maintain a Remediation Process

- Source: https://support.icompaas.com/support/solutions/articles/a_gen_cis_72_631a9c9450-cis-72-establish-and-maintain-a-remediation-process
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [AWS Checks New Version](https://support.icompaas.com/support/solutions/62000112673) › [Respond](https://support.icompaas.com/support/solutions/folders/f_gen_62000112673_respond)
- Last updated: 2026-05-30
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

CIS · Control 7.2 · Priority: critical · Component: Respond

### What this control covers

Establish and maintain a risk-based remediation strategy documented in a remediation process, with monthly, or more frequent, reviews.

### Why it matters

Risk is the language an executive team understands; this control connects technical reality to board-level decisions and budget allocation.

### How to implement

#### AWS

Codify the policy intent as **SCPs, AWS Config conformance packs, and Security Hub standards** so the cloud enforces what the document says.

#### Azure

Codify in **Azure Policy initiatives** (built-in regulatory compliance for CIS, ISO 27001, SOC 2, HIPAA) and assign at management-group level.

#### On-premises

Maintain a policy library with a documented review cadence (annual minimum); store in your GRC tool with attestation tracking. Map each policy to controls so an audit pull cites the exact policy clause.

### Evidence to collect

-   `policy_document` — A signed, version-controlled policy stating leadership intent and the named owner.
-   `infra_scan` — See the iCompaas Evidence library for the canonical source for this evidence type.

Signed policy or standard documents the safeguard. Focus: Establish and Maintain a Remediation Process.

### Quick checklist

-   Establish And Maintain — Remediation Process / Reviews

### Related articles on this site

-   [Acquisition Risk Management](https://support.icompaas.com/support/solutions/articles/62000225148-acquisition-risk-management)
-   [Security Headers Remediation - Content Security Policy](https://support.icompaas.com/support/solutions/articles/62000226554-security-headers-remediation-content-security-policy)
-   [Security Header Remediation: Referrer-Policy](https://support.icompaas.com/support/solutions/articles/62000226558-security-header-remediation-referrer-policy)
-   [NIST 800-171 3.4.1 Establish and maintain baseline configurations and inventories of organizational systems (including hardware, software, firmware, and documentation) throughout the respective system development life cycles.](https://support.icompaas.com/support/solutions/articles/62000229280-nist-800-171-3-4-1-establish-and-maintain-baseline-configurations-and-inventories-of-organizational-s)

## 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.