After any significant change, internal vulnerability scans must be performed so that: vulnerabilities ranked high-risk or critical under the Requirement 6.3.1 rankings are resolved; rescans are run as needed; and the scans are carried out by qualified personnel with organizational independence from the tested systems (a QSA or ASV is not required). Guidance (good practice): scan as part of the change process under Requirement 6.5.2, covering every component the change affects, before the change is treated as complete. Applicability: the credentialed scanning of 11.3.1.2 need not be used for these post-change scans. Customized approach objective: after significant network or system changes, automated tools operating inside the network confirm the security state of every system component, and detected issues are assessed and fixed using a formal risk assessment framework.
This control maps to 38 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 11.3.1.3 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 38 it maps to, and the evidence behind each claim, over MCP and REST.