PCI DSS 4.0 5.2.3: 5.2.3 Periodic evaluation of components not at risk from malware
Any system components treated as not at risk from malware must be evaluated on a periodic basis, and the evaluation must include: a documented list of every system component considered not at risk; identification and assessment of evolving malware threats relevant to those components; and confirmation of whether those components still do not need anti-malware protection. Determinations should be supported by vendor resources, best practice and evidence from industry, and malware trends should be fed into the vulnerability identification work under Requirement 6.3.1. Applicability: covers the components on which no anti-malware solution is deployed under Requirement 5.2.1. Objective under the customized approach: the entity stays aware of changing malware threats so that systems left without malware protection are not exposed to infection.
This control maps to 39 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.
You are reading one control. How much of PCI DSS 4.0 have you already done?
PCI DSS 4.0 5.2.3 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.