Service providers must apply intrusion-detection and/or intrusion-prevention methods that find the covert channels malware uses to communicate, raise alerts on them or block them, and deal with them, such as DNS tunneling to command-and-control servers. Guidance: placement should consider critical network locations and likely covert channel routes; helpful methods include real-time endpoint scanning, egress filtering, allow listing, data loss prevention and network security monitoring, and organizations should keep up-to-date knowledge of how malware operates. Applicability: applies only when the assessed entity is a service provider. Objective under the customized approach: mechanisms spot covert traffic to command-and-control systems and either alert on it or stop it, and alerts are handled by staff, or automatically in a way that blocks such traffic. Future-dated: treated as a best practice up to 31 March 2025 and mandatory since then.
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 11.5.1.1 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.