Summary
- The Telecommunications (Security) Act 2021 writes security duties into the Communications Act 2003 in the language of outcomes: measures “appropriate and proportionate”, reports sent “as soon as reasonably practicable”.
- The regulator's own share of the same duty is phrased as an effort — “OFCOM must seek to ensure” that providers comply (section 105M) — and the only publication the sections read here compel is a statement of general policy (section 105Y).
Two duties, two grammars
There is a sentence buried in the middle of the Telecommunications (Security) Act 2021 that tells you more about how British telecoms security is actually accounted for than any of the headlines that greeted the Bill. It is five words long, and it is addressed to the regulator rather than to the industry: “OFCOM must seek to ensure”.
Around that sentence sits a working regime. Section 1 of the Act substitutes new sections 105A to 105D into the Communications Act 2003, and the first of them is written for an operator, not for a courtroom. The provider of a public electronic communications network or service, it says, “must take such measures as are appropriate and proportionate for the purposes of— (a) identifying the risks of security compromises occurring; (b) reducing the risks of security compromises occurring; and (c) preparing for the occurrence of security compromises” (section 1).
Read that closely and you can see what the drafters thought they were doing. They did not specify a firewall, a patch window, a segmentation standard or a staff-training quota. They named three purposes and handed the operator the adjective. Appropriate and proportionate to what? To the network, the service, the risk and the provider's own scale — none of which the subsection quantifies. This is a duty that can be breached, but it cannot be complied with by ticking a box, because no box is described.
The report goes one way
Section 4 is where the accountability chain becomes visible, and where it becomes thin. It inserts two duties that sit oddly beside each other. The first, section 105J, faces outward: where there is a significant risk of a security compromise, the provider “must take such steps as are reasonable and proportionate for the purpose of bringing the relevant information, expressed in clear and plain language, to the attention of persons who use the network or service and may be adversely affected by the security compromise” (section 4).
The second faces the regulator, and only the regulator. Section 105K(1) requires the provider to “inform OFCOM as soon as reasonably practicable of— (a) any security compromise that has a significant effect on the operation of the network or service”. Note the direction of travel. The user duty is triggered by a risk; the OFCOM duty is triggered by an effect. Note also who defines the effect: “a significant effect on the operation of the network or service” is a threshold the operator applies to its own network before anyone outside it hears anything.
The excerpt of section 105K(1) held for this article ends at paragraph (a), so the full list of reportable matters was not read here and is not characterised. What the read text does establish is the addressee. Nothing in section 105K as read obliges the provider to publish the report, to notify the public at the moment of the compromise, or to hand the same account to anyone other than OFCOM.
The soft verb
Now the sentence. Section 5 inserts section 105M: “OFCOM must seek to ensure that providers of public electronic communications networks and public electronic communications services comply with the duties imposed on them by or under sections 105A to 105D, 105J and 105K” (section 5).
“Seek to ensure” is not a drafting accident, and it is not nothing. It obliges the regulator to try, and a regulator that did not try would be in breach of its own duty. But compare it with the verb loaded onto the industry in the same statute. The provider must take the measures. It must inform OFCOM. It must bring information to users' attention. OFCOM must seek to ensure. One side of this regime carries an obligation of result; the other carries an obligation of effort. Parliament knew how to write the stronger form and chose it for the party with the equipment.
Enforcement by cross-reference
Which leaves the question a board actually asks: what happens when a provider does not do it? Section 7 answers by borrowing. Section 105S(1) provides that “Sections 96A to 100, 102 and 103 apply in relation to a contravention of a security duty as they apply in relation to a contravention of a condition set under section 45, other than an SMP apparatus condition” (section 7).
The security duty does not get a bespoke enforcement ladder. It gets the general-conditions ladder, wheeled in whole by a single subsection that names seven sections and excludes one class of apparatus condition. That is efficient drafting and it is also an accountability decision: the price of breaking a security duty is whatever the price of breaking a general condition is, and a reader who wants the number has to leave this statute and go and find it.
Sections 96A to 96C of the Communications Act 2003, which would supply the ceiling, were not read in this run, so no penalty figure, no percentage of turnover and no enforcement outcome is stated here. The cross-reference is precise; the amount is simply somewhere else.
One document, and it is a policy
Then there is section 10, and this is the part that should be read twice. Section 105Y(1) provides that “OFCOM must prepare and publish a statement of their general policy with respect to the exercise of their functions under sections 105I and 105M to 105V” (section 10). Subsection (4) closes the loop: “In exercising their functions under sections 105I and 105M to 105V OFCOM must have regard to the statement for the time being in force under this section.”
So the regulator must write down its own policy, publish it, and then hold itself to it. That is a real commitment and it is worth saying plainly, because the statutory architecture around it is thinner than most readers of a security story would expect. Across the six documents in the source set — the contents page and the five section pages cited above — the only instrument the text obliges OFCOM to publish is that statement of general policy. No provision read here obliges OFCOM to publish incident reports, enforcement outcomes or provider-level compliance data.
The public guarantee in this chain is a published intention, not a published record.
Whether OFCOM has in fact published its section 105Y statement was not established for this article. Three attempts to find a readable copy failed on provider capacity and a permission error, and silence in the material actually read is not evidence that the regulator has failed to publish anything. The gap is in my retrieval, not necessarily in OFCOM's record.
The same honesty applies to the rest of the Act's machinery. The contents page lists section 3 (codes of practice about security measures), section 6 (powers of OFCOM to assess compliance) and section 8 (civil liability for contravention of security duties) (contents), but only those headings were read here. Their operative content is unknown, and a code of practice or an assessment power could add duties and evidence routes that change the calculation. This article does not pretend otherwise.
What the retrieval itself shows
Two Ofcom pages on network resilience and telecoms security were attempted on 16 November 2026 and returned no readable text to the retrieval session. That is a fact about the retrieval, not about what the pages contain, and their addresses are deliberately not cited here because their existence and content were never verified. Anyone claiming from this article that OFCOM publishes nothing on the subject would be claiming something the evidence does not support and the article does not say.
The delta, and the shape of the perimeter
Our own archive does not help fill the gap. A phrase search of BTW's published articles for “Ofcom network resilience outage reporting” on 16 November 2026 returned no matching piece, while the Ofcom directory entry counts 120 articles. Those 120 are not characterised here; this article works only the statutory security-duty chain that sections 1, 4, 5, 7 and 10 of the 2021 Act insert, and it says nothing about any provider's conduct, any outage, or any enforcement action that may or may not exist.
What remains is a perimeter of a particular shape, and it is worth naming precisely because it is easy to mistake for a wall. A provider that ignores its security duties is in breach of a statutory obligation and faces whatever the general-conditions regime supplies — imported, not restated. A provider that suffers a significant compromise must tell OFCOM quickly, and must tell affected users clearly when there is a significant risk. Neither duty creates a public document. The regulator must try to secure compliance, must publish its policy, and must then have regard to that policy.
An outsider wanting to know whether the regime works has one instrument to read and one institution to trust.
That is not a scandal. It is a design, and the design has a coherent logic: security duties are hard to specify in advance, so the statute sets purposes and proportions rather than standards, and puts the judgment where the network is. But the logic has a price, and the price is legibility. The classification of this regime — soft, or merely differently instrumented — turns on evidence that does not exist in the text. Publish one incident report, or one enforcement outcome under section 105S, and the perimeter moves from intention to record. Until then, the strongest sentence in British telecoms security law is a promise to try.
Member Briefing
Read the full trend briefing
Members read the full briefing with the source notes behind every finding.
Strategic Circle
A daily briefing in your language, built from changes we have verified.
Join for USD 20/monthCancel anytime.
Members also get the full research library, a daily briefing on the networks they follow and the private forum.






