Solutions/
Public sector

Mimic Networks for the public sector

Protect federal servers between disclosure and remediation.

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.

October 27, 2026

The servers

The servers agencies can't afford to lose.

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.

  • Mission application servers. The systems the agency's mission runs on.
  • Public-facing application servers. Where a service meets the internet and a disclosed flaw draws traffic first.
  • Database servers. The records behind both.
  • Active Directory. The domain controllers every other server trusts.
  • Windows Server 2016 servers. Mimic keeps supporting Windows Server 2016 after Microsoft's Extended Support ends on 12 January 2027.

Workstations, laptops, mobile devices and network devices stay out of scope.

A Mimic node on each server you choose, including Windows Server 2016 after 12 January 2027.Federal mission, public-facing, database, Active Directory and Windows Server 2016 servers, each with a Mimic node enforcing its own known-good profile. Workstations, laptops and network devices stay out of scope. PROTECTED SERVERS, WINDOWS SERVER OR RHEL APPLICATION Mission applications MIMIC NODE APPLICATION Public-facing applications MIMIC NODE DATA Database servers MIMIC NODE IDENTITY Active Directory MIMIC NODE APPLICATION Windows Server 2016 MIMIC NODE WORKSTATIONS AND NETWORK DEVICES: OUT OF SCOPE
A Mimic node on each server you choose, including Windows Server 2016 after 12 January 2027.Federal mission, public-facing, database, Active Directory and Windows Server 2016 servers, each with a Mimic node enforcing its own known-good profile. Workstations, laptops and network devices stay out of scope. PROTECTED SERVERS, WINDOWS SERVER OR RHEL APPLICATION Mission applications MIMIC NODE APPLICATION Public-facing applications MIMIC NODE DATA Database servers MIMIC NODE IDENTITY Active Directory MIMIC NODE APPLICATION Windows Server 2016 MIMIC NODE WORKSTATIONS AND NETWORK DEVICES: OUT OF SCOPE
A Mimic node on each server you choose, including Windows Server 2016 after 12 January 2027.

The rules

The rules you answer to.

CISA BOD 26-04, scope

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

Where agency teams start.

Who we help

Who we help.

CISOs

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.

The window before a patch

Risk owners

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.

Windows Server 2016 after 12 January 2027

Proof

How you'll see it work.

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

Where Mimic stops.

  • Mimic Networks protects Windows Server 2016 and later, and Red Hat Enterprise Linux 8 and later.
  • It doesn't run on laptops, desktops or network devices.
  • In Maintenance Mode, Mimic suspends enforcement and keeps monitoring.
  • Mimic doesn't remediate vulnerabilities or report to CISA. Remediation, BOD 26-04 reporting and your system security plan stay with your team.

FAQ

Frequently asked questions.

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.

BOD 26-04 sets the remediation clock. Enforcement covers the servers while the fix moves.Between a vulnerability's disclosure and the deployed fix, BOD 26-04 sets the remediation timelines while the fix is tested and approved. Mimic stops unauthorized changes on protected servers across that whole span. Vulnerability disclosed Remediation clock starts Fix tested and approved Fix deployed WAITING ON THE FIX UNAUTHORIZED CHANGES STOP ON PROTECTED SERVERS BOD 26-04 Phase III applies by 7 December 2026.
BOD 26-04 sets the remediation clock. Enforcement covers the servers while the fix moves.Between a vulnerability's disclosure and the deployed fix, BOD 26-04 sets the remediation timelines while the fix is tested and approved. Mimic stops unauthorized changes on protected servers across that whole span. Vulnerability disclosed Remediation clock starts Fix tested and approved Fix deployed WAITING ON THE FIX UNAUTHORIZED CHANGES STOP ON PROTECTED SERVERS BOD 26-04 Phase III applies by 7 December 2026.
BOD 26-04 sets the remediation clock. Enforcement covers the servers while the fix moves.

See it on your servers.

Start with a demo. Bring the servers you need to protect and the questions your team will ask.

Book a demo