In focus  /
01 Trusted code gets through02 Unapproved execution stops03 Legacy servers get breathing room01 Trusted code gets through02 Unapproved execution stops03 Legacy servers get breathing room
Company profile / Cybersecurity

Virsec and the strange power of saying no

A security company built its case on a simple question: what is this software supposed to do? Its answer is a runtime gate for the code businesses cannot afford to stop.

Advertisement

The interesting thing about a server is how little it needs to improvise. A payroll system does not wake up one morning and develop a taste for mysterious scripts. A water utility's control software does not suddenly need an unfamiliar executable. Yet the security industry has spent years looking for signs of trouble after software begins to behave badly. Virsec, a company in San Jose, asks an earlier question: what should this workload be allowed to do in the first place?

The short version
  • Virsec's VSP maps trusted files, processes, scripts, and libraries, then enforces that map as applications run.
  • Its target is critical server software, including legacy systems whose owners cannot safely patch on command.
  • The company announced a $100 million Series C in 2021; its sales model is enterprise demos and partnerships.
  • The tradeoff is operational: a good allowlist requires a good understanding of legitimate change.

That question became a product. The Virsec Security Platform, or VSP, verifies components of a workload and watches execution against a trusted baseline. The company calls the model “default-deny, allow-on-trust.” If an attacker coerces a legitimate application into launching an unapproved process, loading unexpected code, or running an odd script, Virsec aims to stop that action at runtime. It is the difference between recognizing a burglar by face and knowing the museum is closed.

The trouble with a useful old machine

Consider the least photogenic computer in an enterprise: a server that runs an indispensable, elderly application. Perhaps a manufacturer relies on it for operations. Perhaps a hospital has built a workflow around it. It may have a vulnerable operating system, a vendor whose support has ended, or a maintenance window that takes weeks to negotiate. “Just patch it” sounds excellent until the patch breaks the service everyone came to work to use.

Virsec's answer is a compensating control. It does not claim to rewrite the old program. It tries to stop an exploit from turning a weakness into unauthorized execution, buying the owner time to test and deploy a durable fix. That distinction matters. A blocked exploit can shrink an urgent exposure; it does not make old software young again. The value is the interval between discovering a flaw and safely repairing it.

The mechanism explains Virsec's place in a crowded market. A web application firewall stands at the web edge. Endpoint detection and response tools observe and investigate activity across machines. Vulnerability scanners find known weaknesses. Virsec wants control at the moment code executes inside the workload. Its older materials call the mapping layer Virsec Map and the enforcement layer Virsec Enforce; earlier branding included the Deterministic Protection Platform and AppMap. The language has wandered. The central wager has remained unusually fixed.

“What if we could stop attacks in milliseconds?”Virsec's own description of its ambition

The word “deterministic” is doing heavy lifting there. Virsec presents its control as a rule about trusted behavior, rather than a probability that a pattern looks malicious. That is an appealing answer to alert fatigue. It also places a burden on whoever defines trust. Applications change. New dependencies arrive. A legitimate administrator may do something rare. Buyers should ask how a baseline is learned, reviewed, and updated, and how a new release is handled before enforcement becomes a production surprise.

From an engineer's hunch to a sales machine

Co-founder and CTO Satya Gupta brought a background in embedded systems and network security to the problem. Ray DeMeo co-founded the company; Atiq Raza, a former AMD executive, led it as CEO before becoming executive chairman. Dave Furneaux, an early investor, took the chief executive role in 2020. He described a company with a product launched in late 2018 that now needed a stronger route to customers. A clever security idea had to become something a procurement team could buy and an operations team could live with.

Portrait of Virsec co-founder and CTO Satya Gupta
Satya Gupta, Virsec's co-founder and CTO. Security rules are easy to write on a whiteboard; keeping them useful on a live server is the harder art. Photo: Infosecurity Magazine.

The company found one route through partners. A Raytheon Intelligence & Space relationship put Virsec's memory attack defense in front of government agencies and large enterprises, markets where a small vendor's own sales team might spend a long time learning the doorway. The Red Hat ecosystem catalog lists a Virsec offering integrated with Ansible Automation Platform. Public case-study directories also name Broadcom, a water and wastewater equipment supplier, and a government customer. Virsec's own site says Fortune 100 enterprises, healthcare organizations, and agencies use its technology. Those are claims of reach, not a published customer count.

$100mSeries C announced in 2021
70+Investors and advisers cited in that round
120+Worldwide patents claimed on current company page

The 2021 financing was striking even by the standards of a busy cyber market. BlueIO led a $100 million Series C with a roster that included John Chambers, Mike Ruettgers, Allen & Company, Artiman Ventures, and others. Virsec said the round brought its total funding to $137 million at the time. The plan was to hire, develop the product, and expand support. It was a bet that the bottleneck in enterprise security was not simply finding more problems. It was giving companies a way to stop an attack before the problem became a crisis.

Reported funding / selected rounds
2015
~$7m
2018
~$24-27m
2021
$100m

The product name changes; the question stays

Virsec's current website leads with VSP and speaks directly to operators of cloud and legacy server workloads. In 2025 it introduced OTTOGUARD.AI, an AI-branded product pitched as autonomous, patchless exposure mitigation. A recent company LinkedIn post says OTTOGUARD.AI is moving toward a separate startup. No terms were given there. The sequence says something about a market that keeps changing its nouns: application security, workload protection, exposure management, autonomous defense. Virsec has kept returning to the same verb: enforce.

What does the customer buy? Enterprise software and a deployment process, not a magic patch. Public pricing is absent; prospective buyers are asked to book a demo. A serious pilot would start with a critical workload, catalog its normal components, run in observation mode, then test how enforcement handles planned releases and an attempted unauthorized action. The useful measurement is not a glossy count of threats “seen.” It is whether the control blocks the action while the service continues to do its job.

There is a lesson here beyond Virsec. The most efficient security policy may be the one narrow enough to know what belongs. That is easier on stable, well-understood workloads than on software that changes every hour. For the owner of an old, essential server, though, stability is exactly the point. The machine's refusal to improvise becomes an asset. Virsec has built its business around teaching it to say no.