EN/ABELCommunications
For UK enterprise prospects · regulator-auditable

Lawful intercept, by design.

A private mesh is only credible at scale if the regulator can audit it. EN/ABEL is built for the UK Investigatory Powers Act 2016 and the Telecommunications (Security) Act 2021 from the silicon up - warranted access only, sealed in a tamper-evident chain that IPCO, Ofcom and the ICO can verify end-to-end.

Lawful intercept & compliance

A closed loop the regulator can audit is not a threat. It is the upgrade.

EN/ABEL is built for the UK Investigatory Powers Act 2016, the Telecommunications (Security) Act 2021, the Wireless Telegraphy Act 2006 and Ofcom's General Conditions. We do not build around the regulator. We build with them - and we publish the mechanism by which they can verify it.

Warranted access
IPA 2016 compatible · silicon layer
Key custody
UK by default · dual-jurisdiction on request
Audit chain
SHA-256 · tamper-evident · regulator-exportable
Bulk access
None. Targeted warrants only
Oversight
IPCO, Ofcom, ICO - auditable on demand
Continuous evidence
NIS2 · ISO 27001 · GDPR · SOC 2 · TSA 2021

The legal frame, line by line

IPA 2016
UK statute
Investigatory Powers Act 2016

Targeted equipment interference & retention notices, served on telecommunications operators by the Secretary of State and reviewed by Judicial Commissioners.

EN/ABEL position · Warranted-access hooks at the silicon and SIM layer. Every served warrant is hash-chained into the audit ledger.
RIPA 2000
UK statute
Regulation of Investigatory Powers Act 2000

Lawful interception of communications by public authorities. Successor framework largely consolidated into IPA 2016 but still cited.

EN/ABEL position · Compatible interception interfaces (handover) maintained for warranted requests.
WTA 2006
UK statute
Wireless Telegraphy Act 2006

Licensing and use of radio spectrum in the UK. Enforced by Ofcom.

EN/ABEL position · Operates in licence-exempt and partner-licensed bands. No pirate spectrum, ever.
Comms Act 2003
UK statute
Communications Act 2003

General Conditions, designated vendor regime, network security duties.

EN/ABEL position · Designated-vendor compliant supply chain. UK key custody. No high-risk-vendor cores.
TSA 2021
UK statute
Telecommunications (Security) Act 2021

Security duties on public electronic communications providers; Ofcom enforcement of the Telecoms Security Code of Practice.

EN/ABEL position · Tamper-evident audit chain meets the Code's evidence requirements out of the box.
UK GDPR + DPA 2018
UK statute
Data Protection Act 2018

Lawful basis, data minimisation, retention, breach notification.

EN/ABEL position · Row-level lawful-basis tagging. Auto-emitted breach notification within seconds, not 72 hours.

Questions a regulator (or your in-house counsel) will actually ask

Is EN/ABEL a 'closed network' that the UK government cannot access?
No. EN/ABEL is a private mesh, not an extra-judicial one. We comply with the Investigatory Powers Act 2016 and the Telecommunications (Security) Act 2021. A properly served warrant, signed by the Secretary of State and approved by a Judicial Commissioner, is honoured at the silicon layer - and recorded in a tamper-evident audit chain so the Investigatory Powers Commissioner's Office can verify it after the fact.
Then how is it different from a normal telco?
Two ways. First, lawful access is warranted only - there is no bulk back-door, no marketing pipe, no third-party data resale. Second, every access is sealed into a SHA-256 hash chain that the regulator can audit end-to-end. Today's incumbents cannot prove what was accessed and by whom. We can.
What does 'tamper-evident' actually mean?
Every audit row carries the hash of the previous row. Re-writing any single event invalidates every hash that follows it, and that breakage is detectable by IPCO, Ofcom or an independent auditor in seconds. We publish the verification function - abel_verify_chain() - so anyone with read access can confirm the chain has not been altered.
Who holds the keys?
UK key custody by default. Sovereign deployments can elect dual-jurisdiction custody (for example UK + UAE) at procurement time. Keys never leave designated facilities; rotation is sub-minute under attack signal.
Could you operate outside the UK on different rules?
Yes - with the destination country's regulator, not around them. Each deployment is configured to the lawful-access regime of the jurisdiction it serves. We do not run a single global policy that quietly applies UK rules to UAE traffic, or vice versa.
What about Ofcom General Conditions and emergency calling (999/112)?
Full compliance with General Condition A3 (emergency calls), C1 (information for consumers), and the network security duties under the TSA 2021 Code of Practice. Emergency calling is preserved end-to-end, including over the mesh fallback path.
Is the network 'unhackable'?
No. We do not use that word and you should not trust anyone who does. EN/ABEL is built so that (a) the attack surface is smaller than a public Internet hop, (b) compromise is detected sub-second by the per-SIM behavioural baseline, and (c) any compromise is contained sub-minute by the SIM kill-switch. That is the honest claim.
What evidence can you give a regulator on day one?
On request we provide: (1) the live audit chain export sealed by abel_verify_chain(), (2) the policy compiler output showing which roles can read which rows, (3) a signed continuous-compliance bundle covering NIS2, ISO 27001, GDPR, SOC 2 and the TSA 2021 Code, and (4) the most recent independent pen-test run from the platform's own pen-test runner.
This page is an explainer, not legal advice. Enterprise and sovereign customers receive a per-deployment Lawful Intercept & Evidence Pack signed by our compliance team and reviewable by your DPO and external counsel before contract.