07 Web content filtering (Excellent)
Filter incoming and outgoing web traffic. Allow only approved types of web content. Inspect incoming web content for malware.
Source: ASD Strategies to Mitigate Cyber Security Incidents, 07. 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.
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
- Malware inspection settings on the web gateway, including TLS inspection scope · Endpoint management (MDM / EDR)
- Proxy logs of blocked downloads and category violations · Endpoint management (MDM / EDR)
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Approved web content type list, such as allowed file types and categories, signed off by the security owner · Policy repository / GRC workspace
- Web proxy policy showing allowed content types and category blocks for inbound and outbound traffic · Policy repository / GRC workspace
First move
Common gaps auditors find
- Web filtering applies on the office network but not to remote users off VPN
- HTTPS traffic not inspected, so most malicious downloads pass unchecked
- Outbound web traffic not filtered, allowing data exfiltration to uncategorised sites
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 sheet06 Email content filtering (Excellent) · 08 Deny direct internet connectivity (Excellent)