NS-3 Deploy firewall at the edge of enterprise network
Deploy Azure Firewall or third party NVA at the edge to inspect and control inbound and outbound traffic with documented rules.
Source: Azure Security Benchmark v3 (renamed Microsoft cloud security benchmark), NS-3. 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
- Firewall deployment architecture · Source control / CI pipeline
- Rule set export · Cloud console / configuration management
- Threat intelligence configuration · Cloud console / configuration management
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Change management for rule changes · Policy repository / GRC workspace
First move
Common gaps auditors find
- No egress filtering
- Threat intel feature disabled
- Rules unreviewed for months
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-2 Secure cloud services with network controls · NS-4 Deploy intrusion detection/intrusion prevention systems (IDS/IPS)