5.3.5 Anti-malware cannot be disabled by users
Anti-malware mechanisms cannot be disabled or altered by users unless specifically documented and authorized by management on a case-by-case basis for a limited time period.
5
artefacts
1
held by a system
0
at each review
hard
to go live
Policy repository / GRC workspace
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Logs of authorised disablement · SIEM / log platform
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Policy configuration preventing disablement · Policy repository / GRC workspace
- Exception register with approvals and expiry · Policy repository / GRC workspace
- Sample test of user-attempted disable · Document repository
- Re-enablement verification · Document repository
First move
Mostly documents and reviews. Pull the 1 system-held artefact from your SIEM / log platform on a schedule; put the documents under version control with an owner and review date, and log each review as a dated record with a named reviewer.
Common gaps auditors find
- Local admin can disable AV freely
- Exceptions open-ended
- No re-enablement verification
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheet5.3.4 Audit logs for anti-malware enabled · 5.4.1 Processes and automated mechanisms are in place to detect and protect personnel against phishing attacks