FedRAMP Moderate
IR - Incident Response

FedRAMP Moderate IR-7(1): Incident Response Assistance | Automation Support for Availability of Information and Support (IR-7(1))

Incident Response Assistance | Automation Support for Availability of Information and Support. Increase the availability of incident response information and support using [Assignment: organization-defined automated mechanisms]

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

What else in your programme already covers this

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

CIS Controls v8 · 4 controls

  • CIS-13.1 Centralize Security Event Alerting
  • CIS-13.6 Collect Network Traffic Flow Logs
  • CIS-17.4 Establish and Maintain an Incident Response Process
  • CIS-8.9 Centralize Audit Logs

ISO 27001:2022 · 4 controls

  • 5.24 Information security incident management planning and preparation 
  • 5.26 Response to information security incidents
  • 8.15 Logging
  • 8.16 Monitoring activities

ISO 27002:2022 · 4 controls

  • 5.24 Information security incident management planning and preparation
  • 5.26 Response to information security incidents
  • 8.15 Logging
  • 8.16 Monitoring activities
  • NIST-CSF-DE.AE-06 Information on adverse events is provided to authorized staff and tools
  • NIST-CSF-RS.AN-07 Incident data and metadata are collected, and their integrity and provenance are preserved
  • 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

PCI DSS 4.0 · 4 controls

  • 10.4.1.1 10.4.1.1 Automated mechanisms used for audit log review
  • 11.5.1 11.5.1 IDS/IPS monitoring of CDE traffic
  • 12.10.1 12.10.1 Incident response plan ready for activation
  • 12.10.5 12.10.5 Plan covers alerts from security monitoring systems

SOC 2 · 4 controls

  • SOC2-A1.3 A1.3 Testing recovery plan procedures
  • SOC2-CC7.1 CC7.1 Detecting configuration changes and new vulnerabilities
  • SOC2-CC7.3 CC7.3 Evaluating security events to identify incidents
  • SOC2-CC7.4 CC7.4 Responding to security incidents
  • ASBv3-IR-6 Containment, eradication and recovery - automate the incident handling

NIST SP 800-172 · 1 control

  • 3.6.1e Establish Security Operations Center (SOC)
  • IR-7(1) IR-7(1) Incident Response Assistance | Automation Support for Availability of Information and Support
  • IR-7(1) IR-7(1) Incident Response Assistance | Automation Support for Availability of Information and Support

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 IR - Incident Response

You are reading one control. How much of FedRAMP Moderate have you already done?

FedRAMP Moderate IR-7(1) is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of FedRAMP Moderate your existing evidence covers. Hold ISO 27002:2022 and 182 of 323 FedRAMP Moderate 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. 348 were rejected on the ISO 27002:2022 pair alone.

Query this from an agent

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