Requirement
Protection against malware shall be implemented and supported by appropriate user awareness.
What the engine looks for
Every group below must be satisfied — by an affirmative statement, not a plan, a hedge or a denial — for the control to count as covered. A term ending in … matches any word it begins. Supporting terms do not change the verdict — they raise confidence and distinguish a policy that names a mechanism from one that gestures at a category.
Required element 1 — any one of
malwareantivirusanti-virusedrendpoint protection
Supporting terms — specificity signals
signaturebehaviouralquarantinescanawarenessemail filtering
Equivalent controls elsewhere
Matched on shared topics. Satisfying this control usually moves these too.
| Framework | Control | Title | Shared topics |
|---|---|---|---|
| SOC 2 | CC6.8 | Prevention and detection of unauthorised software | malware endpoint |
| PCI DSS 4.0.1 | 5.2-5.3 | Anti-malware deployed and kept current | malware endpoint |
| PCI DSS 4.0.1 | 5.4.1 | Protection against phishing | malware |
| HIPAA | 164.310(b)-(c) | Workstation use and security (R) | endpoint |
| NIST CSF 2.0 | DE.CM-09 | Computing hardware, software and services are monitored | endpoint |
| HIPAA | 164.308(a)(5)(ii)(A-D) | Security awareness and training (A) | malware |