Azure Security Benchmark
Network Security

Azure Security Benchmark ASBv3-NS-10: Ensure Domain Name System (DNS) security

Configure Domain Name System security so clients resolve through trusted authoritative and recursive services and the zones are protected against hijack and dangling records.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 15 controls across 8 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

FedRAMP High · 3 controls

  • SC-20 Secure Name/Address Resolution Service (Authoritative)
  • SC-21 Secure Name/Address Resolution Service (Recursive or Caching Resolver)
  • SC-22 Architecture and Provisioning for Name/Address Resolution Service

FedRAMP Moderate · 3 controls

  • SC-20 Secure Name/Address Resolution Service (Authoritative)
  • SC-21 Secure Name/Address Resolution Service (Recursive or Caching Resolver)
  • SC-22 Architecture and Provisioning for Name/Address Resolution Service

NIST SP 800-53 Rev 5 · 3 controls

  • NIST800-SC-20 SC-20 Secure Name/Address Resolution Service (Authoritative Source)
  • NIST800-SC-21 SC-21 Secure Name/Address Resolution Service (Recursive or Caching Resolver)
  • NIST800-SC-22 SC-22 Architecture and Provisioning for Name/Address Resolution Service

CIS Controls v8 · 2 controls

  • CIS-4.9 Configure Trusted DNS Servers on Enterprise Assets
  • CIS-9.2 Use DNS Filtering Services

ISO 27001:2022 · 1 control

  • 8.21 Security of network services

ISO 27002:2022 · 1 control

  • 8.21 Security of network services
  • NIST-CSF-PR.IR-01 Networks and environments are protected from unauthorized logical access and usage

UK Cyber Essentials · 1 control

  • CE-MP.3 Anti-Malware Scans Files on Access and Web Pages

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in Network Security

You are reading one control. How much of Azure Security Benchmark have you already done?

Azure Security Benchmark ASBv3-NS-10 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of Azure Security Benchmark your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 71 of 85 Azure Security Benchmark controls already carry evidence.

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 0 were rejected on the NIST SP 800-53 Rev 5 pair alone.

Query this from an agent

The graph holds this control, the 15 it maps to, and the evidence behind each claim, over MCP and REST.