NS-8 Detect and disable insecure services and protocols
Detect insecure services and protocols at operating system, application and package layers and disable them, applying compensating controls where they cannot be disabled.
Source: Azure Security Benchmark v3 (renamed Microsoft cloud security benchmark), NS-8. 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.
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
- Scan results listing insecure services and protocols detected · Vulnerability scanner / patch tooling
- Re-scan evidence confirming remediation · Vulnerability scanner / patch tooling
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Disablement records or hardening baseline entries · Policy repository / GRC workspace
- Compensating control register for exceptions with expiry dates · Policy repository / GRC workspace
First move
Common gaps auditors find
- legacy protocols left enabled for one dependency and forgotten
- exceptions granted with no expiry
- scanning limited to the network layer, missing application and package layers
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 sheetNS-7 Simplify network security configuration · NS-9 Connect on-premises or cloud network privately