AWS Well-Architected Security Pillar
Incident Response

AWS Well-Architected Security Pillar SEC10-BP01: Identify key personnel and external resources

Maintain an up to date roster of incident responders, executives, legal, comms, AWS support contacts and external IR retainer firms with on call rotations.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 42 controls across 19 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-CSF-GV.RR-02 Roles, responsibilities, and authorities related to cybersecurity risk management are established, communicated, understood, and enforced
  • NIST-CSF-GV.SC-08 Relevant suppliers and other third parties are included in incident planning, response, and recovery activities
  • NIST-CSF-ID.IM-04 Incident response plans and other cybersecurity plans that affect operations are established, communicated, maintained, and improved
  • NIST-CSF-RC.CO-03 Recovery activities and progress in restoring operational capabilities are communicated to designated internal and external stakeholders
  • NIST-CSF-RS.CO-02 Internal and external stakeholders are notified of incidents
  • 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-04 Incidents are escalated or elevated as needed

C5 (Germany) · 3 controls

  • C5-OIS-05 Contact with Relevant Government Agencies and Interest Groups
  • C5-SIM-01 Policy for security incident management
  • C5-SIM-02 Processing of security incidents

CIS Controls v8 · 3 controls

  • CIS-17.1 Designate Personnel to Manage Incident Handling
  • CIS-17.2 Establish and Maintain Contact Information for Reporting Security Incidents
  • CIS-17.5 Assign Key Roles and Responsibilities

NIST SP 800-161 Rev 1 · 3 controls

NIST SP 800-171 Rev 3 · 3 controls

  • 03.06.02 Incident Monitoring, Reporting, and Response Assistance
  • 03.06.04 Incident Response Training
  • 03.06.05 Incident Response Plan

NIST SP 800-53 Rev 5 · 3 controls

CMMC 2.0 · 2 controls

FedRAMP High · 2 controls

  • IR-7 Incident Response Assistance
  • IR-8 Incident Response Plan

FedRAMP Moderate · 2 controls

  • IR-7 Incident Response Assistance
  • IR-8 Incident Response Plan

ISO 27001:2022 · 2 controls

  • 5.24 Information security incident management planning and preparation 
  • 5.5 Contact with authorities

ISO 27002:2022 · 2 controls

  • 5.24 Information security incident management planning and preparation
  • 5.5 Contact with authorities

PCI DSS 4.0 · 2 controls

  • 12.10.1 12.10.1 Incident response plan ready for activation
  • 12.10.3 12.10.3 Incident response personnel available 24/7
  • ANSSI-HYG-39 Designate an Information System Security Officer and Make the Role Known
  • ASBv3-IR-2 Preparation - setup incident notification

HIPAA Security Rule · 1 control

ISO 27701:2019 · 1 control

  • 6.13.1 Management of information security incidents and improvements

SOC 2 · 1 control

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.

Other controls in Incident Response

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

AWS Well-Architected Security Pillar SEC10-BP01 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.

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.

Query this from an agent

The graph holds this control, the 42 it maps to, and the evidence behind each claim, over MCP and REST.