Incident Monitoring
✓ LOW ✓ MODERATE ✓ HIGHRequirements NIST SOURCE
Track and document incidents.
Discussion (NIST Supplemental Guidance)
Documenting incidents includes maintaining records about each incident, the status of the incident, and other pertinent information necessary for forensics as well as evaluating incident details, trends, and handling. Incident information can be obtained from a variety of sources, including network monitoring, incident reports, incident response teams, user complaints, supply chain partners, audit monitoring, physical access monitoring, and user and administrator reports. IR-4 provides information on the types of incidents that are appropriate for monitoring.
Enhancements NIST SOURCE
IR-5(1) Automated Tracking, Data Collection, and Analysis LOW MODERATE ✓ HIGH
Track incidents and collect and analyze incident information using [organization-defined automated mechanisms].
Discussion
Automated mechanisms for tracking incidents and collecting and analyzing incident information include Computer Incident Response Centers or other electronic databases of incidents and network monitoring devices.
Implementation Guidance
Original engineering commentary written for this explorer — not NIST source text and not authoritative guidance.
No engineering interpretation has been authored for IR-5 yet. This section is architected to receive it — see the Requirements and Assessment sections above for the authoritative NIST source content in the meantime.
Assessment
Assessment Objectives
- incidents are tracked;
- incidents are documented.
Examine
[SELECT FROM: Incident response policy; procedures addressing incident monitoring; incident response records and documentation; incident response plan; system security plan; privacy plan; other relevant documents or records].
Interview
[SELECT FROM: Organizational personnel with incident monitoring responsibilities; organizational personnel with information security and privacy responsibilities].
Test
[SELECT FROM: Incident monitoring capability for the organization; mechanisms supporting and/or implementing the tracking and documenting of system security incidents].
Overlays
STIGs & CCIs
No STIG checks or CCI mappings are currently loaded for IR-5. This section is architected to display, per product: STIG ID, Finding ID, Severity, Title, Description, Check, Fix, CCI, and NIST control mapping — but nothing is populated here until a real DISA STIG/CCI dataset is ingested.
Learn more about STIG/CCI integration →Evidence
Categorized from the SP 800-53A "Examine"/"Test" artifact list above by keyword — not an authoritative NIST evidence list.
Policy
- Incident response policy
- incident response plan
- system security plan
- privacy plan
Testing
- Incident monitoring capability for the organization
- mechanisms supporting and/or implementing the tracking and documenting of system security incidents
Other Records
- procedures addressing incident monitoring
- incident response records and documentation
- other relevant documents or records