Skip to main content
MuonPartners
Services
Architecture

Solution design and technology roadmapping

Solution AssessmentTechnology RoadmapsIntegration DesignSolution ArchitectureTechnical Design
Cyber Security

Security assessments, IAM, and compliance

AssessmentsIAMComplianceSecurity BaselineCyber Innovation
Network and Platform

Network architecture and cloud platforms

Network DesignCloud StrategyModernisation
Enterprise Architecture

Business-technology alignment

Business AlignmentPortfolio AnalysisGovernance
View all services
ProjectsCase StudiesInsightsToolsAbout
Contact Us

Services

Architecture
Solution AssessmentTechnology RoadmapsIntegration DesignSolution ArchitectureTechnical Design
Cyber Security
AssessmentsIAMComplianceSecurity BaselineCyber Innovation
Network and Platform
Network DesignCloud StrategyModernisation
Enterprise Architecture
Business AlignmentPortfolio AnalysisGovernance
ProjectsCase StudiesInsightsToolsAboutContact
Get in Touch
MuonPartners

Strategic technology consulting for Australian organisations navigating complexity.

Services

  • Architecture
  • Cyber Security
  • Network and Platform
  • Enterprise Architecture

Company

  • About
  • Products
  • Frameworks
  • Cross-Framework Mapping
  • Projects
  • Case Studies
  • Insights
  • Contact

Contact

  • [email protected]
  • Australia
  • LinkedIn

© 2026 Muon Partners. All rights reserved.

ABN 50 669 022 315 · A Muon Group company.

Privacy PolicyTerms of Service
  1. Frameworks
  2. >SP 800-53
  3. >Audit And Accountability
  4. >SP800-53-AU-2
SP800-53-AU-2Active

Event Logging

Statement

Identify the types of events that the system is capable of logging in support of the audit function: event types; 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; Specify the following event types for logging within the system: event types; event types (subset of AU-02_ODP[01]); frequency or situation; frequency; 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 Review and update the event types selected for logging frequency.

Location

Control Family
Audit and Accountability

Control Details

Identifier
SP800-53-AU-2
Family
AU

Organisation-Defined Parameters

au-02_odp.01
event types
au-02_odp.02
event types (subset of AU-02_ODP[01])
au-02_odp.03
frequency or situation
au-02_odp.04
frequency

Supplemental Guidance

An event is an observable occurrence in a system. The types of events that require logging are those events that are significant and relevant to the security of systems and the privacy of individuals. Event logging also supports specific monitoring and auditing needs. Event types include password changes, failed logons or failed accesses related to systems, security or privacy attribute changes, administrative privilege usage, PIV credential usage, data action changes, query parameters, or external credential usage. In determining the set of event types that require logging, organizations consider the monitoring and auditing appropriate for each of the controls to be implemented. For completeness, event logging includes all protocols that are operational and supported by the system.

To balance monitoring and auditing requirements with other system needs, event logging requires identifying the subset of event types that are logged at a given point in time. For example, organizations may determine that systems need the capability to log every file access successful and unsuccessful, but not activate that capability except for specific circumstances due to the potential burden on system performance. The types of events that organizations desire to be logged may change. Reviewing and updating the set of logged events is necessary to help ensure that the events remain relevant and continue to support the needs of the organization. Organizations consider how the types of logging events can reveal information about individuals that may give rise to privacy risk and how best to mitigate such risks. For example, there is the potential to reveal personally identifiable information in the audit trail, especially if the logging event is based on patterns or time of usage.

Event logging requirements, including the need to log specific event types, may be referenced in other controls and control enhancements. These include AC-2(4), AC-3(10), AC-6(9), AC-17(1), CM-3f, CM-5(1), IA-3(3)(b), MA-4(1), MP-4(2), PE-3, PM-21, PT-7, RA-8, SC-7(9), SC-7(15), SI-3(8), SI-4(22), SI-7(8) , and SI-10(1) . Organizations include event types that are required by applicable laws, executive orders, directives, policies, regulations, standards, and guidelines. Audit records can be generated at various levels, including at the packet level as information traverses the network. Selecting the appropriate level of event logging is an important part of a monitoring and auditing capability and can identify the root causes of problems. When defining event types, organizations consider the logging necessary to cover related event types, such as the steps in distributed, transaction-based processes and the actions that occur in service-oriented architectures.

Assessment Objective

event types that the system is capable of logging are identified in support of the audit logging function; the event logging function is coordinated with other organizational entities requiring audit-related information to guide and inform the selection criteria for events to be logged; event types (subset of AU-02_ODP[01]) are specified for logging within the system; the specified event types are logged within the system frequency or situation; a rationale is provided for why the event types selected for logging are deemed to be adequate to support after-the-fact investigations of incidents; the event types selected for logging are reviewed and updated frequency.

ATTACK
ATTACK-T1556.006relatedvia ctid-attack-to-sp800-53
ATTACK-T1556.007relatedvia ctid-attack-to-sp800-53
View in graphReport an issue
← Back to Audit and Accountability
Audit and Accountability69 controls
SP800-53-AU-1Policy and ProceduresSP800-53-AU-2Event LoggingSP800-53-AU-2(1)Compilation of Audit Records from Multiple SourcesSP800-53-AU-2(2)Selection of Audit Events by ComponentSP800-53-AU-2(3)Reviews and UpdatesSP800-53-AU-2(4)Privileged FunctionsSP800-53-AU-3Content of Audit RecordsSP800-53-AU-3(1)Additional Audit InformationSP800-53-AU-3(2)Centralized Management of Planned Audit Record ContentSP800-53-AU-3(3)Limit Personally Identifiable Information ElementsSP800-53-AU-4Audit Log Storage CapacitySP800-53-AU-4(1)Transfer to Alternate StorageSP800-53-AU-5Response to Audit Logging Process FailuresSP800-53-AU-5(1)Storage Capacity WarningSP800-53-AU-5(2)Real-time AlertsSP800-53-AU-5(3)Configurable Traffic Volume ThresholdsSP800-53-AU-5(4)Shutdown on FailureSP800-53-AU-5(5)Alternate Audit Logging CapabilitySP800-53-AU-6Audit Record Review, Analysis, and ReportingSP800-53-AU-6(1)Automated Process IntegrationSP800-53-AU-6(2)Automated Security AlertsSP800-53-AU-6(3)Correlate Audit Record RepositoriesSP800-53-AU-6(4)Central Review and AnalysisSP800-53-AU-6(5)Integrated Analysis of Audit RecordsSP800-53-AU-6(6)Correlation with Physical MonitoringSP800-53-AU-6(7)Permitted ActionsSP800-53-AU-6(8)Full Text Analysis of Privileged CommandsSP800-53-AU-6(9)Correlation with Information from Nontechnical SourcesSP800-53-AU-6(10)Audit Level AdjustmentSP800-53-AU-7Audit Record Reduction and Report GenerationSP800-53-AU-7(1)Automatic ProcessingSP800-53-AU-7(2)Automatic Sort and SearchSP800-53-AU-8Time StampsSP800-53-AU-8(1)Synchronization with Authoritative Time SourceSP800-53-AU-8(2)Secondary Authoritative Time SourceSP800-53-AU-9Protection of Audit InformationSP800-53-AU-9(1)Hardware Write-once MediaSP800-53-AU-9(2)Store on Separate Physical Systems or ComponentsSP800-53-AU-9(3)Cryptographic ProtectionSP800-53-AU-9(4)Access by Subset of Privileged UsersSP800-53-AU-9(5)Dual AuthorizationSP800-53-AU-9(6)Read-only AccessSP800-53-AU-9(7)Store on Component with Different Operating SystemSP800-53-AU-10Non-repudiationSP800-53-AU-10(1)Association of IdentitiesSP800-53-AU-10(2)Validate Binding of Information Producer IdentitySP800-53-AU-10(3)Chain of CustodySP800-53-AU-10(4)Validate Binding of Information Reviewer IdentitySP800-53-AU-10(5)Digital SignaturesSP800-53-AU-11Audit Record RetentionSP800-53-AU-11(1)Long-term Retrieval CapabilitySP800-53-AU-12Audit Record GenerationSP800-53-AU-12(1)System-wide and Time-correlated Audit TrailSP800-53-AU-12(2)Standardized FormatsSP800-53-AU-12(3)Changes by Authorized IndividualsSP800-53-AU-12(4)Query Parameter Audits of Personally Identifiable InformationSP800-53-AU-13Monitoring for Information DisclosureSP800-53-AU-13(1)Use of Automated ToolsSP800-53-AU-13(2)Review of Monitored SitesSP800-53-AU-13(3)Unauthorized Replication of InformationSP800-53-AU-14Session AuditSP800-53-AU-14(1)System Start-upSP800-53-AU-14(2)Capture and Record ContentSP800-53-AU-14(3)Remote Viewing and ListeningSP800-53-AU-15Alternate Audit Logging CapabilitySP800-53-AU-16Cross-organizational Audit LoggingSP800-53-AU-16(1)Identity PreservationSP800-53-AU-16(2)Sharing of Audit InformationSP800-53-AU-16(3)Disassociability