| name | SA-15(13)_logging-syntax |
| description | Require the developer of the system or system component to minimize the use of personally identifiable information in development and test environment |
| category | configuration |
| version | 5.2.0 |
| author | cyberstrike-official |
| tags | ["nist","sp800-53","rev5","sa-15-13","sa","enhancement"] |
| tech_stack | ["any"] |
| cwe_ids | ["CWE-16"] |
| chains_with | ["AU-2","AU-3","IR-4","IR-8","SA-5"] |
| prerequisites | ["SA-15"] |
| severity_boost | {"AU-2":"Chain with AU-2 for comprehensive security coverage","AU-3":"Chain with AU-3 for comprehensive security coverage","IR-4":"Chain with IR-4 for comprehensive security coverage"} |
SA-15(13) Logging Syntax
Enhancement of: SA-15
High-Level Description
Family: System and Services Acquisition (SA)
Framework: NIST SP 800-53 Rev 5
In support of better incident response and the ability to more quickly reconstruct security-related actions, identifying specific requirements for secure logging facilitates the ability to connect application-produced audit event logs with operational data. Event types are consistent with the event types defined in AU-02.
What to Check
How to Test
Step 1: Review Documentation
Examine the System Security Plan (SSP) and related artifacts for SA-15(13) 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
| Tool | Purpose | Usage |
|---|
| Manual Review | Documentation and interview-based | N/A |
Remediation Guide
Control Statement
Require the developer of the system or system component to minimize the use of personally identifiable information in development and test environments.
Implementation Guidance
In support of better incident response and the ability to more quickly reconstruct security-related actions, identifying specific requirements for secure logging facilitates the ability to connect application-produced audit event logs with operational data. Event types are consistent with the event types defined in AU-02.
Risk Assessment
