Every change to network connections and every change to the configuration of network security controls must be approved and handled through the formal change control process defined in Requirement 6.5.1. Applicability: a change to a network connection means adding, removing or altering a connection; a change to an NSC configuration includes changes to the device itself and changes that affect how it enforces security. Customized approach objective: changes to connections and NSCs do not lead to misconfigured devices, insecure services being introduced, or unauthorised connections.
This control maps to 35 controls across 19 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.2 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 35 it maps to, and the evidence behind each claim, over MCP and REST.