Network security control configurations must be reviewed at least every six months, confirming each time that they remain relevant and effective. The testing procedures also check that configurations no longer backed by a business justification have been removed or updated, and the guidance suggests entities with many network changes consider reviewing more often. Applicability: no special notes; applies to every assessed entity. Customized approach objective: NSC settings that permit or block access to trusted networks are checked periodically so that only authorised connections with a current business justification remain allowed.
This control maps to 31 controls across 18 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.
PCI DSS 4.0 1.2.7 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of PCI DSS 4.0 your existing evidence covers. Hold ISO 27001:2022 and 139 of 280 PCI DSS 4.0 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. 415 were rejected on the ISO 27001:2022 pair alone.
The graph holds this control, the 31 it maps to, and the evidence behind each claim, over MCP and REST.