Mimic Networks for the public sector
Protect a federal server you can't patch yet by controlling what can change on it while the fix moves through testing and change control. Mimic Networks checks each change to a protected Windows or Linux server against its known-good profile and stops unauthorized ones at the point of execution. By 7 December 2026, BOD 26-04 has agencies remediating on CISA's timelines.
The servers
Mimic Networks protects the servers that host mission applications, on Windows Server or Red Hat Enterprise Linux. Each one gets a Mimic node and its own known-good profile, and you choose which servers go first.
Workstations, laptops, mobile devices and network devices stay out of scope.
The rules
Binding Operational Directive 26-04, issued 10 June 2026
This Directive supersedes and hereby revokes BOD 19-02 ... and BOD 22-01
Source: CISA, read 26 October 2026.
Context. Programs and pages that still cite BOD 22-01's deadlines are out of date. BOD 26-04's Table 1 sets the timelines now.
Start here
Who we help
BOD 26-04 sets the remediation clock, and a fix still has to clear testing and change control. Mimic stops unauthorized changes on protected servers at the point of execution while it does.
Some mission servers won't migrate off Windows Server 2016 before 12 January 2027. Mimic keeps supporting Windows Server 2016 after Microsoft's Extended Support ends on 12 January 2027.
Proof
DashCam records each blocked attempt: what it tried to change, when and the process behind it, so a test leaves evidence your team can read afterward.
Limits
FAQ
BOD 26-04, issued 10 June 2026, has federal agencies remediate each vulnerability as quickly as possible and no later than the timelines in its Table 1. That Phase III duty applies within 180 days of issuance, by 7 December 2026. Mimic doesn't remediate anything. It stops unauthorized changes on the servers it protects at the point of execution while remediation runs.
Yes. BOD 26-04 says it supersedes and revokes BOD 19-02 and BOD 22-01, and CISA's directives list marks both revoked. Plans and pages that still cite BOD 22-01's deadlines are out of date, so check which timelines your program tracks. What Mimic does doesn't change with the directive: unauthorized changes on protected servers stop at the point of execution.
Mimic Networks runs alongside the EDR, vulnerability scanning and patch tooling an agency already runs. EDR asks whether activity matches an attack it recognizes; Mimic asks whether a change to a protected server was authorized, and stops unauthorized changes at the point of execution. Each blocked change lands in DashCam, and Mimic feeds enforcement events to your SIEM and SOAR platforms.
Mimic keeps supporting Windows Server 2016 after Microsoft's Extended Support ends on 12 January 2027. That matters for mission servers that can't migrate in time. When an exploit needs an unauthorized change on a protected server, Mimic stops it at the point of execution. The Windows Server 2016 guide covers the options server by server.
Related
Start with a demo. Bring the servers you need to protect and the questions your team will ask.