Protect telecom management servers from unauthorized change.

Not as a flat deadline. Regulation 12(c)(i) of SI 2022/933 lets a provider decide that a period of more than 14 days from when a patch or mitigation becomes available is appropriate, as long as the decision is taken at an appropriate governance level and recorded in writing. While a patch waits, Mimic stops unauthorized changes on protected servers at the point of execution.

Mimic Networks protects the servers that host network management, OSS and security critical functions, along with privileged access and jump servers and Active Directory. It protects Windows Server 2016 and later, and Red Hat Enterprise Linux 8 and later, so check each server against that floor. Network functions and network equipment stay out of scope, so the controls you run on them today keep that job.

For each change Mimic Networks blocks on a protected server, DashCam records each blocked attempt: what it tried to change, when and the process behind it. Your security team gets facts to work from after an incident, and your network security engineers see what tried to change a server that hosts a security critical function. Mimic also feeds enforcement events to your SIEM and SOAR platforms.

Ofcom's security report, published on GOV.UK on 6 March 2026, says the Code's measures are due for implementation between 31 March 2024 and 31 March 2028. Under the government's 2022 response, Tier 1 providers' more complex measures fall due by 31 March 2027 and the most complex by 31 March 2028. Mimic doesn't change those dates; it protects the servers while you work through them.