Where any insecure service, protocol or daemon is present on system components: (a) the business justification is documented; and (b) additional security features that lower the risk of using them are documented and implemented. The guidance recommends enabling security features before new components are deployed, so insecure configurations do not enter the environment. Applicability: no special notes; applies to every assessed entity. Customized approach objective: no insecure service, protocol or daemon can be used as a route to compromise system components.
This control maps to 32 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 2.2.5 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 32 it maps to, and the evidence behind each claim, over MCP and REST.