Under active development Content is continuously updated and improved

AU-16Cross-organizational Audit Logging

IL5
IL6

>Control Description

Employ organization-defined methods for coordinating organization-defined audit information among external organizations when audit information is transmitted across organizational boundaries.

>DoD Impact Level Requirements

No specific parameter values or requirements for this impact level.

>Discussion

When organizations use systems or services of external organizations, the audit logging capability necessitates a coordinated, cross-organization approach. For example, maintaining the identity of individuals who request specific services across organizational boundaries may often be difficult, and doing so may prove to have significant performance and privacy ramifications. Therefore, it is often the case that cross-organizational audit logging simply captures the identity of individuals who issue requests at the initial system, and subsequent systems record that the requests originated from authorized individuals.

Organizations consider including processes for coordinating audit information requirements and protection of audit information in information exchange agreements.

>Related Controls

>Assessment Interview Topics

Questions assessors commonly ask

Process & Governance:

  • What formal policies and procedures govern the implementation of AU-16 (Cross-Organizational Audit Logging)?
  • Who are the designated roles responsible for implementing, maintaining, and monitoring AU-16?
  • How frequently is the AU-16 policy reviewed and updated, and what triggers policy changes?
  • What training or awareness programs ensure personnel understand their responsibilities related to AU-16?

Technical Implementation:

  • Describe the specific technical mechanisms or controls used to enforce AU-16 requirements.
  • What automated tools, systems, or technologies are deployed to implement AU-16?
  • How is AU-16 integrated into your system architecture and overall security posture?
  • What configuration settings, parameters, or technical specifications enforce AU-16 requirements?

Evidence & Documentation:

  • What documentation demonstrates the complete implementation of AU-16?
  • What audit logs, records, reports, or monitoring data validate AU-16 compliance?
  • Can you provide evidence of periodic reviews, assessments, or testing of AU-16 effectiveness?
  • What artifacts would you present during a FedRAMP assessment to demonstrate AU-16 compliance?

Ask AI

Configure your API key to use AI features.