What evidence do auditors commonly ask for on 16 Antivirus software with signatures (Limited)?

List of endpoints whose signatures are older than the permitted age, with follow-up action for each; Antivirus console report showing signature version and last update time on each endpoint; Signature update schedule and distribution server configuration; Recent detection logs of known malware identified by signatures.

What is the most common gap auditors find on 16?

Endpoints offline or off VPN running signatures weeks out of date

ASD Strategies to Mitigate Cyber Security Incidents · Preventing Malware Delivery and Execution

`16` Antivirus software with signatures (Limited)

Antivirus software with up-to-date signatures to identify known malware.

Source: ASD Strategies to Mitigate Cyber Security Incidents, 16. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open ASD Strategies to Mitigate Cyber Security Incidents in the compliance library.

artefacts

held by a system

at each review

easy

to go live

Endpoint management (MDM / EDR)

where the evidence lives

teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

List of endpoints whose signatures are older than the permitted age, with follow-up action for each · Endpoint management (MDM / EDR)
Antivirus console report showing signature version and last update time on each endpoint · Endpoint management (MDM / EDR)
Signature update schedule and distribution server configuration · Endpoint management (MDM / EDR)
Recent detection logs of known malware identified by signatures · Endpoint management (MDM / EDR)

periodic reviewEvidence produced at each review

none for this control

governing documentDocuments that govern the control

none for this control

First move

Automate the pull from your Endpoint management (MDM / EDR). Device compliance report from the MDM (encryption, EDR agent, OS version) on a daily pull.

Common gaps auditors find

Endpoints offline or off VPN running signatures weeks out of date
Servers left without antivirus because of perceived performance impact
Alerts for failed signature updates not monitored

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 sheet

15 User education (Limited) · 17 TLS encryption between email servers (Limited)