NET-13.2: Secure Name / Address Resolution Service (Recursive or Caching Resolver)
Mechanisms exist to perform data origin authentication and data integrity verification on the Domain Name Service (DNS) resolution responses received from authoritative sources when requested by client systems.
Renumbered: Formerly NET-10.2 in SCF 2025.4.
Control Question: Does the organization perform data origin authentication and data integrity verification on the Domain Name Service (DNS) resolution responses received from authoritative sources when requested by client systems?
General (18)
| Framework | Mapping Values |
|---|---|
| GovRAMP | SC-21 |
| GovRAMP Core | SC-21 |
| GovRAMP Low | SC-21 |
| GovRAMP Low+ | SC-21 |
| GovRAMP Moderate | SC-21 |
| GovRAMP High | SC-21 |
| MITRE ATT&CK 16 | T1071 T1071.001 T1071.002 T1071.003 T1071.004 T1568 T1568.002 |
| NIST 800-53 R4 | SC-21 |
| NIST 800-53 R5.2 | SC-21 |
| NIST 800-53B R5 (low) (source) | SC-21 |
| NIST 800-53B R5 (moderate) (source) | SC-21 |
| NIST 800-53B R5 (high) (source) | SC-21 |
| NIST 800-82 R3 | SC-21 |
| NIST 800-82 R3 LOW OT Overlay | SC-21 |
| NIST 800-82 R3 MODERATE OT Overlay | SC-21 |
| NIST 800-82 R3 HIGH OT Overlay | SC-21 |
| NIST 800-171 R2 (source) | NFO - SC-21 |
| Shared Assessments SIG 2025 | P.2.4 |
US (11)
| Framework | Mapping Values |
|---|---|
| USA Federal CMS MARS-E 2.0 | SC-21 |
| USA Federal DHS CISA TIC 3.0 | 3.PEP.DO.DNVAC 3.PEP.DO.DNVAD |
| USA Federal CJIS Security Policy 6.0 | SC-21 |
| USA Federal FedRAMP R5 (low) | SC-21 |
| USA Federal FedRAMP R5 (moderate) | SC-21 |
| USA Federal FedRAMP R5 (high) | SC-21 |
| USA Federal FedRAMP R5 (LI-SaaS) | SC-21 |
| USA Federal IRS 1075 2021 | SC-21 |
| USA Texas DIR SCSC 2.2 2025 | SC-21 |
| USA Texas TX-RAMP Level 1 | SC-21 |
| USA Texas TX-RAMP Level 2 | SC-21 |
APAC (1)
| Framework | Mapping Values |
|---|---|
| APAC Singapore CCOP CII 2026 | 11.2.1 A.8.2 |
Capability Maturity Model
Level 0 — Not Performed
Practices are non-existent, based on the inability to demonstrate an implemented and operational capability. A reasonable person would conclude the control is not being performed.
Level 1 — Performed Informally
SCR-CMM Level 1 criteria definitions are not available for this control: ▪ A reasonable person would conclude this control requires a structured process. ▪ At this level of maturity, the "ad hoc" nature of performing a capability informally would indicate the intent of the control is not met due to a lack of consistency and formality.
Level 2 — Planned & Tracked
Network Security (NET) capabilities are requirements-driven, but are not standardized across the entity (e.g., local/regional level consistency). Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Policies and standards associated with NET domain capabilities are formally documented and centrally-managed by the entity. ▪ Standardized Operating Procedures (SOP) associated with NET domain capabilities are documented and maintained by process owners. ▪ IT and/or cybersecurity personnel work with business stakeholders and process owners to appropriately scope and reasonably implement cybersecurity and data protection controls associated with NET domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD). ▪ Network security-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines). ▪ Network security management may be a defined function (e.g., team or department) or assigned as an additional duty to existing IT and/or cybersecurity personnel. ▪ IT personnel define secure networking practices to protect the Confidentiality, Integrity, Availability and Safety (CIAS) of the organization's TAASD. ▪ Secure Baseline Configurations (SBC) enforce the principles of least privileges and least functionality for boundary protection technologies.
Level 3 — Well Defined
Network Security (NET) capabilities are standardized across the entity for applicability to People, Processes, Technologies, Data and/or Facilities (PPTDF) to ensure consistency for Technology Assets, Applications, Services and/or Data (TAASD). Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Policies and standards associated with NET domain capabilities are formally documented and centrally-managed by the entity's Governance, Risk & Compliance (GRC) team, or similar function. ▪ Standardized Operating Procedures (SOP) associated with NET domain capabilities are well-documented and kept current by process owners. ▪ A network security management team, or similar function, is appropriately staffed and supported to implement and maintain NET domain capabilities. ▪ Technology is leveraged to enhance the efficiency and accuracy of network security operations (e.g., network management solution and log aggregator). ▪ The entity's Governance, Risk & Compliance (GRC) team, or similar function, works with business stakeholders and process owners to appropriately scope and reasonably implement cybersecurity and data protection controls associated with NET domain capabilities to address Minimum Compliance Requirements (MCR) (e.g., applicable statutory, regulatory and/or contractual requirements) and Discretionary Security Requirements (DSR) (e.g., entity-required controls). ▪ Secure Baseline Configurations (SBC) enforce the principles of least privileges and least functionality for boundary protection technologies. ▪ An implemented and operational capability exists to perform data origin authentication and data integrity verification on the Domain Name Service (DNS) resolution responses received from authoritative sources when requested by client systems.
Level 4 — Quantitatively Controlled
Utilize SCR-CMM Level 3 criteria definitions: ▪ There are no defined Level 4 criteria, since it is reasonable to assume a quantitatively-controlled process is not necessary to operationalize this control. ▪ While it may be possible to develop “metrics-driven” capabilities for this control, the criteria would be organization-specific to define.
Level 5 — Continuously Improving
Utilize SCR-CMM Level 3 or Level 4 (if available) criteria definitions: ▪ There are no defined Level 5 criteria, since it is reasonable to assume a continuously-improving process is not necessary to operationalize this control. ▪ Level 5 capabilities should be considered “world-class” where the control builds on Level 4 capabilities, but are continuously improving through Artificial Intelligence (AI) and/or Machine Learning (ML) technologies. ▪ While it may be possible to develop responsive capabilities for this control through the use of AI and/or ML technologies, the criteria would be organization-specific to define.
Assessment Objectives
- NET-13.2_A01 data origin authentication is requested for the name/address resolution responses that the system receives from authoritative sources.
- NET-13.2_A02 data origin authentication is performed on the name/address resolution responses that the system receives from authoritative sources.
- NET-13.2_A03 data integrity verification is requested for the name/address resolution responses that the system receives from authoritative sources.
- NET-13.2_A04 data integrity verification is performed on the name/address resolution responses that the system receives from authoritative sources.
Technology Recommendations
Micro/Small
- Use reputable DNS resolver (e.g., Cloudflare 1.1.1.1, Google 8.8.8.8)
Small
- Secure DNS resolver with filtering (e.g., Cisco Umbrella free, Cloudflare Gateway)
Medium
- DNS security service (e.g., Cisco Umbrella, Cloudflare Gateway)
- DNS filtering policy
Large
- Enterprise DNS security service (e.g., Cisco Umbrella, Palo Alto DNS Security)
- DNS-layer threat blocking
Enterprise
- Enterprise DNS security platform with threat intelligence
- Recursive resolver security
- DNSSEC validation
- DNS over HTTPS (DoH)