NS-6 Deploy web application firewall
Deploy a web application firewall in front of web applications and APIs and configure rules appropriate to the application-layer attacks those endpoints face.
Source: Azure Security Benchmark v3 (renamed Microsoft cloud security benchmark), NS-6. 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
- WAF deployment inventory covering all public web and API endpoints · Endpoint management (MDM / EDR)
periodic reviewEvidence produced at each review
- Record of rules moved from detection to prevention mode · Document repository
governing documentDocuments that govern the control
- Rule set and managed rule version in use · Document repository
- Tuning and exclusion register · Policy repository / GRC workspace
First move
Common gaps auditors find
- WAF left in detection-only mode indefinitely
- endpoints published that bypass the WAF
- managed rule sets never updated
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-5 Deploy DDOS protection · NS-7 Simplify network security configuration