Join our Newsletter — 33% off our NHI Course
Home› Glossary› Cyber Security› Web Filtering
Cyber Security

Web Filtering

← Back to Glossary
By NHI Mgmt Group Updated October 31, 2026 Domain: Cyber Security

Web filtering is the control of access to websites, web apps, or categories of online services based on policy. Organisations use it to block or restrict access to generative AI tools for certain users or groups, reducing the chance that sensitive information is shared outside approved boundaries.

What Web Filtering Actually Does

Web filtering is a policy control, not just a browser blocklist. It decides which websites, web apps, or online service categories users can reach, and it often operates through proxies, DNS controls, category databases, and exception handling. In practice, the control exists to shape acceptable use and reduce exposure to risky destinations.

Because the decision is policy-driven, web filtering is usually broader than simple URL blocking. Organisations can allow, deny, warn, time-limit, or log access based on user, device, network location, or content category. That makes it a practical control for balancing productivity, safety, and security.

Why Organisations Use It

The most common reason is to reduce data leakage and unsafe web use. If a user cannot reach an unsanctioned online service, they are less likely to paste confidential material into tools that are outside approved oversight. It is also used to cut access to known malicious sites, risky file-hosting domains, and inappropriate content classes.

For modern environments, the control has expanded beyond classic web browsing. It now often includes access decisions for generative AI tools, remote browser isolation, and cloud-delivered web gateways, where policy has to follow the user rather than the office network.

Web filtering is most effective when it is treated as a boundary control, not a standalone cure. It works best when paired with logging, user identity awareness, and clear exception governance so that business needs do not quietly erode the policy.

How Web Filtering Is Implemented

There are several common implementation patterns. A forward proxy can inspect and enforce web requests centrally, while a secure web gateway adds cloud-based policy enforcement, threat intelligence, and reporting. DNS filtering blocks or reroutes requests earlier in the lookup path, and browser or endpoint controls can apply policy even when the user is remote.

Category-based filtering is the usual operational model. Instead of maintaining a giant static list of URLs, defenders map destinations into classes such as generative AI, file sharing, gambling, malware, anonymity services, or uncategorised sites. That approach is easier to manage, but it depends on good classification and timely updates.

Exceptions matter as much as blocks. If bypass paths such as alternate DNS, personal proxies, or unsupported clients are left open, the control becomes inconsistent. Good implementations therefore combine policy enforcement with logging, reviewable exceptions, and detection of bypass attempts.

What Good Policy Looks Like

A useful web filtering policy is specific about who, what, and why. The same destination may be appropriate for one team and prohibited for another, so the policy should reflect business role, data sensitivity, and acceptable use rather than relying on a single universal rule set.

Logging is a core part of the design because the control is both preventative and evidential. Security teams need to know which categories are being accessed, which exceptions are being granted, and whether users are finding ways around enforcement. That visibility helps the organisation tune the policy without guessing.

For this reason, web filtering should be reviewed as an ongoing control lifecycle. New services, browser behaviors, encrypted DNS, and AI tools can change what users can reach faster than a static policy can keep up.

Risk and Threat Considerations

Web filtering reduces exposure, but it can also create blind spots if organisations assume the block itself is enough. Users may route around weak controls with personal devices, encrypted DNS, VPNs, proxies, or unsanctioned browser paths, and that bypass can defeat both data-loss prevention and malware reduction goals.

Failure mechanism: Policy gaps, weak exception handling, or incomplete enforcement let users reach destinations the organisation believes are blocked, which can expose sensitive information or allow access to risky content categories.

Impact: The result can be data leakage, shadow use of generative AI tools, exposure to malicious content, and poor visibility into where sensitive browsing activity actually occurs.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

NIST SP 800-53 Rev 5 and CIS Controls v8 set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
NIST SP 800-53 Rev 5AC-3 — Access EnforcementWeb filtering enforces policy-based access decisions to web destinations.
AU-2 — Event LoggingFiltering depends on logging access decisions and exception use.
Recommendation — Use AC-3 to enforce approved web access rules by user group, device, and policy context. Log allowed, blocked, and exception-driven web requests so policy drift can be reviewed.
CIS Controls v8CIS-9 — Email and Web Browser ProtectionsThis control family directly covers browser and web access protections, including filtering.
Recommendation — Apply CIS-9 safeguards to restrict risky web destinations and reduce exposure to malicious content.

Practitioner Guidance

Why practitioners should care: Web filtering only works when policy, enforcement, and logging line up. If the control is managed as a coarse internet block rather than a governed access layer, users will find inconsistent paths around it and the organisation will lose both protection and insight.

Governance implication: Treat exceptions as a formal decision, not an informal convenience. The policy should define which destinations are blocked by default, which user groups may be exempt, and how changes are approved and reviewed over time.

Practitioner takeaway: The strongest web filtering programmes are the ones that stay current with modern browsing paths, especially remote work, encrypted DNS, and AI service usage.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on October 31, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org