PublishedISO 9001:2026 published 16 Sept 2026 · 2015 certificates must transition by 30 Sept 2029What changed →
Internal Auditor course (ISO 19011:2026):free until 31 Oct · then $59 for three monthsStart free now →
← Back to Clause Explorer
A.8.23ISO 27001:2022 Annex ANew in 2022

Web filtering

ISO/IEC 27002:2022 attributes

Control type
Preventive
Security properties
Confidentiality · Integrity · Availability
Cybersecurity concept
Protect
Operational capability
System and network security
Security domain
Protection

Attribute tags as published in ISO/IEC 27002:2022, compiled from public listings — confirm against your licensed copy.

Plain-language summary

New in 2022: managing which external websites people can reach from your devices, so that known malicious, phishing and high-risk sites are blocked before a click turns into an infection — on the office network, on laptops working from home and on managed phones.

What the clause is really asking

The web is a main delivery route for malware and credential theft; this new control asks you to manage access to external websites to reduce exposure. That means deciding which categories of site to block (known malware and phishing, newly registered domains, anonymisers, illegal content), enforcing them through DNS filtering, a secure web gateway or browser controls, and telling people the rules and the exception route. The threat has moved: the Microsoft Digital Defense Report 2025 found that ClickFix-style lures — a fake page telling the user to paste a command to 'fix' their browser or prove they are human — made up a large share of the initial access it observed. Filtering blocks the lure pages and payload hosts it knows about; awareness and endpoint controls must catch the rest. QR-code phishing moves the click onto a phone, outside the office filter, so coverage has to follow the device. The common misunderstanding is that this is about blocking social media; it is about malicious content, and filtering that stops at the office firewall misses every remote worker.

What auditors look for

Auditors ask for the web filtering rules and the categories you block, then check the configuration in the filtering tool. They test it: from a sample laptop on the office network and, where they can, off the network on a hotspot, they try a blocked category or a vendor-provided test URL. Given QR-code phishing, they ask whether managed phones are filtered. They pull the block reports and ask who reviews them and what happened after the last malicious-site hit. They ask how users request access to a wrongly blocked site and who approves it. The hard question: does the filtering still apply when the laptop leaves the building?

Typical evidence

Web filtering rules within the acceptable use or a topic-specific policy; blocked category list and configuration screenshots; coverage evidence for office, remote and mobile devices; block and threat reports with review records; exception requests and approvals; test results from on and off the network; awareness material covering ClickFix and QR-code phishing; threat feed update settings.

How to comply — recommendations

Add a short section to your acceptable use policy saying which categories are blocked and why, and how to ask for an exception. Implement DNS-layer or agent-based filtering that follows the laptop off the network, not only a filter on the office firewall, and extend it to managed phones through your mobile device management. Block at least malware, phishing, newly registered and uncategorised domains, and anonymising proxies. Review the block report monthly — a spike of phishing hits for one user is an incident lead. Brief staff on the two current lures: any page asking them to paste or run a command, and QR codes in emails or on posters asking them to sign in. Test off-network coverage quarterly.

Common nonconformities

No web filtering, or no defined blocked categories; filtering only on the office network while staff work remotely; mobile devices not covered; block reports never reviewed; exceptions granted informally with no record; filtering rules not communicated to users; filtering subscription or threat feed lapsed; policy concerned only with productivity, not malicious sites.

Related clauses

ISO/IEC 27002:2022 8.23 (guidance); ISO 27001 7.3 (awareness); Annex A 5.7 (threat intelligence), 5.10 (acceptable use), 6.3 (awareness and training), 8.1 (user endpoint devices), 8.7 (protection against malware), 8.16 (monitoring activities); NIST CSF 2.0 PR.IR (technology infrastructure resilience), DE.CM (continuous monitoring).

Resources for this clause

Get the free ISO 27001 Annex A — 93 Controls Quick Reference (A3 PDF)

Free, instant download. We'll only email you the occasional practical quality update — no spam, unsubscribe anytime.

Qlause provides interpretive guidance only and is not a substitute for the standard. Refer to your licensed copy of the relevant standard for the authoritative text.

Certification & implementation

Working on a certification or system implementation project?

Implementing ISO 9001, moving to the 2026 edition, getting ready for a certification audit, or stuck on a clause that doesn't seem to fit your operation? Tell us where you are and where you're stuck. We'll look at it and suggest a practical next step, or connect you with people we trust who can help.

Email hello@qlause.app

No sales pitch, no obligation — we read every message.