# NIST SP 800-53 Rev. 5 IR-5 — Incident Monitoring - Source: https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ir-5-incident-monitoring - Section: [Compliance](https://support.icompaas.com/compliance) › [NIST SP 800-53 Rev. 5 Controls](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5) › IR — Incident Response - Last updated: 2026-06-05 - Publisher: iCompaas, Inc. (https://www.icompaas.com) **NIST SP 800-53 Rev. 5**·Control `IR-5`·high·Component: **Incident Response** ## What this control requires > Track and document incidents with detailed records from sources like network monitoring, response teams, and audit logs to support forensic analysis and trend evaluation. This control supports the Incident Tracking System capability within the Incident Response family. > > — NIST SP 800-53 Rev. 5, Control IR-5 ### In plain English Track and document incidents with detailed records from sources like network monitoring, response teams, and audit logs to support forensic analysis and trend evaluation. In practice, this means you can prove you audit management-level controls on a defined cadence. ## Why it matters SP 800-53 is the catalogue every U.S. federal authorisation (FedRAMP, FISMA, CMMC) and most regulated industries point at. A missing control surfaces as a Plan of Action & Milestones (POA&M) item that an Authorizing Official must approve before the Authority To Operate is granted or renewed. This control is rated **high**. Auditors expect a named owner, a remediation SLA, and a tooling artefact that evidences continuous operation. ## What an auditor looks for A 3PAO (FedRAMP) or Independent Assessor (NIST RMF) tests against NIST SP 800-53A assessment procedures. For each control they expect a documented implementation that addresses every assessment objective (Examine, Interview, Test) and an implementation summary in the System Security Plan. Within **Incident Response**, the assessor will trace your implementation back to the catalogue reference (Control IR-5) and look for objective evidence on the latest two assessment cycles. ## How to implement #### Incident Response **Runbook.** Maintain a runbook keyed by incident type with named roles (IC, comms, scribe), an out-of-band comms channel, and a 72-hour timeline for external notification. **Tabletop.** Run a quarterly tabletop exercise (ransomware, insider, supply-chain) and feed gaps back into the runbook. #### Logging Monitoring **AWS.** Org-trail CloudTrail to a central log archive account, GuardDuty in every region, and Security Hub for cross-source correlation. **Azure.** Pipe every diagnostic setting into a central Log Analytics workspace; onboard Microsoft Sentinel for SIEM/SOAR. **GCP.** Aggregate audit logs in a dedicated logging project with sink to BigQuery; enable Security Command Center Premium and route findings to Chronicle SIEM. ### Operational checklist - **Audit.** Document the trigger, the owner and the cadence. - **Network.** Document the trigger, the owner and the cadence. - **Response.** Document the trigger, the owner and the cadence. - **System.** Document the trigger, the owner and the cadence. - **Control.** Document the trigger, the owner and the cadence. - **Scope:** management, system, incidents, records, analysis, sources, capability, response. ## Evidence to collect - **Ticketing Workflow.** `ticketing_workflow` evidence - **Infra Scan.** Continuous infrastructure-posture telemetry — AWS Config, Azure Policy compliance, GCP Organisation Policy, Wiz / Prisma findings. Workflow metrics (ServiceNow, Jira) show approvals and remediation. Focus: Incident Monitoring. ## Common pitfalls - Runbooks that name a role but no person, or list a paging channel that no longer exists. - Per-account logging that nobody stitches together at the org level — incidents that cross accounts go undetected for days. ## How it maps to other frameworks Computed from shared tags, control component and key-operation subjects — handy when you are reconciling controls across an audit. - [**NIST SP 800-171 Rev. 3 3.6.2** — Incident Monitoring, Reporting, and Response Assistance](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-6-2-incident-monitoring-reporting-and-response-assistance) - [**SOC 2 (2017 TSC) CC7.4** — Incident Response](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/cc7-4-incident-response) - [**BSI C5:2020 OPS-15** — Logging and Monitoring - Accountability](https://support.icompaas.com/compliance/bsi-c5-2020/ops-15-logging-and-monitoring-accountability) - [**ISO/IEC 27001:2022 A.5.27** — Learning from information security incidents](https://support.icompaas.com/compliance/iso-27001-2022/a-5-27-learning-from-information-security-incidents) ## Related controls in NIST SP 800-53 Rev. 5 - [**Control IR-10** — Integrated Information Security Analysis Team](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ir-10-integrated-information-security-analysis-team) - [**Control IR-4(15)** — Public Relations And Reputation Repair](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ir-4-15-public-relations-and-reputation-repair) - [**Control IR-4(11)** — Integrated Incident Response Team](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ir-4-11-integrated-incident-response-team) - [**Control IR-6(2)** — Vulnerabilities Related To Incidents](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ir-6-2-vulnerabilities-related-to-incidents) - [**Control AU-2** — Event Logging](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/au-2-event-logging) - [**Control IR-4** — Incident Handling](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ir-4-incident-handling) ## References - [NIST Computer Security Resource Center — NIST SP 800-53 Rev. 5](https://csrc.nist.gov/Projects/risk-management/sp800-53-controls) - Catalogue identifier: `Control IR-5` Topics: logging monitoringincident responsechange managementcontinuous monitoring ## Related compliance guidance - [NIST SP 800-53 Rev. 5: a practical implementation guide for cloud teams](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5): Start with the full NIST SP 800-53 implementation guide — scope, roadmap, evidence and how the assessment runs. - [NIST SP 800-171 and CMMC: a practical guide to protecting CUI in the cloud](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3): If your obligation is protecting CUI in your own systems for a federal or defence contract, this derived subset — not the full catalogue — is the requirement. - [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Most commercial SaaS already hold a SOC 2 Type 2, and FedRAMP 20x Class A is designed for providers that have one.