UK-TSA-MON-01 | Security Monitoring | 23 |
UK-TSA-MON-02 | Incident Notification | 54 |
UK-TSA-MON-03 | Ofcom Enforcement | 0 |
UK-TSA-NET-01 | Security Architecture | 90 |
UK-TSA-NET-02 | Access Control and Authentication | 68 |
UK-TSA-NET-03 | Supply Chain Security | 43 |
UKTSA-1 | Security Duties (Sections 105A-D) | 0 |
UKTSA-2 | Code of Practice and Network Architecture | 0 |
UKTSA-3 | Supply Chain and Equipment Security | 0 |
UKTSA-4 | Incident Reporting and Ofcom Cooperation | 0 |
ACT | Communications Act 2003 ss.105A to 105Y as inserted by the 2021 Act: security duties of network and service providers (in force 1 October 2022) | 0 |
COP | Telecommunications Security Code of Practice v1.1 (July 2026): measure groups and their Tier 1 and Tier 2 dates | 0 |
DVD | Designated vendor directions, ss.105Z1 to 105Z29 (in force 17 November 2021) | 0 |
ENFORCE | Enforcement and penalties | 0 |
FRAMEWORK | The telecoms security framework and its three layers | 0 |
M1 | M1.01 to M1.06 Exposed edge: records of external systems, two-yearly testing, and separation from security critical functions | 0 |
M10a | M10.01 to M10.19 Third party supplier contracts: records, shared responsibility, control of data, 48-hour incident notice, 30-day root cause and managed service exit | 0 |
M10b | M10.20 to M10.35 Third party administrators: mediated, ticketed and logged access, per-provider segregation and testing of the administrator | 0 |
M10c | M10.36 to M10.54 Equipment suppliers and patching: security declarations, secure deployment guidance, support periods, vulnerability fixes and 14-day patching of exploited flaws | 0 |
M11 | M11.01 to M11.42 Management plane: formal change, ticketed time-bound privileged access, break-glass controls, segregated management plane and hardened privileged access workstatio | 0 |
M12 | M12.01 to M12.05 Signalling monitoring: monitor and analyse signalling, protect signalling records, alert others and fuzz interfaces | 0 |
M13 | M13.01 to M13.28, M19.01 to M19.07 Virtualisation: locked-down fabric, trust domains and host pools, no containers as trust boundaries, and automated, attested administration | 0 |
M14 | M14.01 to M14.03 End-of-life equipment conditions, blocking unauthorised SIM over-the-air messages, and security retained after upgrades | 0 |
M15 | M15.01 to M15.13 Network oversight functions: patched, rebuilt from known-good state, on trusted platforms, managed only from privileged workstations and monitored | 0 |
M16 | M16.01 to M16.22, M20.01 Security monitoring and analysis: skilled analysts, threat hunting, 13-month logs, near real-time analysis within five minutes and anomaly models | 0 |
M17 | M17.01, M18.01 to M18.06 Administration through systems, not direct device access; signalling resilience, hub addressing, authenticated outgoing signalling and hidden topology | 0 |
M2 | M2.01 to M2.06, M6.01 to M6.05 Privileged access basics: review, logging, secure protocols, unique accounts, MFA and no default or hardcoded accounts | 0 |
M21 | M21.01 to M21.07 Retaining national resilience: UK-located oversight functions, UK capability, offshore data governance and one month of UK connectivity without international links | 0 |
M22 | M22.01 to M22.04 New v1.1 measures by March 2028: further CAF processes, test network default passwords and permitted signalling for fixed networks | 0 |
M23 | M23.01 to M23.03 New v1.1 measures by December 2028: SIM provider certificate checks, automated vulnerability scanning and validated automation pipelines | 0 |
M24 | M24.01 to M24.09 New v1.1 measures by December 2029: logging tests, number analysis data, threat modelling, trusted boot, CPE anomaly blocking, service accounts, APIs and unused se | 0 |
M3 | M3.01 to M3.19, M7.01 to M7.04 Signalling and routing security: understand and filter signalling, do not trust source addresses, secure BGP and prevent spoofing | 0 |
M4 | M4.01 to M4.08, M8.01 to M8.16 Procurement and SIM risk: assess suppliers before contract, test security, track end-of-life equipment, and protect SIM keys | 0 |
M5 | M5.01 to M5.07 Supporting business processes: CAF-based processes, prioritised security changes, restorable read-only backups and incident management | 0 |
M9 | M9.01 to M9.06 Customer premises equipment: unique credentials, supported devices, restricted and secure management, inbound connections blocked | 0 |
REG | Electronic Communications (Security Measures) Regulations 2022, SI 2022/933 (in force 1 October 2022) | 0 |
STATUS | Status in September 2026 | 0 |
TIERS | Tiers and the legal effect of the Code of Practice | 0 |
r10 | reg.10 Govern security from board level: policy, incident categorisation, risk reporting, post-incident review and insider risk | 0 |
r11 | reg.11 Review security measures regularly and produce a written 12-month risk assessment at least yearly | 0 |
r12 | reg.12 Deploy patches and mitigations in a time suited to severity, and record governance decisions to take longer than 14 days | 0 |
r13 | reg.13 Ensure responsible persons are competent and resourced, and configure new supplier equipment securely | 0 |
r14 | reg.14 Carry out realistic, unannounced security testing, including of people and physical access | 0 |
r15 | reg.15 Share information about compromises that may affect other networks, and give and request assistance | 0 |
r3a | reg.3(1) to (4) Design, redesign and maintain the network to reduce security risk, and record risks and exposure yearly | 0 |
r3b | reg.3(3)(d), (e), 3(5) Protect and appropriately locate security critical functions, secure equipment through its lifecycle, and contain compromises | 0 |
r3c | reg.3(3)(f) Be able to identify risks and operate the network without reliance on persons, equipment or data outside the UK | 0 |
r4a | reg.4(1) to (4)(a) Protect operational data and network functions, and keep privileged workstations away from incoming signals | 0 |
r4b | reg.4(4)(b), (c), 4(5) Monitor and reduce risks from incoming signals and customer equipment, and use encrypted signals within the network | 0 |
r4c | reg.4(6), (7) Service providers: monitor and reduce SIM card risks and replace SIMs where appropriate | 0 |
r5 | reg.5 Keep real-time monitoring and content analysis tools out of reach of the listed countries | 0 |
r6a | reg.6(1), (2) Monitor and analyse access to and operation of security critical functions, automated where possible, and investigate anomalies | 0 |
r6b | reg.6(3) Record all access to security critical functions, alert on manual changes, analyse promptly and keep data 13 months | 0 |
r6c | reg.6(4) Record type, location, software, hardware and identifiers of equipment supplied to customers | 0 |
r7a | reg.7(1) to (3), 7(4)(a) Identify and reduce third party supplier risk and bind suppliers contractually to security measures | 0 |
r7b | reg.7(4)(b), (c), 7(5) Secure supplier connections and data sharing, plan exits, and keep a written plan for supply interruption | 0 |
r8a | reg.8(1), (2) Reduce unauthorised access: multi-factor authentication, two-person changes, no default credentials, automated changes | 0 |
r8b | reg.8(3) to (5) Isolate security critical functions from unsafe signals and keep security permissions and credentials minimal, individual and unique | 0 |
r8c | reg.8(6) Give no security permission to anyone while in a listed country, and prevent its use from there | 0 |
r9a | reg.9(1), (2)(a), (b), (3) Prepare to limit and recover from compromises, keeping online and offline copies in the UK | 0 |
r9b | reg.9(2)(c) Have means to assess, contain and deal with compromises, including a written plan when effects cannot be prevented within 14 days | 0 |
s105A | s.105A Take appropriate and proportionate measures to identify, reduce and prepare for security compromises | 0 |
s105C | s.105C Take measures to prevent adverse effects of a compromise and remedy or mitigate its effect | 0 |
s105I | s.105I When notified by OFCOM, explain any failure to act in accordance with the Code of Practice | 0 |
s105J | s.105J Tell affected users of a significant risk of a security compromise, in clear and plain language | 0 |
s105K | s.105K Inform OFCOM as soon as reasonably practicable of significant security compromises | 0 |
s105L | s.105L(6) to (8) Comply with OFCOM directions to inform users or the public of a security compromise | 0 |
s105N | ss.105N, 105O, 105P Cooperate with OFCOM security assessments and comply with assessment notices | 0 |
s105U | ss.105U, 105V Take interim steps directed by OFCOM pending enforcement | 0 |
s105Z1 | ss.105Z1 to 105Z3 Comply with the requirements of a designated vendor direction | 0 |
s105Z14 | ss.105Z12, 105Z14, 105Z15 Comply with OFCOM inspection notices on designated vendor compliance, without defeating them, and pay their costs | 0 |
s105Z25 | ss.105Z22 to 105Z25, 105Z27 Obey urgent enforcement directions, keep directions confidential when required, and supply information on request | 0 |
s105Z7 | s.105Z7 Prepare and provide a compliance plan when the Secretary of State requires one | 0 |