Skip to main content

NET-13: Domain Name Service (DNS) Resolution

NET 10 — Critical Protect

Mechanisms exist to ensure Domain Name Service (DNS) resolution is designed, implemented and managed to protect the security of name / address resolution.

Renumbered: Formerly NET-10 in SCF 2025.4.

Code reused: In SCF 2025.4 and earlier, NET-13 was Electronic Messaging. That control is now NET-40.1.

Control Question: Does the organization ensure Domain Name Service (DNS) resolution is designed, implemented and managed to protect the security of name / address resolution?

General (20)
Framework Mapping Values
CIS CSC 8.1 4.9
CIS CSC 8.1 IG2 4.9
CIS CSC 8.1 IG3 4.9
GovRAMP SC-20
GovRAMP Low SC-20
GovRAMP Low+ SC-20
GovRAMP Moderate SC-20
GovRAMP High SC-20
MITRE ATT&CK 16 T1071 T1071.001 T1071.002 T1071.003 T1071.004 T1553.004 T1566 T1566.001 T1566.002 T1568 T1568.002 T1598 T1598.002 T1598.003
NIST 800-53 R4 SC-20 SC-20(2)
NIST 800-53 R5.2 SC-20 SC-20(02)
NIST 800-53B R5 (low) (source) SC-20
NIST 800-53B R5 (moderate) (source) SC-20
NIST 800-53B R5 (high) (source) SC-20
NIST 800-82 R3 SC-20 SC-20(02)
NIST 800-82 R3 LOW OT Overlay SC-20
NIST 800-82 R3 MODERATE OT Overlay SC-20
NIST 800-82 R3 HIGH OT Overlay SC-20
NIST 800-171 R2 (source) NFO - SC-20
Shared Assessments SIG 2025 N.8
US (10)
EMEA (7)
APAC (3)
Framework Mapping Values
APAC Australia ISM June 2026 ISM-0574 ISM-0861 ISM-1026 ISM-1027 ISM-1151 ISM-1183 ISM-1540 ISM-1782 ISM-1799 ISM-2017
APAC India RBI Digital Payments 2021 51.0
APAC Singapore CCOP CII 2026 11.2.1 11.2.2 A.8.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. ▪ IT and/or cybersecurity personnel ensure Domain Name Service (DNS) resolution is designed, implemented and managed to protect the security of name / address resolution.

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 ensure Domain Name Service (DNS) resolution is designed, implemented and managed to protect the security of name / address resolution.

Level 4 — Quantitatively Controlled

Network Security (NET) capabilities, in addition to being standardized across the entity and centrally managed to ensure consistency across Technology Assets, Applications, Services and/or Data (TAASD), efforts are metrics driven to provide sufficient insight for decision makers to predict optimal performance, ensure continued operations and/or identify areas for improvement. Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Applicable SCR-CMM Level 3 (Well Defined) capabilities are implemented and operational. ▪ Metrics reporting includes quantitative analysis of Key Performance Indicators (KPIs). ▪ Metrics reporting includes quantitative analysis of Key Risk Indicators (KRIs). ▪ Scope of metrics, KPIs and KRIs covers organization-wide cybersecurity and data protection controls, including functions performed by third-parties. ▪ Organizational leadership maintains a formal process to objectively review and respond to metrics, KPIs and KRIs (e.g., monthly or quarterly review). ▪ Based on metrics analysis, process improvement recommendations are submitted for review and are handled in accordance with change control processes. ▪ Business and technical stakeholders are involved in reviewing and approving proposed changes to evolve capabilities.

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

  1. NET-13_A01 additional data origin authentication is provided along with the authoritative name resolution data that the system returns in response to external name/address resolution queries.
  2. NET-13_A02 integrity verification artifacts are provided along with the authoritative name resolution data that the system returns in response to external name/address resolution queries.
  3. NET-13_A03 the means to indicate the security status of child zones (and if the child supports secure resolution services) is provided when operating as part of a distributed, hierarchical namespace.
  4. NET-13_A04 the means to enable verification of a chain of trust among parent and child domains when operating as part of a distributed, hierarchical namespace is provided.

Evidence Requirements

E-NET-01 Content / DNS Filtering

Documented evidence of the methods that content / DNS filtering is implemented to prevent Internet traffic from prohibited content and/or hostile web sites.

Network Security

Technology Recommendations

Micro/Small

  • Secure Baseline Configurations (SBC)

Small

  • Secure Baseline Configurations (SBC)

Medium

  • Secure Baseline Configurations (SBC)

Large

  • Secure Baseline Configurations (SBC)

Enterprise

  • Secure Baseline Configurations (SBC)

The Secure Controls Framework (SCF) is maintained by SCF Council. Use of SCF content is subject to the SCF Terms & Conditions.

Manage this control in SCF Connect

Track implementation status, collect evidence, and map controls to your compliance frameworks automatically.