NS-1 Establish network segmentation boundaries
Establish network segmentation boundaries using virtual networks, subnets, and network security groups to isolate workloads based on sensitivity and function.
Source: Azure Security Benchmark v3 (renamed Microsoft cloud security benchmark), NS-1. 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
- NSG rule export · Cloud console / configuration management
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- VNet topology diagram · Policy repository / GRC workspace
- Segmentation policy · Policy repository / GRC workspace
- Hub-spoke architecture documentation · Policy repository / GRC workspace
First move
Common gaps auditors find
- Flat VNet topology
- Default-allow NSG rules
- No micro-segmentation for sensitive workloads
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 sheetLT-7 Use approved time synchronization sources · NS-2 Secure cloud services with network controls