Incident Communication
What is Incident Communication?
The structured process of informing stakeholders, regulators, affected parties, and the public about security incidents according to defined protocols.
Terms that appear alongside incident communication
Each of these is named in at least one of the same controls as incident communication. The number is how many controls name both.
- post incident review 3 shared controls
- incident response 3 shared controls
- lessons learned 3 shared controls
- remediation 2 shared controls
- cyber threat 2 shared controls
- threat modeling 2 shared controls
- business continuity 2 shared controls
- incident reporting 2 shared controls
Frameworks that govern incident communication
What the standards actually require on incident communication
Requirements naming incident communication across 5 standards, quoted from the control text.
Incident communication. Article 31 requires AI agents to communicate serious security incidents to the competent authority, including risks to life, safety, critical infrastructure or fundamental rights.
BRAI-A31 · Communication of serious security incidents →HKMA C-RAF Domain 5 RESPONSE AND RECOVERY + Domain 6 SITUATIONAL AWARENESS. DOMAIN 5 RESPONSE AND RECOVERY (3 sub-areas): (1) INCIDENT RESPONSE PLANNING - documented IR plan + playbooks + runbooks + RACI + escalation criteria + decision trees + communication p...
HKMA-CRAF-Domain5-6-Response-Recovery-SitAwareness · HKMA C-RAF Domain 5 (Response and Recovery) + Domain 6 (Situational Awareness) - Incident Response, Recovery, Threat Landscape, Information Sharing →HKMA TM-G-1 Cyber + Audit + Outsourcing + Cloud. (1) SECURITY MONITORING AND SIEM (TM-G-1.7.1) - SIEM + SOC + 24x7 monitoring + log management + correlation + use cases + alert handling + escalation + UEBA + behavior analytics + SOAR automation + threat detect...
HKMA-TMG1-Cyber-Monitoring-Threat-Intel-IR-Audit-Outsource-Cloud · TM-G-1 Security Monitoring + SIEM + Threat Intel + Cyber IR + Audit + Outsourcing + Cloud Computing Risk →UR E26 Goals 4 (Respond) + 5 (Recover) require incident response + recovery capabilities. Incident Response Plan (IRP) covers: detection triggers + classification (safety-impact + business-impact);
IACS-UR-E26-Respond-Recover-IncidentResponse-Recovery-Backup-Lessons · IACS UR E26 Respond + Recover Goals - Incident Response + Communication + Recovery + Backup + Lessons Learned →Maintain API performance per Operational Guidelines including 99.5% minimum availability + p95 latency under 1.5 seconds + p99 latency under 3 seconds + throughput targets per tier + reporting of all API operations metrics monthly to CBN.
NGOB-4 · API Performance, Availability, and Service Level →Questions people ask about incident communication
What is Incident Communication?
Why is Incident Communication important for compliance?
Which compliance frameworks address Incident Communication?
Where can I learn more about Incident Communication?
See how Incident Communication applies across compliance frameworks
Our platform maps 686 frameworks with 311K cross-framework control mappings. Explore how this concept is addressed across standards.