# ISO/IEC 27701 A.3.12 — Response to incidents

- Source: https://support.icompaas.com/support/solutions/articles/a_gen_iso27701_a312_6361ebf466-isoiec-27701-a312-response-to-incidents
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [ISO/IEC 27701 (Privacy Information Management)](https://support.icompaas.com/support/solutions/c_gen_iso27701) › [Security considerations](https://support.icompaas.com/support/solutions/folders/f_gen_cgeniso27701_securityconsiderations)
- Last updated: 2026-05-30
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

ISO/IEC 27701 · Control A.3.12 · Priority: critical · Component: Security considerations

### What this control covers

Respond to incidents related to PII according to documented procedures. Implementation: Implement response steps, notification templates and forensic logging. Justification: Proper response includes notification, mitigation and recordkeeping.

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

#### GCP

Use **Cloud KMS** with customer-managed encryption keys (CMEK) for BigQuery, GCS, and Compute. **Sensitive Data Protection** (DLP API) inspects/de-identifies PII at scale.

#### Google Workspace

Enable **client-side encryption** for Drive/Docs and turn on **Drive Labels + DLP** rules to prevent external sharing of regulated data classes.

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

### Evidence to collect

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

Signed policies, procedures, and registers document the safeguard. Service management or request-handling tickets prove timely handling. Focus: Response to incidents.

### Quick checklist

-   Implement — Response To Incidents
-   Document — Response To Incidents
-   Log — Response To Incidents

### Related articles on this site

-   [NIST 800-171 3.3.4 Alert in the event of an audit logging process failure.](https://support.icompaas.com/support/solutions/articles/62000229274-nist-800-171-3-3-4-alert-in-the-event-of-an-audit-logging-process-failure-)
-   [NIST 800-171 3.6.1 Establish an operational incident-handling capability for organizational systems that includes preparation, detection, analysis, containment, recovery, and user response activities.](https://support.icompaas.com/support/solutions/articles/62000229301-nist-800-171-3-6-1-establish-an-operational-incident-handling-capability-for-organizational-systems-t)
-   [CMMC 2.0 AU.3.046 Alert in the event of an audit logging process failure.](https://support.icompaas.com/support/solutions/articles/62000229434-cmmc-2-0-au-3-046-alert-in-the-event-of-an-audit-logging-process-failure-)
-   [CMMC 2.0 IR.2.092 Establish an operational incident-handling capability for organizational systems that includes preparation, detection, analysis, containment, recovery, and user response activities.](https://support.icompaas.com/support/solutions/articles/62000229547-cmmc-2-0-ir-2-092-establish-an-operational-incident-handling-capability-for-organizational-systems-th)