# CIS 17.2 — Establish and Maintain Contact Information for Reporting Security Incidents

- Source: https://support.icompaas.com/support/solutions/articles/a_gen_cis_172_b62a645afb-cis-172-establish-and-maintain-contact-information-for-reporting-security-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.2 · Priority: critical · Component: Respond

### What this control covers

Establish and maintain contact information for parties that need to be informed of security incidents. Contacts may include internal staff, third-party vendors, law enforcement, cyber insurance providers, relevant government agencies, Information Sharing and Analysis Center (ISAC) partners, or other stakeholders. Verify contacts annually to ensure that information is up-to-date.

### Why it matters

How quickly and methodically you contain an incident determines the regulatory consequence — most fines are not for the breach itself but for the slow or absent response.

### How to implement

#### AWS

Wire **GuardDuty**, **Security Hub** and **Macie** findings into your ticketing/SIEM via EventBridge. Maintain documented playbooks for IAM-key compromise, EC2 instance compromise, S3 data exposure, and run **quarterly tabletop exercises**.

#### Azure

Use **Defender for Cloud** + **Microsoft Sentinel** with playbooks (Logic Apps) for automated containment — disable user, isolate VM (NSG), revoke session tokens. Keep an on-call rotation in Teams with PagerDuty.

#### GitHub

Subscribe to **secret-scanning** alerts and **Dependabot** security advisories; require triage SLAs by severity. For exposed secrets, rotate at the cloud provider FIRST then revoke at GitHub — order matters.

#### On-premises

Roll out role-based security awareness annually + phishing simulations quarterly. Track completion in your LMS and tie to performance review for repeat-fails.

### Evidence to collect

-   `vendor_risk_management` — See the iCompaas Evidence library for the canonical source for this evidence type.

Third-party risk management evidence (assessments, contracts, due diligence) shows supplier oversight. Focus: Establish and Maintain Contact Information for Reporting Security Incidents.

### Quick checklist

-   Establish And Maintain — Date / Response
-   Ensure — Date / Response

### Related articles on this site

-   [Ensure security contact information is registered](https://support.icompaas.com/support/solutions/articles/62000081061-ensure-security-contact-information-is-registered)
-   [Source Code Supply Chain Security](https://support.icompaas.com/support/solutions/articles/62000225179-source-code-supply-chain-security)
-   [NIST 800-171 3.2.3 Provide security awareness training on recognizing and reporting potential indicators of insider threat.](https://support.icompaas.com/support/solutions/articles/62000229270-nist-800-171-3-2-3-provide-security-awareness-training-on-recognizing-and-reporting-potential-indicat)
-   [NIST 800-171 3.4.2 Establish and enforce security configuration settings for information technology products employed in organizational systems.](https://support.icompaas.com/support/solutions/articles/62000229281-nist-800-171-3-4-2-establish-and-enforce-security-configuration-settings-for-information-technology-p)

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