Web Filtering and ISO 27001

Internet Access Controls Explained
Team meeting in an office setting with text overlay reading “Web Filtering and ISO 27001.”

As organisations move to cloud‑first, remote‑enabled operating models, controlling how users access the internet has become a core information security and governance requirement—not just a productivity measure.

In recognition of this shift, ISO/IEC 27001:2022 introduced Annex A Control 8.23: Web filtering, formalising the expectation that organisations actively manage internet access to reduce cyber risk.

For many organisations, this has reframed web filtering from a technical decision into a compliance and audit‑readiness issue.

What Does ISO 27001 Say About Web Filtering?

ISO 27001 Annex A Control 8.23 – Web filtering requires organisations to manage access to external websites to reduce exposure to threats such as malware, phishing, and unauthorised data transfer.

In practice, auditors are no longer asking whether a web filtering policy exists—they are asking whether:

  • Internet access is actively controlled
  • Technical restrictions are in place
  • Risks are identified and treated
  • Controls are reviewed and improved over time

This shift reflects the reality that many security incidents begin with web‑based activity.

COMPLIANCE AS A SERVICE

Download the Board‑Ready ISO 27001 Compliance Pathway

A practical guide to treating ISO 27001 as an ongoing governance obligation — delivered through Compliance‑as‑a‑Service.

CaaS eBook Tile (2)

Why Internet Access Controls Matter in ISO 27001

Unrestricted internet access introduces multiple risk vectors, including:

  • Phishing and credential theft
  • Malware and ransomware delivery
  • Data leakage via cloud or AI tools
  • Use of illegal or non‑compliant services

ISO 27001 treats web filtering as part of a broader expectation that organisations understand where data flows, how users interact with online services, and what controls prevent misuse.

ISO 27001 Web Filtering Is About Risk Management — Not Productivity

A key misconception is that ISO 27001 web filtering is about blocking social media or time‑wasting websites.

In reality, the primary objective of Control 8.23 is risk reduction, including:

  • Preventing access to known malicious sites
  • Reducing exposure to drive‑by downloads and exploit kits
  • Limiting unsanctioned cloud or AI services
  • Providing audit evidence of active control

Auditors are focused on how risk is managed, not how restrictive policies appear

What Auditors Typically Look For

During an ISO 27001 audit, assessors commonly seek evidence of:

  1. Defined rules
    Clear criteria for allowed and disallowed categories of websites
  2. Technical enforcement
    Controls that actively block or restrict access—policies alone are insufficient
  3. Exception handling
    A documented process for legitimate business access
  4. Monitoring and review
    Logs, reports, and evidence of continual improvement

Organisations relying solely on user awareness or policy documents often fail to meet the intent of the control.

Where Legacy Web Filtering Falls Short for ISO 27001

Many legacy or DNS‑only filtering approaches struggle to satisfy modern audit expectations because they:

  • Cannot see activity inside encrypted HTTPS traffic
  • Do not provide visibility into cloud‑based applications
  • Fail to detect shadow IT or shadow AI usage
  • Lack usable reporting for auditors or leadership

As a result, organisations may technically “filter” the web, but still lack the evidence required for compliance.

This is why ISO 27001 increasingly aligns with modern web filtering and secure web gateway models, rather than static perimeter controls.

Modern Web Filtering and Secure Web Gateways in ISO 27001

Modern approaches typically include:

  • Identity‑aware web filtering
  • Inline inspection of web traffic
  • SaaS and cloud application visibility
  • Centralised logging and reporting

These capabilities help meet not only Control 8.23, but also broader ISO 27001 requirements around:

  • Access control
  • Supplier risk
  • Logging and monitoring
  • Continual risk treatment

Learn how this fits into a broader architecture in our guide to

👉 modern web filtering and secure gateways.

Web Filtering, Compliance‑as‑a‑Service, and Audit Readiness

For many organisations, implementing and maintaining these controls in‑house is challenging.

Compliance‑as‑a‑Service models help by:

  • Embedding web filtering into the ISMS
  • Maintaining documentation, evidence, and reporting
  • Aligning technical controls with risk registers
  • Supporting ongoing audits and leadership reporting

This approach turns web filtering from a point‑in‑time project into a living, defensible control.

👉 Learn more about Compliance‑as‑a‑Service and how it supports ISO 27001 outcomes.

Why ISO 27001 Web Filtering Is Now a Leadership Issue

ISO 27001 places accountability squarely on organisational leadership.

Without effective internet access controls:

  • Risk cannot be accurately assessed
  • Data exposure may go undetected
  • Audit findings become more likely

Modern web activity—including cloud services and AI use—means web filtering now sits at the intersection of cyber security, compliance, and governance.

Key Takeaway for ISO 27001 Programs

Web filtering under ISO 27001 is no longer optional or superficial.

Annex A Control 8.23 makes it clear that organisations must actively manage internet access using technical controls aligned to modern risk. Those relying on legacy approaches may meet policy requirements—but fall short on operational evidence.

To see how web filtering has evolved to meet these expectations, explore our

👉 modern web filtering as part of our Managed Cyber Security Service.

Frequently Asked Questions

1. Is web filtering required for ISO 27001 compliance?

Yes. ISO/IEC 27001:2022 mandates web filtering under Annex A Control 8.23 (Web Filtering). Organisations must implement controls to manage and restrict access to external websites that pose security, legal or operational risks. Failure to do so can result in audit findings and increased exposure to cyber threats.

Last updated:

2. What does ISO 27001 Annex A Control 8.23 require?

ISO 27001 Control 8.23 requires organisations to establish, implement and maintain web filtering controls that:

  • Restrict access to malicious, inappropriate or high-risk websites
  • Enforce acceptable use policies for internet access
  • Log and monitor web activity for security events
  • Review filtering rules regularly as risks and business needs change

Auditors expect documented policy, technical enforcement and evidence of ongoing governance.

Last updated:

3. Does DNS filtering satisfy ISO 27001 web filtering requirements?

No. DNS filtering can reduce risk by blocking known malicious domains, but on its own it usually lacks:

  • Visibility into user activity and accessed content
  • Category-based policy enforcement
  • Audit-ready reporting and historical evidence
  • Inspection of encrypted web traffic

ISO 27001 auditors typically expect broader web filtering controls that demonstrate enforcement, monitoring and review over time.

Last updated:

4. How does web filtering support ISO 27001 audit readiness?

Web filtering supports audit readiness by providing clear, demonstrable evidence that internet access risks are identified, controlled and reviewed. Logs, reports and policy records show auditors that controls are enforced consistently, monitored continuously and aligned with the organisation’s risk management and compliance objectives.

Last updated:

5. What are the business risks of inadequate web filtering under ISO 27001?

Insufficient web filtering increases exposure to malware, phishing and data leakage, and often leads to audit non-conformities. For executives, this can result in certification delays, regulatory scrutiny, operational disruption and reputational damage, all from risks that are typically considered preventable.

Last updated:

6. What evidence do ISO 27001 auditors expect for web filtering?

Auditors commonly look for:

  • A documented web filtering and acceptable use policy
  • Proof of technical enforcement and configuration
  • Logs and reports showing blocked activity and monitoring
  • Records of periodic reviews and updates
  • Evidence linking web filtering to incident detection and response

Centralised reporting and consistent record keeping are critical for audit defensibility.

Last updated:

7. Can web filtering be outsourced and still comply with ISO 27001?

Yes. ISO 27001 allows security controls to be outsourced, provided the organisation retains accountability. Contracts must define responsibilities, security requirements and review mechanisms, and the service must deliver consistent enforcement, monitoring and evidence to support ongoing compliance.

Last updated:

8. How often should web filtering policies be reviewed under ISO 27001?

Web filtering controls should be reviewed at least annually as part of the ISMS cycle, and sooner if risks, regulations or business operations change. Reviews are also expected after security incidents and during internal or external audits to confirm continued effectiveness.

Last updated:

Shadow AI & AI Governance Protection

For executives and technical leaders who need visibility and control

Your workforce is already using AI tools. The question is whether you can see it, govern it, and prevent data leakage.

If you're concerned about Shadow AI risk, AI governance gaps, or enabling AI safely without blocking innovation, we'll show you exactly what's happening in your organisation and how to protect it.

Request a demo to view real‑time visibility, protection, and governance controls

Reviewed by Bradley Kaine CEO of KMTech.  

More on Web Filtering from KMTech

Everything on this topic, in one place.

Last updated:

Related Stories

Cyber security professionals collaborating during a managed detection and response (MDR) planning session.

What Is Your MDR Actually Costing You?

Your MDR renewal quote is only part of the cost. See the three hidden costs to check before you sign, with ASD cyber threat report figures.

IT security analysts at KMTech reviewing SOC alerts, illustrating how alert fatigue in cyber security drives hidden operational and budget costs

Alert Fatigue Is a Budget Line, Not Just a Morale Problem

Alert fatigue is what happens when the volume of alerts, most of them low priority or false positives, is more than people can sensibly assess.

Financial services professional reviewing AI governance controls and professional indemnity insurance risk requirements.

PI Insurance and AI for Financial Services Firms

A guide for financial planners, accounting principals, and practice managers on the five AI governance questions PI insurers are asking at renewal, what evidence they want, what a gap costs you, and what the RI Advice precedent means for your cover.

Want to be part of the crowd?

html