800-53 · AU Audit and Accountability
AU-2
Event Logging
frameworkNIST SP 800-53 Rev 5.2
sectionAU Audit and Accountability
csf 2.0PR.PS-04
topicsLogging & Audit
frameworks7 3 3
Official texta. Identify the types of events that the system is capable of logging in support of the audit function: [Assignment: organization-defined event types];
b. Coordinate the event logging function with other organizational entities requiring audit-related information to guide and inform the selection criteria for events to be logged;
c. Specify the following event types for logging within the system: [Assignment: organization-defined organization-defined event types (subset of the event types defined in [AU-2a.](#au-2_smt.a)) along with the frequency of (or situation requiring) logging for each identified event type];
d. Provide a rationale for why the event types selected for logging are deemed to be adequate to support after-the-fact investigations of incidents; and
e. Review and update the event types selected for logging [Assignment: organization-defined frequency].NIST SP 800-53 Rev 5.2 control statement (public domain)
b. Coordinate the event logging function with other organizational entities requiring audit-related information to guide and inform the selection criteria for events to be logged;
c. Specify the following event types for logging within the system: [Assignment: organization-defined organization-defined event types (subset of the event types defined in [AU-2a.](#au-2_smt.a)) along with the frequency of (or situation requiring) logging for each identified event type];
d. Provide a rationale for why the event types selected for logging are deemed to be adequate to support after-the-fact investigations of incidents; and
e. Review and update the event types selected for logging [Assignment: organization-defined frequency].NIST SP 800-53 Rev 5.2 control statement (public domain)
Wrong or missing mapping? Report it
| Framework | Requirement | Title | Link | Source / reason |
|---|---|---|---|---|
| NIST CSF 2.0 | DE.AE-03PR.PS-04 | Information is correlated from multiple sources; Log records are generated and made available for continuous monitoring | Crosswalk | Same topic: Logging & Audit |
| ISO 27001 | A.8.15A.8.17 | Logging; Clock synchronization | Crosswalk | Same topic: Logging & Audit |
| CIS v8.1 | CIS 8.2CIS 3.14CIS 8.1CIS 8.3CIS 8.4CIS 8.5CIS 8.7CIS 8.8CIS 8.10CIS 8.12 | Collect Audit Logs; Log Sensitive Data Access… | Crosswalk | Same topic: Logging & Audit |
| SOC 2 | CC7.2 | Monitoring system components for anomalies | Editorial | Same topic: Logging & Audit (editorial pick) |
| PCI DSS | 10.2.110.3.210.6.110.5.1 | Audit logs enabled and active; Logs protected from modification… | Crosswalk | Same topic: Logging & Audit5 loosely related (not mappings)10.4.2.1 Review frequency set by targeted risk analysis Only shares CSF PR.PS-04: related, not a mapping |
| CMMC | AU.L2-3.3.1AU.L2-3.3.2AU.L2-3.3.7AU.L2-3.3.3 | System Auditing; User Accountability… | Crosswalk | Same topic: Logging & Audit NIST SP 800-171r2 Appendix D 2 loosely related (not mappings) |
| HIPAA | §164.312(b) | Audit Controls | Crosswalk | Same topic: Logging & Audit2 loosely related (not mappings)§164.308(a)(1)(ii)(D) Information System Activity Review Only shares CSF PR.PS-04: related, not a mapping |
| GDPR | — | No requirement | No mapping in our data | No mapping in our data (only GDPR's security articles are mapped, editorially). |
| NIS2 | 3.2 | Monitoring and logging | Crosswalk | Same topic: Logging & Audit |
| Essential Eight | ISM-1509ISM-1623ISM-1660ISM-1683ISM-1815 | Privileged access events are centrally logged; PowerShell module logging, script block logging and transcription events are centrally…… | Editorial | Same topic: Logging & Audit (editorial pick) |
| DORA | Art.10(3) | Detection | Editorial | Same topic: Logging & Audit (editorial pick) |
| CPS 234 | — | No requirement | No mapping in our data | No mapping in our data (CPS 234 is principles-based and its links are editorial). |
| Cyber Essentials | — | No requirement | No mapping in our data | No mapping in our data (Cyber Essentials covers five technical controls only). |
Crosswalk a published crosswalk (NIST, ENISA, CIS, PCI SSC) makes the link · Editorial ControlMapping's judgement where no crosswalk exists; the reason is shown · only shares a CSF 2.0 outcome: worth checking, not a mapping · No mapping in our data nothing mapped in our data; often new work, but check the coverage notes. How links are sourced.