For every service, protocol and port that is in use and regarded as insecure, the entity must define and implement security features so that the associated risk is mitigated. The guidance adds that where the business genuinely needs such an item, its use should be justified and its risk understood and accepted by the organisation. Applicability: no special notes; applies to every assessed entity. Objective under the customized approach: the particular risks arising from ports, protocols and services that are insecure are understood, evaluated and suitably reduced.
This control maps to 42 controls across 17 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.6 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 42 it maps to, and the evidence behind each claim, over MCP and REST.