# CIS 17.3 — Establish and Maintain an Enterprise Process for Reporting Incidents

- Source: https://support.icompaas.com/support/solutions/articles/a_gen_cis_173_50a0081345-cis-173-establish-and-maintain-an-enterprise-process-for-reporting-incidents
- 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 17.3 · Priority: critical · Component: Respond

### What this control covers

Establish and maintain an enterprise process for the workforce to report security incidents. The process includes reporting timeframe, personnel to report to, mechanism for reporting, and the minimum information to be reported. Ensure the process is publicly available to all of the workforce. Review annually, or when significant enterprise changes occur that could impact this Safeguard.

### 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 an Enterprise Process for Reporting Incidents.

### Quick checklist

-   Establish And Maintain — Enterprise
-   Ensure — Enterprise

### Related articles on this site

-   [164.308(a)(1)(i)- Security management process](https://support.icompaas.com/support/solutions/articles/62000230582-164-308-a-1-i-security-management-process)
-   [Ensure IAM password policy requires minimum length of 14 or greater](https://support.icompaas.com/support/solutions/articles/62000080817-ensure-iam-password-policy-requires-minimum-length-of-14-or-greater)
-   [Ensure ELB uses predefined security policy (ssl)](https://support.icompaas.com/support/solutions/articles/62000219192-ensure-elb-uses-predefined-security-policy-ssl-)
-   [Security Headers Remediation - Content Security Policy](https://support.icompaas.com/support/solutions/articles/62000226554-security-headers-remediation-content-security-policy)

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