Opens in a new tab
UK telecoms staff reviewing equipment for Ofcom telecoms security enforcement

Ofcom Telecoms Security Enforcement: UK Rules and Fines in 2026

Ofcom telecoms security enforcement applies to UK public telecoms network and service providers under the Telecommunications (Security) Act 2021. The detailed security regulations took effect on 1 October 2022 Electronic Communications (Security Measures) Regulations 2022. Ofcom telecoms security enforcement includes monitoring provider compliance. Providers must manage security risks and be able to explain their measures. Organisations that merely buy connectivity are not, for that reason alone, public telecoms providers.

  • Scope: Ofcom telecoms security enforcement covers providers of public telecoms networks and services across the UK, not every organisation that uses them.
  • Key dates: The regulations took effect on 1 October 2022; the current Code is version 1.1 Telecommunications Security Code of Practice.
  • Regulator: Ofcom monitors provider compliance, investigates suspected failures and can demand information about security measures.
  • Provider duties: Public providers must manage compromise risks, apply the regulations and account for how their security measures meet statutory duties.
  • Penalties: Security breaches can attract fines of up to 10 per cent of relevant turnover, or £100,000 per day for continuing failure Ofcom enforcement announcement.
  • Outside scope: A private-only network is outside these public-provider duties. Smaller public providers remain covered, even where detailed Code measures are not expected Telecommunications (Security) Act 2021.

🚨 What is Ofcom telecoms security enforcement?

Ofcom telecoms security enforcement is the statutory system for supervising and enforcing security duties on UK public telecoms providers. Section 105A of the Communications Act 2003 requires appropriate and proportionate measures to identify and reduce security compromise risks and prepare for compromises Telecommunications (Security) Act 2021. The duties concern network and service security, not only malicious intrusions.

The Electronic Communications (Security Measures) Regulations 2022 prescribe further measures alongside those overarching duties Department for Science, Innovation and Technology review. Providers therefore need to read the Act and regulations together. Our Telecommunications Security Act overview explains the wider statutory framework, while this article focuses on supervision, information requests and enforcement.

The Department for Science, Innovation and Technology issued version 1.1 of the Telecommunications Security Code of Practice on 14 July 2026 Telecommunications Security Code of Practice. The Code gives detailed guidance; it does not replace statutory duties. Section 105S connects contraventions of listed security duties to established Communications Act enforcement provisions statutory enforcement provisions. Compliance rests on the legal duties, not a provider’s choice to adopt the Code.

⚖️ Who is covered by Ofcom telecoms security enforcement?

Ofcom telecoms security enforcement covers providers of public electronic communications networks and public electronic communications services in the UK. A business does not become a public provider simply by buying broadband or operating an internal network. The provider’s actual network or service determines whether the statutory duties apply; commercial labels alone do not settle the question.

The Telecommunications Security Code of Practice directs its detailed measures at the largest, Tier 1 providers and medium-sized, Tier 2 providers. Tier 2 providers have more time for some measures. Smaller Tier 3 providers are not expected to follow the detailed Code measures Telecommunications Security Code of Practice. That distinction concerns Code expectations, not an exemption from duties applying to public providers.

The Department for Science, Innovation and Technology describes the Code’s detailed guidance as directed at providers with relevant turnover of at least £50 million statutory call for evidence. Providers near a tier boundary should establish the relevant turnover and record why they classify themselves as they do. Our telecoms security Code analysis gives the measures more space; the enforcement question is whether the provider can justify its security position.

Lightbulb Icon Key Takeaway

Tier 3 means lighter expectations under the detailed Code, not freedom from statutory security duties.

🗓️ When do the duties and reporting changes apply?

The statutory framework is already in force: the Electronic Communications (Security Measures) Regulations 2022 commenced on 1 October 2022 security measures regulations. UK public providers should not wait for a new enforcement policy before meeting their duties. The current Code is version 1.1, issued on 14 July 2026 Telecommunications Security Code of Practice; that revision is separate from commencement of the regulations.

Desk clock beside telecoms test leads and an incident folder

Ofcom consulted on revisions to its policy under section 105Y of the Communications Act 2003, including its supervisory approach and expectations for reporting security compromises. Its consultation page still showed a pending statement when updated on 1 October 2026 Ofcom policy consultation. A provider should distinguish the published proposal from current requirements and check for a final statement before changing its reporting process.

The consultation included a proposed 72 hour incident reporting form Ofcom reporting consultation. A proposed form does not, by itself, establish a universal reporting deadline for every telecoms security incident. Providers need a process that assesses each compromise against the applicable current reporting requirements and preserves the reasoning behind the decision.

The Department for Science, Innovation and Technology also closed a statutory call for evidence on the framework on 12 October 2026 telecoms security call for evidence. A call for evidence is not an amendment to the Act or regulations. Compliance plans should separate binding duties, current Code guidance and possible policy changes, with an owner assigned to watch for published decisions.

✅ What must providers do and show Ofcom?

Providers must take appropriate and proportionate steps to identify and reduce compromise risks and prepare for compromises under section 105A of the Communications Act 2003 Telecommunications (Security) Act 2021. The regulations add specific security measures Department for Science, Innovation and Technology review. A documented decision matters because Ofcom may ask not just whether a control exists, but how it addresses a provider’s risks.

AreaRequirement or expectationPractical evidence
Risk managementIdentify and reduce compromise risksRisk decisions, control ownership and review records
PreparednessPrepare for security compromisesResponse arrangements and tested escalation routes
Prescribed measuresApply the security regulationsImplementation records and documented exceptions
Code guidanceAssess applicable tier expectationsA mapped assessment and reasons for departures
Regulator requestsAnswer information notices as requiredVerified responses and supporting records
Security duties and the evidence a public provider should be ready to explain

Section 135 of the Communications Act 2003 lets Ofcom require information it considers necessary for its functions. A recipient must respond in the manner and within the reasonable period specified Communications Act information powers. Assign responsibility for checking submissions against underlying records before they go to the regulator. The answer should say what is implemented, what remains outstanding and how any uncertainty was checked.

Our cyber security strategy support can help teams organise risk decisions and control ownership. For providers assessing how they detect and escalate compromises, round-the-clock security monitoring addresses a different part of the problem. Neither service changes the provider’s responsibility to meet its legal duties or answer Ofcom accurately.

🧩 What penalties can Ofcom impose?

Ofcom telecoms security enforcement can include substantial penalties for breaches of security duties. Its published summary gives a maximum of 10 per cent of relevant turnover for a breach, or £100,000 per day for a continuing failure Ofcom enforcement announcement. Those are ceilings, not automatic fines. The applicable duty and enforcement route matter when assessing exposure.

Compliance professional checking records beside telecoms testing equipment

Section 105T of the Communications Act 2003 sets the £100,000 daily maximum for continuing contraventions of most security duties, with an exception for duties imposed by section 105I statutory penalty provisions. Providers should not apply that daily figure to every type of information failure. The statute distinguishes security-duty enforcement from other failures that Ofcom may investigate.

Ofcom separately says that failure to provide information, or refusal to explain a failure to follow a code of practice, can attract a maximum £10 million fine or £50,000 per day for a continuing failure Ofcom enforcement announcement. An information request is an enforcement risk in its own right. Legal and security teams should check the notice, its deadline and the accuracy of every factual response.

Ofcom can also require interim steps to address security gaps while enforcement is under way Ofcom enforcement announcement. A provider facing scrutiny therefore needs to manage the underlying security issue while responding to the investigation. A penalty is not the only possible consequence: mandated action may demand immediate operational attention.

Lightbulb Icon Key Takeaway

Separate penalties for security-duty breaches from those for information and Code-explanation failures; do not assume one ceiling applies to every notice.

⚙️ How do Ofcom telecoms security enforcement investigations work?

Ofcom telecoms security investigations can examine both operational resilience and the accuracy of information supplied by a provider. Supervision does not always become a formal investigation. In its report covering October 2024 to October 2025, Ofcom identified difficulties with provider supply chains and pre-contract equipment testing, but did not consider those findings serious enough to open compliance investigations Ofcom security report.

Telecoms incident team examining a network module and records

The regulator fined BT £17.5 million after finding it was inadequately prepared for a failure of its emergency call handling service Ofcom BT decision. Ofcom identified insufficient warning systems and inadequate procedures for assessing and mitigating the incident. The decision shows why a provider’s preparations for service failure matter even where the issue is not described as a cyber attack.

In a separate matter, Ofcom opened an investigation into Tata Communications (UK) Limited concerning its response to a statutory information request about security measures Ofcom Tata investigation. Ofcom said some information might not have been complete or accurate. An open investigation is not a finding of wrongdoing. The case illustrates why a provider should verify its submissions before sending them.

Section 135 of the Communications Act 2003 gives Ofcom the power to request necessary information and specify a reasonable response period Communications Act information powers. When a notice arrives, preserve the relevant records, identify who can confirm each answer and keep an account of unresolved points. Our security operations centre guide discusses the monitoring function that can support incident records.

🧭 How should UK providers prepare for Ofcom scrutiny?

UK public providers should prepare for Ofcom telecoms security enforcement by mapping each applicable duty to an owner, a control and evidence that the control works. Start with the Act and regulations, then assess the current Code against the provider’s tier. Record why any detailed Code measure is not followed and how the underlying statutory duty is met.

Telecoms staff testing spare equipment and cables before installation

Test whether incident staff can recognise a possible security compromise, escalate it and make a defensible reporting decision. Keep the assessment and the information used to reach it. The proposed revisions to Ofcom’s reporting policy should remain on the watch list, but should not displace current requirements before a final policy is confirmed.

Examine dependencies on other providers and equipment suppliers before assuming a contract settles responsibility. Ofcom has identified difficulties where providers supply other providers and where equipment needs pre-contract testing Ofcom security report. Procurement, engineering and compliance teams need a shared account of what was assessed, what remains untested and who accepted the risk.

Finally, rehearse the response to an Ofcom information notice: find the records, confirm facts with technical owners and review the submission for gaps. Our UK cyber protection measures article offers a broader operational perspective. For telecoms providers, the immediate test is narrower: can the organisation demonstrate its security decisions and give the regulator an accurate answer?

❓ Frequently asked questions

What telecoms security rules does Ofcom enforce?

Ofcom telecoms security enforcement covers statutory duties on UK public telecoms providers under the Communications Act 2003, as amended by the Telecommunications (Security) Act 2021. The Electronic Communications (Security Measures) Regulations 2022 add specific measures. The Telecommunications Security Code of Practice provides detailed guidance for the providers it addresses; it does not replace the Act or regulations.

Is there a 72 hour deadline for reporting telecoms security incidents?

Do not treat 72 hours as a universal legal deadline based on Ofcom’s proposed form. Ofcom included a 72 hour incident reporting form in its consultation on revised guidance Ofcom reporting consultation. Providers should apply the currently applicable reporting requirements to each compromise and check whether Ofcom has since published a final policy.

What are Ofcom’s maximum fines for telecoms security breaches?

For a breach of security duties, Ofcom gives a maximum of 10 per cent of relevant turnover, or £100,000 per day for a continuing failure Ofcom enforcement announcement. Different ceilings apply to some information and Code-explanation failures. The maximum is not the expected penalty in every case; the duty and enforcement route must be identified first.

Does a Tier 3 provider have to follow the security Code?

Tier 3 public providers are not expected to follow the detailed measures in the Telecommunications Security Code of Practice Telecommunications Security Code of Practice. They are not exempt from statutory security duties merely because those detailed Code measures are not expected. A provider should establish its tier and be able to explain how its own measures satisfy applicable duties.

Can Ofcom fine a provider for giving incomplete information?

Information failures can create a separate risk under Ofcom telecoms security enforcement. Ofcom investigated whether Tata Communications (UK) Limited complied with a statutory information request after indicating that some answers might have been incomplete or inaccurate Ofcom Tata investigation. That investigation is not a finding of wrongdoing. Providers should verify responses against records and comply with the notice they receive.

What evidence can Ofcom demand under section 135?

Section 135 of the Communications Act 2003 permits Ofcom to require information it considers necessary for its functions, including specified security functions. The recipient must comply in the manner and within the reasonable period Ofcom specifies Communications Act information powers. The scope of a particular request depends on its notice; providers should read it closely and validate their answers.

Has Ofcom’s revised section 105Y enforcement policy taken effect?

Ofcom’s consultation page still marked the proposed revisions as pending a statement when it was updated on 1 October 2026 Ofcom policy consultation. That update does not establish that the proposal took effect. Providers should check for a subsequent final statement and keep proposed reporting changes separate from duties already in force.

Contact Us

Share this post

About the Author

Josh Lipscombe Junior SOC Analyst headshot

Josh Lipscombe

SOC Analyst

  • BSc Computer Science with Cyber Security
  • Sentinel One Incident Response Engineer (SIREN)
  • Microsoft SC – 200: Security Operations Analyst
  • Microsoft SC – 300: Identity and Access Administrator Associate

Josh Lipscombe

A First Class Honours graduate in BSc Computer Science with Cyber Security from the University of Kent, Josh is passionate about safeguarding organisations from digital threats. With hands-on expertise in SentinelOne’s AI-powered EDR platform, Microsoft security tools, and scripting languages, he delivers a proactive, detail-oriented approach to incident response and automation.

Josh has supported clients through critical cyber incidents, applying a systematic, solution-focused methodology, from detection and triage to rapid remediation. In Security Operations, he has a wide range of experience, from client onboarding and incident resolution to using and developing automation playbooks to streamline processes. His background in preemptively hunting for vulnerabilities means that he is proactively looking to prevent cyber incidents across our client’s networks.

View Profile
Author
Josh Lipscombe Junior SOC Analyst headshot

Josh Lipscombe

SOC Analyst

Category
Published
Nov 20 - 2026
Cypro firewall showing robust network security
Secure your business.
Elevate your security, accelerate your growth. We take care of cyber security for high-growth companies, at every stage of their journey.
Get in touch
Related Posts
View All Posts
  • UK security lead comparing cyber security consultancy UK proposals at a desk
    Cyber security consultancy UK: choosing the right support

    Compare independent consultants, Cyber Advisors and consultancy firms in the UK. Learn which fits your risks, what to check and…

  • Cyber security advisory discussion beside a service map in a UK office
    Cyber Security Advisory: Scope, Costs and UK Choices

    Learn what cyber security advisory covers, when your UK organisation needs it, how it differs from testing and what determines…

  • UK buyers comparing cyber security consulting firms using paper proposals
    Cyber security consulting firms: choosing a UK provider

    Compare independent consultants, specialist firms and large consultancies in the UK. Learn which fits your scope, how to check assurance…

CyPro Cookie Consent

Hmmm cookies...

Our delicious cookies make your experience smooth and secure.

Privacy PolicyOkay, got it!

We use cookies to enhance your experience, analyse site traffic, and for marketing purposes. For more information on how we handle your personal data, please see our Privacy Policy.

Schedule a Call