AWS Well-Architected Security Pillar SEC10-BP02: Develop incident management plans

What else in your programme already covers this

This control maps to 57 controls across 26 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

NIST Cybersecurity Framework 2.0 · 9 controls

NIST-CSF-DE.AE-08 Incidents are declared when adverse events meet the defined incident criteria
NIST-CSF-ID.IM-04 Incident response plans and other cybersecurity plans that affect operations are established, communicated, maintained, and improved
NIST-CSF-RC.RP-01 The recovery portion of the incident response plan is executed once initiated from the incident response process
NIST-CSF-RS.CO-03 Information is shared with designated internal and external stakeholders
NIST-CSF-RS.MA-01 The incident response plan is executed in coordination with relevant third parties once an incident is declared
NIST-CSF-RS.MA-02 Incident reports are triaged and validated
NIST-CSF-RS.MA-03 Incidents are categorized and prioritized
NIST-CSF-RS.MA-05 The criteria for initiating incident recovery are applied
NIST-CSF-RS.MI-02 Incidents are eradicated

FedRAMP High · 4 controls

IR-4 Incident Handling
IR-8 Incident Response Plan
IR-9 Information Spillage Response. Respond to information spills by: a. Assigning [Assignment: organization-defined personnel or roles] with responsibility for responding to information spills; b. Identifying the specific information involved in the system contamination; c. Alerting
SI-7(7) Integration of Detection and Response

FedRAMP Moderate · 4 controls

IR-4 Incident Handling
IR-8 Incident Response Plan
IR-9 Information Spillage Response. Respond to information spills by: a. Assigning [Assignment: organization-defined personnel or roles] with responsibility for responding to information spills; b. Identifying the specific information involved in the system contamination; c. Alerting
SI-7(7) Integration of Detection and Response

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 3 controls

CCM-SEF-01 Security Incident Management Policy and Procedures
CCM-SEF-03 Incident Response Plans
CCM-SEF-06 Event Triage Processes

ISO 27001:2022 · 3 controls

5.24 Information security incident management planning and preparation
5.25 Assessment and decision on information security events
5.26 Response to information security incidents

SOC 2 · 3 controls

SOC2-CC7.3 Evaluates security events to determine incident status
SOC2-CC7.4 Responds to identified security incidents through defined procedures
SOC2-CC9.1 Identifies, selects and develops risk mitigation activities

C5 (Germany) · 2 controls

C5-SIM-01 Policy for security incident management
C5-SIM-02 Processing of security incidents

CIS Controls v8 · 2 controls

CIS-17.4 Establish and Maintain an Incident Response Process
CIS-17.6 Define Mechanisms for Communicating During Incident Response

CMMC 2.0 · 2 controls

IR.L2-3.6.1 Incident Handling
IR.L2-3.6.2 Incident Reporting

ISO 27002:2022 · 2 controls

5.24 Information security incident management planning and preparation
5.26 Response to information security incidents

NIST SP 800-161 Rev 1 · 2 controls

161R1-IR-4 Incident Handling
161R1-IR-8 Incident Response Plan

NIST SP 800-171 Rev 3 · 2 controls

03.06.01 Incident Handling
03.06.05 Incident Response Plan

NIST SP 800-53 Rev 5 · 2 controls

NIST800-IR-4 Incident handling
NIST800-IR-8 Incident response plan

NIST SP 800-53 Rev 5 LOW · 2 controls

IR-4 Incident Handling
IR-8 Incident Response Plan

NIST SP 800-53 Rev 5 MODERATE · 2 controls

IR-4 Incident Handling
IR-8 Incident Response Plan

NIST SP 800-53 Revision 5.1 HIGH · 2 controls

IR-4 Incident Handling
IR-8 Incident Response Plan

PCI DSS 4.0 · 2 controls

10.7.3 Failure response timeline
12.10.1 Incident response plan

ACSC Essential Eight · 1 control

E8-ADMIN-ML2 Restrict Administrative Privileges (ML2)

ANSSI Guide d'hygiene informatique (42 mesures, v2.0) · 1 control

ANSSI-HYG-40 Define a Security Incident Management Procedure

Australia Consumer Data Right - Banking (CDR) · 1 control

AUCDR-IS-STEP5 Step 5 - Manage and report security incidents

Azure Security Benchmark · 1 control

ASBv3-IR-1 Preparation - update incident response plan and handling process

HIPAA Security Rule · 1 control

164.308(a)(6)(i) Security Incident Procedures (Standard)

ISO 27701:2019 · 1 control

6.13.1 Management of information security incidents and improvements

ISO/IEC 42001:2023 · 1 control

A.8.4 Communication of incidents

NIST SP 800-66 Rev 2 · 1 control

164.308(a)(6)(i) Security Incident Procedures (Standard)

UK Cyber Essentials · 1 control

CE-SC.8 Process for Compromised Passwords

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

You are reading one control. How much of AWS Well-Architected Security Pillar have you already done?

AWS Well-Architected Security Pillar SEC10-BP02 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of AWS Well-Architected Security Pillar your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 52 of 63 AWS Well-Architected Security Pillar controls already carry evidence.

If you hold NIST SP 800-53 Rev 582.5% covered · 11 gaps If you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.174.6% covered · 16 gaps If you hold ISO 27002:202273% covered · 17 gaps If you hold FedRAMP Moderate69.8% covered · 19 gaps If you hold Azure Security Benchmark65.1% covered · 22 gaps If you hold PCI DSS 4.063.5% covered · 23 gaps

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 0 were rejected on the NIST SP 800-53 Rev 5 pair alone.

See the released pairs, $299 each Browse the graph free