Duties for carrying out each Requirement 5 activity (deploying and updating anti-malware, evaluating systems considered not at risk, reviewing malware logs, approving temporary disablement, operating anti-phishing controls) must be written down, allocated, and understood by those who hold them. They may be recorded within policies or in a separate document such as a RACI matrix, and staff may acknowledge their assigned duties. Applicability: applies to every entity in scope, with no special notes. Customized approach objective: daily Requirement 5 work is allocated, and the people who own it answer for its continuous, successful operation.
This control maps to 21 controls across 14 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 5.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 21 it maps to, and the evidence behind each claim, over MCP and REST.