Protect validated servers you can't patch on demand.

Each change Mimic Networks blocks on a protected server lands in DashCam: what it tried to change, when and the process behind it. That record sits underneath your application's own audit trail; it doesn't replace it. Your quality team can use it to see what was attempted against a validated server between releases and what Mimic stopped,.

FDA's final Computer Software Assurance guidance, issued 3 February 2026, works through examples. In one, the manufacturer assesses the changes and the effect they may have on the intended use before the change goes in. That step is why a patch to a validated system queues. The queue is the window Mimic covers on the servers it protects.

Your quality team decides that, not Mimic. Before a Virtual Patching safeguard goes live, Mimic replays it against the host's recorded behavior to show what it would block. FDA's questions and answers on electronic systems in clinical investigations say changes, security patches included, should be assessed and validated through the system's life cycle depending on risk. The replay result gives your team evidence for that call.

Mimic protects the servers behind the lab, the production floor and the clinic. In the lab, that's LIMS and chromatography data system servers. On the production side, it's MES and batch record servers. Quality management system and clinical data servers sit across both. Each runs on Windows Server or Red Hat Enterprise Linux. Instruments, workstations and laptops stay out of scope.