NIST SP 800-53 Rev 5
AU - Audit and Accountability

NIST SP 800-53 Rev 5 NIST800-AU-1: AU-1 Policy and Procedures

a. Develop, document, and disseminate to [Assignment: organization-defined personnel or roles]: 1. [Selection (one or more): organization-level; mission/business process-level; system-level] audit and accountability policy that: (a) Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and (b) Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and 2. Procedures to facilitate the implementation of the audit and accountability policy and the associated audit and accountability controls; b. Designate an [Assignment: organization-defined official] to manage the development, documentation, and dissemination of the audit and accountability policy and procedures; and c. Review and update the current audit and accountability: 1. Policy [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]; and 2. Procedures [Assignment: organization-defined frequency] and following [Assignment: organization-defined events].

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

What else in your programme already covers this

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

ISO 27701:2019 · 5 controls

  • 5.3.2 Policy
  • 5.5.5 Documented information
  • 6.2.1 Management direction for information security
  • 6.9.4 Logging and monitoring
  • 6.9.7 Information systems audit considerations

SOC 2 · 5 controls

  • SOC2-CC5.3 CC5.3 Deploying controls through policies and procedures (COSO principle 12)
  • SOC2-CC7.1 CC7.1 Detecting configuration changes and new vulnerabilities
  • SOC2-CC7.2 CC7.2 Monitoring system components for anomalies
  • SOC2-CC7.3 CC7.3 Evaluating security events to identify incidents
  • SOC2-CC7.4 CC7.4 Responding to security incidents

ISO 27001:2022 · 4 controls

  • 5.1 Policies for information security
  • 5.35 Independent review of information security
  • 5.36 Compliance with policies, rules and standards for information security
  • 8.15 Logging

ISO 27002:2022 · 4 controls

  • 5.1 Policies for information security
  • 5.35 Independent review of information security
  • 5.36 Compliance with policies, rules and standards for information security
  • 8.15 Logging
  • NIST-CSF-GV.PO-01 Policy for managing cybersecurity risks is established based on organizational context, cybersecurity strategy, and priorities and is communicated and enforced
  • NIST-CSF-GV.PO-02 Policy for managing cybersecurity risks is reviewed, updated, communicated, and enforced to reflect changes in requirements, threats, technology, and organizational mission
  • ASBv3-GS-7 Define and implement logging, threat detection and incident response strategy

C5 (Germany) · 1 control

CIS Controls v8 · 1 control

  • CIS-8.1 Establish and Maintain an Audit Log Management Process

CMMC 2.0 · 1 control

  • ITSG33-AU Audit and Accountability (AU)
  • CCM-LOG-01 Logging and Monitoring Policy and Procedures

FedRAMP High · 1 control

  • AU-1 Policy and Procedures

FedRAMP Moderate · 1 control

  • AU-1 Policy and Procedures
  • AU-1 AU-1 Policy and Procedures
  • AU-1 AU-1 Policy and Procedures
  • AU-1 AU-1 Policy and Procedures

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 AU - Audit and Accountability

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

NIST SP 800-53 Rev 5 NIST800-AU-1 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of NIST SP 800-53 Rev 5 your existing evidence covers. Hold ISO 27001:2022 and 163 of 1014 NIST SP 800-53 Rev 5 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. 342 were rejected on the ISO 27001:2022 pair alone.

Query this from an agent

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