What evidence do auditors commonly ask for on NS-10 Ensure Domain Name System (DNS) security?

List of authoritative and recursive resolvers in use and their trust basis; DNS zone access control and change audit records; Dangling or stale record scan results; DNSSEC or equivalent integrity configuration where supported.

What is the most common gap auditors find on NS-10?

decommissioned resources leaving dangling CNAMEs open to subdomain takeover

Azure Security Benchmark v3 (renamed Microsoft cloud security benchmark) · Network Security

`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.

Source: Azure Security Benchmark v3 (renamed Microsoft cloud security benchmark), NS-10. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open Azure Security Benchmark v3 (renamed Microsoft cloud security benchmark) in the compliance library.

artefacts

held by a system

at each review

easy

to go live

Vulnerability scanner / patch tooling

where the evidence lives

teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

Dangling or stale record scan results · Vulnerability scanner / patch tooling
DNSSEC or equivalent integrity configuration where supported · Cloud console / configuration management

periodic reviewEvidence produced at each review

DNS zone access control and change audit records · Identity provider / directory

governing documentDocuments that govern the control

List of authoritative and recursive resolvers in use and their trust basis · Document repository

First move

Automate the pull from your Vulnerability scanner / patch tooling. Scan schedule, findings and remediation age straight from the scanner; patch compliance from the patch console.

Common gaps auditors find

decommissioned resources leaving dangling CNAMEs open to subdomain takeover
clients allowed to use arbitrary public resolvers
zone changes made without audit trail

Do this for your whole sheet

Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.

Build my evidence sheet

NS-9 Connect on-premises or cloud network privately · PA-1 Separate and limit highly privileged/administrative users