Skip to content
Technological controls
ISO 27001A.8.23

ISO 27001 Annex A 8.23 Web filtering

What it says

Access to external websites shall be managed to reduce exposure to malicious content.

Quoted as published. Everything else on this page is written by Control Stack.

In plain English

Manage your organisation's access to external websites, for example by blocking known malicious sites, to reduce exposure to malicious content.

Your organisation must manage access to external websites to reduce exposure to malicious content, such as malware downloads and phishing pages (fake sites that capture passwords). Managing access means deciding which types of website people may reach and applying that decision, usually through web filtering: tools that block or allow sites by address or category. The requirement is to reduce exposure, not remove it. It applies wherever people browse for work, including away from the office.

Why it matters

One visit to a malicious site can plant malware or capture a password on a fake sign-in page. Blocking known and suspected malicious sites reduces how often people reach that content, which lowers the chance of a device being compromised that way.

How to implement

  1. Set rules for which types of website people may reach.

    Cover known or suspected malicious sites and command and control servers (used to direct infected devices). You can add illegal content and unneeded upload sites. Put them in your acceptable use rules (Annex A 5.10). Say who approves exceptions, and put the request link on the filter's block page.

  2. Turn on filtering that covers every way people browse.

    Use a secure web gateway, DNS filtering (blocking when a site's name is looked up) or browser and endpoint protection. Use a device agent or per-device setting so it works away from the office. A small organisation can pair built-in browser protection with a cloud DNS filter set on each device.

  3. Close the ways round the filter.

    Use managed browser and device settings so people cannot turn off protection, change DNS or proxy settings, or use another browser. Where the browser offers the setting, stop them clicking past unsafe-site warnings. Many filters see only the site name in encrypted traffic, so weigh inspecting it against privacy and legal limits.

  4. Keep the block lists current.

    Turn on automatic updates from the filter provider, and add malicious sites your own threat intelligence identifies (Annex A 5.7). Record each manual allow entry with a reason, an approver and an end date.

  5. Log blocks and follow them up.

    Send filter logs to your log platform (Annex A 8.15), and alert on repeated blocks from one device, which can indicate malware (Annex A 8.7 covers protection against it). Where an IT provider runs the filter, get the settings and reports, and agree who acts on alerts.

Keep it running

Check the filter's coverage report for devices that have stopped reporting, and follow up repeated blocks from one device, which can point to an infection. Look again when you add browsers, device types or remote working arrangements.

Evidence and audit

  1. Check 1 of 5What an auditor asks for

    Ask for

    The filter's coverage report, compared with the device list.

    Look at

    Devices on the list that the filter does not show, especially laptops used away from the office and managed phones.

    Good evidence

    Every in-scope device reports to the filter, and any exception has a recorded reason.

  2. Check 2 of 5What an auditor asks for

    Ask for

    A demonstration from a managed device, on and off the office network, using a harmless test page for a malicious category, such as the filter provider's malware or phishing test page.

    Look at

    Whether the page is blocked both times, and whether the person can click past the warning, change browser or device settings, or switch browser to avoid it.

    Good evidence

    The test page is blocked in both locations, and the person cannot get past the block without an approved exception.

  3. Check 3 of 5What an auditor asks for

    Ask for

    The live filter policy, compared with the written rules.

    Look at

    Whether the rules cover malicious content, whether the categories they name, such as malicious sites and command and control servers, are enforced, and when the block lists last updated.

    Good evidence

    The rules cover malicious content (such as known or suspected malicious sites), every category they require is enforced in the live policy, and block list updates are current.

  4. Check 4 of 5What an auditor asks for

    Ask for

    The filter's allow list, compared with exception records.

    Look at

    Allow entries with no record, and exceptions past their end date.

    Good evidence

    Every allow entry has a reason, an approver and an end date that has not passed.

  5. Check 5 of 5What an auditor asks for

    Ask for

    Block logs for a recent period, with records of any follow-up.

    Look at

    Whether repeated blocks from one device were looked into.

    Good evidence

    Repeated blocks from a single device have a recorded follow-up and outcome.

Mappings

Closest match in ASD Information Security Manual: ISM-0963, Implementing web content filters for safety, which asks for the same thing.

Essential Eight

ASD Essential Eight: 1 mapping

ASD ISM

ASD Information Security Manual: 15 mappings

ASD Essentials

ASD Essentials for enterprise IT: 2 mappings

Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.

Get help with this control

ISO 27001 training

Mindset Cyber, a PECB Authorised Titanium Partner, sells official PECB ISO/IEC 27001 courses that map directly to the controls in this library.