Content of Audit Records

frameworkNIST SP 800-53 Rev 5.2 sectionAU Audit and Accountability csf 2.0PR.PS-04 topicsLogging & Audit frameworks7 3 3

Official textEnsure that audit records contain information that establishes the following:
a. What type of event occurred;
b. When the event occurred;
c. Where the event occurred;
d. Source of the event;
e. Outcome of the event; and
f. Identity of any individuals, subjects, or objects/entities associated with the event.NIST SP 800-53 Rev 5.2 control statement (public domain)

gap from 800-53 → gap to 800-53 →

Wrong or missing mapping? Report it

Equivalents of AU-3 in other frameworks
Framework	Requirement	Title	Link	Source / reason
NIST CSF 2.0	DE.AE-03 PR.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.15 A.8.17 A.5.28	Logging; Clock synchronization…	Crosswalk	Same topic: Logging & Audit NIST SP 800-53 → ISO 27001 mapping
CIS v8.1	CIS 8.2 CIS 3.14 CIS 8.1 CIS 8.3 CIS 8.4 CIS 8.5 CIS 8.7 CIS 8.8 CIS 8.10 CIS 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.1 10.3.2 10.6.1 10.5.1	Audit logs enabled and active; Logs protected from modification…	Crosswalk	Same topic: Logging & Audit 5 loosely related (not mappings) 10.3.1 Read access to logs limited to need Loosely related Only shares CSF PR.PS-04: related, not a mapping 10.3.3 Logs promptly backed up to a central server Loosely related Only shares CSF PR.PS-04: related, not a mapping 10.3.4 File-integrity monitoring on logs Loosely related Only shares CSF PR.PS-04: related, not a mapping 10.4.2.1 Review frequency set by targeted risk analysis Loosely related Only shares CSF PR.PS-04: related, not a mapping 10.6.3 Time settings protected from change Loosely related Only shares CSF PR.PS-04: related, not a mapping
CMMC	AU.L2-3.3.1 AU.L2-3.3.2 AU.L2-3.3.7	System Auditing; User Accountability…	Crosswalk	Same topic: Logging & Audit 3 loosely related (not mappings) AU.L2-3.3.3 Event Review Loosely related Only shares CSF PR.PS-04: related, not a mapping AU.L2-3.3.5 Audit Correlation Loosely related Only shares CSF PR.PS-04: related, not a mapping AU.L2-3.3.6 Reduction & Reporting Loosely related Only shares CSF PR.PS-04: related, not a mapping
HIPAA	§164.312(b)	Audit Controls	Crosswalk	Same topic: Logging & Audit 2 loosely related (not mappings) §164.308(a)(1)(ii)(D) Information System Activity Review Loosely related Only shares CSF PR.PS-04: related, not a mapping §164.308(a)(5)(ii)(C) Log-in Monitoring Loosely related 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-1509 ISM-1623 ISM-1660 ISM-1683 ISM-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 · Loosely related 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.