Deploy network intrusion detection and prevention capability that inspects traffic and payload to and from the workload, tuned so the alerts it raises are usable by the security operations team.
This control maps to 28 controls across 21 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.
Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.
Azure Security Benchmark ASBv3-NS-4 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of Azure Security Benchmark your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 71 of 85 Azure Security Benchmark controls already carry evidence.
Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 0 were rejected on the NIST SP 800-53 Rev 5 pair alone.
The graph holds this control, the 28 it maps to, and the evidence behind each claim, over MCP and REST.