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.
Free. Save your status, tasks and notes.
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
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.
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.
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.
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.
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
- 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.
- 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.
- 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.
- 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.
- 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.
ASD Essential Eight: 1 mapping
This control is broader than E8-AH-ML1.2.
E8-AH-ML1.2 requires that web browsers do not process Java content from the internet to reduce exposure to exploitation via browser-borne active content. ISO/IEC 27001:2022 Annex A 8.23 requires managing access to external websites to reduce exposure to malicious content, which can include blocking risky content types and scripts delivered from the web. Annex A 8.23 is broader because it covers overall web access management (not just Java) and may be implemented via multiple controls (filtering, isolation, policy, monitoring).
ASD Information Security Manual: 15 mappings
This control is equivalent to ISM-0963.
Annex A 8.23 requires organisations to manage access to external websites to reduce exposure to malicious content. ISM-0963 requires implementation of web content filtering to filter potentially harmful web-based content, aligning with the same intent and outcome, although ISM-0963 provides a more explicit implementation approach.
This control is broader than ISM-0267.
Annex A 8.23 requires managing access to external websites to reduce exposure to malicious content. ISM-0267 applies this concept to a specific high-risk website class by requiring blocking access to non-approved webmail services, which reduces phishing and malware delivery. Annex A 8.23 is broader because it covers overall web destination access management beyond webmail services.
This control is broader than ISM-0961.
Annex A 8.23 requires external website access to be managed to reduce exposure to malicious content. ISM-0961 is a specific implementation approach that uses web filters to restrict client-side active content to an organisation-approved domain list, directly reducing exposure to web-based malware. Annex A 8.23 is broader because it can be satisfied through multiple mechanisms (e.g., category filtering, reputation services, DNS filtering), not only active content restrictions.
This control is broader than ISM-1171.
Annex A 8.23 requires organisations to manage access to external websites to reduce exposure to malicious content. ISM-1171 is a targeted web filtering control that blocks attempts to access websites via direct IP addresses, helping prevent bypass of domain-based filtering. Annex A 8.23 is broader because it addresses general website access management, whereas ISM-1171 focuses on a specific evasion technique.
This control is broader than ISM-1236.
ISM-1236 requires web content filters to block malicious domains, dynamic domains, and domains that can be registered anonymously for free. ISO/IEC 27001:2022 Annex A 8.23 requires managing access to external websites to reduce exposure to malicious content, which can be implemented via web filtering and domain/category blocking. ISM-1236 is a specific, prescriptive subset focused on domain-name blocking criteria, whereas Annex A 8.23 is broader and technology-agnostic about how web access is managed.
This control is broader than ISM-1485.
ISM-1485 requires blocking browsers from processing web advertisements from the internet to reduce exposure to malicious content delivered via advertising networks. Annex A 8.23 requires managing access to external websites (web filtering) to reduce exposure to malicious content more generally across web destinations and content types. ISM-1485 is a specific technique that can be implemented via browser policy or filtering mechanisms and therefore represents a subset of the broader web access management objective in Annex A 8.23.
This control is broader than ISM-1782.
Annex A 8.23 requires external website access to be managed to reduce exposure to malicious content. ISM-1782 specifies using protective DNS to block known malicious domain names, which directly implements malicious site blocking. Annex A 8.23 is broader because it does not prescribe DNS-based controls and can include methods such as proxy category filtering.
This control partially overlaps ISM-0659.
ISM-0659 requires that files imported or exported via gateways or cross domain solutions (CDSs) undergo content filtering checks to detect unwanted or harmful content. ISO/IEC 27001:2022 Annex A 8.23 requires managing access to external websites to reduce exposure to malicious content, commonly using web filtering and content inspection technologies at network boundaries. They overlap where gateway security stacks apply URL/content inspection and malware filtering to content entering the organisation, but Annex A 8.23 is focused on web browsing destinations while ISM-0659 is specifically about file transfer through gateways/CDSs (including non-web transfer paths).
- ISM-0958Apply an approved domain or website category list to all gateway web trafficPartially overlaps
This control partially overlaps ISM-0958.
ISM-0958 requires an organisation-approved allow/block list of domain names or website categories for all HTTP/HTTPS traffic through gateways. ISO/IEC 27001:2022 Annex A 8.23 requires managing access to external websites to reduce exposure to malicious content, which is commonly achieved via domain/category filtering at gateways. Annex A 8.23 is outcome-focused and broader in permissible techniques, while ISM-0958 is a specific prescriptive mechanism (approved lists) and explicitly scoped to gateway HTTP/HTTPS traffic.
This control partially overlaps ISM-1237.
ISM-1237 requires web content filtering to be applied to outbound web traffic where appropriate. Annex A 8.23 requires organisations to manage access to external websites to reduce exposure to malicious content, commonly implemented via web filtering/proxy controls. Both address controlling web access to reduce risk, but ISM-1237 is specifically framed around outbound traffic filtering (including suitability), while Annex A 8.23 is broader in intent (malicious website exposure) and not limited to outbound traffic implementation detail.
This control partially overlaps ISM-2068.
ISM-2068 requires organisations to strictly limit internet connectivity to only those networked devices that require access. Annex A 8.23 relates by managing access to external websites through web filtering to reduce exposure to malicious content, controlling internet use once connectivity exists.
- ISM-2112AI applications processing classified data cannot directly access public dataPartially overlaps
This control partially overlaps ISM-2112.
ISM-2112 requires disabling AI applications' direct access to external public data sources when processing classified data. ISO/IEC 27001:2022 Annex A 8.23 overlaps because web filtering and managed access to external websites can be used to restrict or block AI systems from reaching public internet sources. Annex A 8.23 focuses on reducing exposure to malicious content, whereas ISM-2112 is primarily about preventing classified data exposure via outbound access irrespective of maliciousness.
This control supports ISM-0258.
Annex A 8.23 requires organisations to manage access to external websites to reduce exposure to malicious content. ISM-0258 requires establishing a web usage policy, which supports Annex A 8.23 by defining acceptable use and responsibilities that inform filtering decisions. ISM-0258 is governance-focused, not implementing technical access management.
This control supports ISM-0260.
Annex A 8.23 requires organisations to manage access to external websites to reduce exposure to malicious content. ISM-0260 mandates that all web access is conducted through web proxies, providing a central enforcement point to implement and monitor website access controls and filtering. While Annex A 8.23 focuses on the outcome (reduced exposure via managed access), ISM-0260 is an architectural requirement that enables consistent application of web filtering and policy enforcement.
This control depends on ISM-0874.
ISM-0874 requires all user devices to route internet access through the organisation's gateway instead of direct connections. ISO/IEC 27001:2022 Annex A 8.23 requires managing access to external websites (e.g., web filtering) to reduce exposure to malicious content, which is typically enforced at a central gateway/proxy. ISM-0874 enables consistent application of web filtering and URL controls, but it does not itself require filtering decisions or policy enforcement that Annex A 8.23 focuses on.
ASD Essentials for enterprise IT: 2 mappings
- IT.PRO-09.2Block outbound network connections to known malicious or untrusted destinationsPartially overlaps
This control partially overlaps IT.PRO-09.2.
IT.PRO-09.2 requires outbound network connections to known malicious or untrusted destinations to be blocked. It shares common ground with Annex A 8.23, since blocking known malicious websites is a core web filtering measure for reducing exposure to malicious content. IT.PRO-09.2 applies to all outbound connections rather than only web traffic, while Annex A 8.23 covers wider management of access to external websites.
- IT.PRO-09.3Inspect external or untrusted inbound content to stop malicious or unsafe contentPartially overlaps
This control partially overlaps IT.PRO-09.3.
IT.PRO-09.3 requires inbound content from external or untrusted sources to be inspected to prevent delivery of malicious or unsafe content. It shares common ground with Annex A 8.23, as inspecting web content reduces exposure to malicious content from external websites. IT.PRO-09.3 covers all inbound channels, such as email and file transfers, while Annex A 8.23 also manages which external websites can be accessed at all.
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.




