ISO 27001 Annex A 8.23 Web filtering to reduce malicious website exposure
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.
What it means
In plain EnglishLimit access to risky websites to avoid malware and phishing threats.
This control is about making sure your team members aren't accidentally stumbling onto harmful websites that could infect your systems with viruses or steal your information. Think of it like having a bouncer at a club, but for your internet browsing: keeping the bad stuff out and only letting in the good.
Free. Save your status, tasks and notes.
Why it matters
Unfiltered access to websites can lead to malware infections and phishing attacks, compromising sensitive data and disrupting operations.
How to implement
The IT manager should identify risky website categories, like those known for phishing or distributing malware.
They can do this by referencing lists from cyber security agencies such as the ASD. Once identified, these websites should be blocked using web filtering tools available in many security software packages.
The HR department should ensure that all employees receive training on recognising unsafe websites and understanding why certain sites are blocked.
This can be done through regular workshops or training sessions, where employees learn about internet safety and the organisation's policies.
The board should approve a clear policy on web usage that outlines which types of websites are banned and why.
This policy should be informed by both ISO 27002:2022 guidance and the requirements under Australian regulations like the Privacy Act 1988.
IT staff should regularly update the web filtering system to adapt to new threats and business needs.
This involves staying informed with threat intelligence reports (such as those provided by ASD) and adjusting block lists accordingly.
The security team should conduct regular audits of the web filtering system to ensure it is functioning as intended.
This involves testing whether known malicious sites are effectively blocked and confirming that legitimate business needs are not hindered.
Keep it running
Regularly update web filtering categories, validate block/allow lists, and review proxy/DNS logs to tune rules for new malicious sites.
Evidence and audit
- Check 1 of 5What an auditor asks for
Ask for
The latest web usage policy document.
Look at
Whether it specifies categories of websites that are blocked. GOOD is a clear and up-to-date policy that reflects the latest cyber threats.
- Check 2 of 5What an auditor asks for
Ask for
A demonstration of the web filtering system in action.
Look at
Whether it effectively blocks access to known malicious sites. GOOD is when attempts to access these sites are stopped by the system.
- Check 3 of 5What an auditor asks for
Ask for
Training records or materials regarding web safety training.
Look at
How often this training is conducted and what it covers. GOOD is regular, comprehensive training that includes information on risky web practices.
- Check 4 of 5What an auditor asks for
Ask for
Updates or change logs of web filter configurations.
Look at
Whether these logs show regular, necessary adjustments. GOOD is a log showing that the list of blocked sites is reviewed and updated frequently.
- Check 5 of 5What an auditor asks for
Ask for
Reports or alerts generated from the web filtering system.
Look at
The details of sites that were blocked or attempts to access restricted sites. GOOD is reports showing proactive blocking and minimal instances of policy violations.
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).
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.
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 connections to known malicious and untrusted destinations using threat intelligencePartially 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 all inbound content channels and block 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 runs PECB-accredited ISO/IEC 27001 training that maps directly to the controls in this library.




