| name | PT-5_privacy-notice |
| description | Provide notice to individuals about the processing of personally identifiable information that: Is available to individuals upon first interacting wit |
| category | configuration |
| version | 5.2.0 |
| author | cyberstrike-official |
| tags | ["nist","sp800-53","rev5","pt-5","pt"] |
| tech_stack | ["any"] |
| cwe_ids | ["CWE-359"] |
| chains_with | ["PM-20","PM-22","PT-2","PT-3","PT-4","PT-7","RA-3","SC-42","SI-18"] |
| prerequisites | [] |
| severity_boost | {"PM-20":"Chain with PM-20 for comprehensive security coverage","PM-22":"Chain with PM-22 for comprehensive security coverage","PT-2":"Chain with PT-2 for comprehensive security coverage"} |
PT-5 Privacy Notice
High-Level Description
Family: Personally Identifiable Information Processing and Transparency (PT)
Framework: NIST SP 800-53 Rev 5
Privacy notices help inform individuals about how their personally identifiable information is being processed by the system or organization. Organizations use privacy notices to inform individuals about how, under what authority, and for what purpose their personally identifiable information is processed, as well as other information such as choices individuals might have with respect to that processing and other parties with whom information is shared. Laws, executive orders, directives, regulations, or policies may require that privacy notices include specific elements or be provided in specific formats. Federal agency personnel consult with the senior agency official for privacy and legal counsel regarding when and where to provide privacy notices, as well as elements to include in privacy notices and required formats. In circumstances where laws or government-wide policies do not require privacy notices, organizational policies and determinations may require privacy notices and may serve as a source of the elements to include in privacy notices.
Privacy risk assessments identify the privacy risks associated with the processing of personally identifiable information and may help organizations determine appropriate elements to include in a privacy notice to manage such risks. To help individuals understand how their information is being processed, organizations write materials in plain language and avoid technical jargon.
What to Check
How to Test
Step 1: Review Documentation
Examine the System Security Plan (SSP) and related artifacts for PT-5 implementation details. Verify the organization has documented how this control is satisfied.
Step 2: Validate Implementation
# For cloud environments, use cloud-audit-mcp tools
# For on-premises, review system configurations directly
# Example: Check if account management policies exist
grep -r "account.management\|access.control" /etc/security/ 2>/dev/null
Step 3: Test Operating Effectiveness
Verify the control is actively functioning, not just documented. Check logs, configurations, and operational evidence.
Tools
