NIST SP 800-171 Rev 3
03.03 AU (Audit and Accountability)

NIST SP 800-171 Rev 3 03.03.01: Event Logging

Specify event types to be logged; coordinate logging across system components; review event types periodically.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 42 controls across 23 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

PCI DSS 4.0 · 6 controls

  • 10.2.1 10.2.1 Audit logging enabled on all system components
  • 10.2.1.1 10.2.1.1 Logs capture individual user access to cardholder data
  • 10.2.1.4 10.2.1.4 Logs capture invalid logical access attempts
  • 10.2.1.5 10.2.1.5 Logs capture changes to identification and authentication credentials
  • 10.2.1.7 10.2.1.7 Logs capture creation and deletion of system-level objects
  • 5.3.4 5.3.4 Anti-malware audit logs enabled and retained
  • ASBv3-DS-7 Enable logging and monitoring in DevOps
  • ASBv3-GS-7 Define and implement logging, threat detection and incident response strategy
  • ASBv3-IR-4 Detection and analysis - investigate an incident
  • LT-3 Enable logging for security investigation
  • LT-4 Enable network logging for security investigation

CIS Controls v8 · 5 controls

  • CIS-3.14 Log Sensitive Data Access
  • CIS-8.1 Establish and Maintain an Audit Log Management Process
  • CIS-8.2 Collect Audit Logs
  • CIS-8.5 Collect Detailed Audit Logs
  • CIS-8.9 Centralize Audit Logs
  • ANSSI-HYG-22 Put in Place a Secure Internet Access Gateway
  • ANSSI-HYG-36 Enable and Configure Logging on the Most Important Components
  • SEC04-BP01 Configure service and application logging
  • SEC04-BP02 Capture logs, findings, and metrics in standardized locations

C5 (Germany) · 2 controls

  • C5-OPS-10 Logging and Monitoring - Concept
  • C5-OPS-13 Logging and Monitoring - Identification of Events

CMMC 2.0 · 2 controls

SOC 2 · 2 controls

  • SOC2-CC2.1 CC2.1 Relevant, quality information to support internal control (COSO principle 13)
  • SOC2-CC7.2 CC7.2 Monitoring system components for anomalies
  • E8-UAH-ML3 User Application Hardening - Maturity Level 3
  • AUCDR-IS-1 Limit risk of unauthorised access to the CDR data environment

FedRAMP High · 1 control

FedRAMP Moderate · 1 control

HIPAA Security Rule · 1 control

ISO 27001:2022 · 1 control

ISO 27002:2022 · 1 control

ISO 27018:2019 · 1 control

ISO 27701:2019 · 1 control

  • 6.9.4 Logging and monitoring

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in 03.03 AU (Audit and Accountability)

You are reading one control. How much of NIST SP 800-171 Rev 3 have you already done?

NIST SP 800-171 Rev 3 03.03.01 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of NIST SP 800-171 Rev 3 your existing evidence covers. Hold PCI DSS 4.0 and 69 of 97 NIST SP 800-171 Rev 3 controls already carry evidence.

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 0 were rejected on the PCI DSS 4.0 pair alone.

Query this from an agent

The graph holds this control, the 42 it maps to, and the evidence behind each claim, over MCP and REST.