Internal vulnerability scans must use authenticated scanning, with these conditions: systems that cannot accept scanning credentials are documented; systems that do accept credentials are scanned with sufficient privileges; and where scanning accounts permit interactive logins, those accounts are governed per Requirement 8.2.2. Applicability: authenticated tools may run on the host or over the network. 'Sufficient' privileges means enough access to system resources for a thorough scan that finds known vulnerabilities. The requirement does not cover components unable to accept credentials, such as mainframes, containers and certain network or security appliances. Objective under the customized approach: automated tools can find vulnerabilities local to each system that are invisible from a remote vantage point. Future-dated: treated as a best practice up to 31 March 2025 and mandatory since then.
This control maps to 22 controls across 15 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.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 22 it maps to, and the evidence behind each claim, over MCP and REST.