| name | SC-20_secure-nameaddress-resolution-service-authoritative-source |
| description | Provide additional data origin authentication and integrity verification artifacts along with the authoritative name resolution data the system ret... |
| category | configuration |
| version | 5.2.0 |
| author | cyberstrike-official |
| tags | ["nist","sp800-53","rev5","sc-20","sc"] |
| tech_stack | ["aws","azure","gcp","linux","windows","network"] |
| cwe_ids | ["CWE-311"] |
| chains_with | ["AU-10","SC-8","SC-12","SC-13","SC-21","SC-22"] |
| prerequisites | [] |
| severity_boost | {"AU-10":"Chain with AU-10 for comprehensive security coverage","SC-8":"Chain with SC-8 for comprehensive security coverage","SC-12":"Chain with SC-12 for comprehensive security coverage"} |
SC-20 Secure Name/Address Resolution Service (Authoritative Source)
High-Level Description
Family: System and Communications Protection (SC)
Framework: NIST SP 800-53 Rev 5
Providing authoritative source information enables external clients, including remote Internet clients, to obtain origin authentication and integrity verification assurances for the host/service name to network address resolution information obtained through the service. Systems that provide name and address resolution services include domain name system (DNS) servers. Additional artifacts include DNS Security Extensions (DNSSEC) digital signatures and cryptographic keys. Authoritative data includes DNS resource records. The means for indicating the security status of child zones include the use of delegation signer resource records in the DNS. Systems that use technologies other than the DNS to map between host and service names and network addresses provide other means to assure the authenticity and integrity of response data.
What to Check
How to Test
Step 1: Review Documentation
Examine the System Security Plan (SSP) and related artifacts for SC-20 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 |
|---|
| cloud-audit-mcp | Check encryption and network controls | cloud_audit_encryption |
| nmap | Network scanning | nmap -sV --script ssl-enum-ciphers |
Remediation Guide
