Auditing Capability for Significant Events
LOW MODERATE HIGHRequirements NIST SOURCE
Upon detection of a potential integrity violation, provide the capability to audit the event and initiate the following actions: [one of: generate an audit record; alert current user; alert; ].
Discussion (NIST Supplemental Guidance)
Organizations select response actions based on types of software, specific software, or information for which there are potential integrity violations.
Implementation Guidance
Original engineering commentary written for this explorer — not NIST source text and not authoritative guidance.
No engineering interpretation has been authored for SI-7(8) 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
- one or more of the following PARAMETER VALUES is/are selected: {generate an audit record; alert current user; alert <SI-07(08)_ODP[02] personnel or roles>; <SI-07(08)_ODP[03] other actions>};
- personnel or roles to be alerted upon the detection of a potential integrity violation is/are defined (if selected);
- other actions to be taken upon the detection of a potential integrity violation are defined (if selected);
- the capability to audit an event upon the detection of a potential integrity violation is provided;
- <SI-07(08)_ODP[01] SELECTED PARAMETER VALUES> is/are initiated upon the detection of a potential integrity violation.
Examine
[SELECT FROM: System and information integrity policy; system and information integrity procedures; procedures addressing software, firmware, and information integrity; system design documentation; system configuration settings and associated documentation; integrity verification tools and associated documentation; records of integrity scans; incident response records; list of security-relevant changes to the system; automated tools supporting alerts and notifications if unauthorized security changes are detected; system audit records; system security plan; other relevant documents or records].
Interview
[SELECT FROM: Organizational personnel responsible for software, firmware, and/or information integrity; organizational personnel with information security responsibilities; system/network administrators; system developer].
Test
[SELECT FROM: Software, firmware, and information integrity verification tools; mechanisms supporting and/or implementing the capability to audit potential integrity violations; mechanisms supporting and/or implementing alerts about potential integrity violations].
Overlays
STIGs & CCIs
No STIG checks or CCI mappings are currently loaded for SI-7(8). 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
- System and information integrity policy
- system security plan
Configuration
- system design documentation
- system configuration settings and associated documentation
Testing
- Software, firmware, and information integrity verification tools
- mechanisms supporting and/or implementing the capability to audit potential integrity violations
- mechanisms supporting and/or implementing alerts about potential integrity violations
Other Records
- system and information integrity procedures
- procedures addressing software, firmware, and information integrity
- integrity verification tools and associated documentation
- records of integrity scans
- incident response records
- list of security-relevant changes to the system
- automated tools supporting alerts and notifications if unauthorized security changes are detected
- system audit records
- other relevant documents or records