AU-16(3)—Disassociability
>Control Description
Implement ⚙organization-defined measures to disassociate individuals from audit information transmitted across organizational boundaries.
>Supplemental Guidance
Preserving identities in audit trails could have privacy ramifications, such as enabling the tracking and profiling of individuals, but may not be operationally necessary. These risks could be further amplified when transmitting information across organizational boundaries. Implementing privacy-enhancing cryptographic techniques can disassociate individuals from audit information and reduce privacy risk while maintaining accountability.
>Assessment Interview Topics
Questions assessors commonly ask
Process & Governance:
- •What formal policies and procedures govern the implementation of AU-16(3) (Disassociability)?
- •Who are the designated roles responsible for implementing, maintaining, and monitoring AU-16(3)?
- •How frequently is the AU-16(3) policy reviewed and updated, and what triggers policy changes?
- •What training or awareness programs ensure personnel understand their responsibilities related to AU-16(3)?
Technical Implementation:
- •Describe the specific technical mechanisms or controls used to enforce AU-16(3) requirements.
- •What automated tools, systems, or technologies are deployed to implement AU-16(3)?
- •How is AU-16(3) integrated into your system architecture and overall security posture?
- •What configuration settings, parameters, or technical specifications enforce AU-16(3) requirements?
Evidence & Documentation:
- •What documentation demonstrates the complete implementation of AU-16(3)?
- •What audit logs, records, reports, or monitoring data validate AU-16(3) compliance?
- •Can you provide evidence of periodic reviews, assessments, or testing of AU-16(3) effectiveness?
- •What artifacts would you present during a FedRAMP assessment to demonstrate AU-16(3) compliance?
Ask AI
Configure your API key to use AI features.