Oligo Raises $60M to Extend Runtime Security to AI Agents
Data Breach TodayArchived Aug 14, 2026✓ Full text saved
CEO: Funding Will Expand Exploit Blocking Across Cloud-Native and Agentic Apps Startup Oligo raised $60 million to expand runtime exploit blocking to agentic AI, tracing activity from prompts and tool calls to system calls as faster exploitation and growing enterprise agent deployments challenge traditional patch-first defenses.
Full text archived locally
✦ AI Summary· Claude Sonnet
Agentic AI
Oligo Raises $60M to Extend Runtime Security to AI Agents
CEO: Funding Will Expand Exploit Blocking Across Cloud-Native and Agentic Apps
Michael Novinson (MichaelNovinson) • August 13, 2026
Credit Eligible
Get Permission
Nadav Czerninski, co-founder and CEO, Oligo (Image: Oligo)
A startup led by a former Israeli Military Intelligence captain raised $60 million to extend runtime security to agentic applications as enterprises rapidly adopt artificial intelligence.
See Also: Why Traditional DLP Can't Keep Up With AI Data Growth
The funding - led by Ballistic Ventures, Canon Capital, Greenfield Partners, Lightspeed Venture Partners, Red Dot Capital and TLV Partners - will help Oligo identify exploitation as it occurs and block it before an attacker causes damage, said co-founder and CEO Nadav Czerninski. He said Oligo had developed the technology before agentic AI became a major enterprise security concern.
"We're building the leading runtime security platform to protect cloud-native and agentic applications, and we're actually the only solution that can block attacks without taking down the application in runtime," Czerninski told ISMG. "We do that using our technology that we call the deep app inspection, which basically allows us to see live code execution in real time in a non-intrusive way."
Oligo, founded in 2022, employs 129 people and has raised $140 million, having previously completed a $50 million Series B funding round in January 2025 led by Greenfield Partners. The company has been led since its inception by Czerninski, who previously spent more than six years leading the Israeli Military's cyber research team (see: Oligo Security Raises $50M to Tackle App Detection, Response).
How Securing Agentic Apps, Traditional Apps Differs
The traditional period between vulnerability disclosure and exploitation is disappearing, with attackers reverse-engineering a patch and exploiting the vulnerability before organizations have had a realistic opportunity to deploy the fix. Czerninski said these changes make security approaches built around lengthy detection, investigation and remediation cycles increasingly inadequate.
"We're seeing the exploit window being faster than ever," Czerninski said. "In the past, once there was a patch out, you had time to patch it. Now we're seeing a negative amount of days, meaning once the patch is out, attackers already leverage it. Organizations really have to have something to protect themselves."
Agentic applications introduce security considerations that conventional applications do not, he said, meaning security teams must understand prompts, models, tool calls, function calls and the actions those components ultimately initiate. The goal is to trace activity from the original prompt through the agent's decisions and tool calls down to the system calls occurring on the operating system, he said.
"We added the ability to see not just the action that happens on the operating system, but we see agentic applications and everything that happens in them from the prompt itself to those tool calls and function calls down to the actual system call detect on the operating system," Czerninski said. "The agentic applications require us to add another level of deep visibility to monitor from prompt to action."
Czerninski said Oligo's deep application inspection already observes the application call stack and the activity that ultimately produces system calls. The primary difference is what Oligo does with the information after collecting it. For agentic environments, he said the company has developed detections and analytical capabilities that identify models and tools and examine how they behave at runtime.
"The main difference is how we productize around that data," Czerninski said. "We collect the same data, very deep, the deepest data that anyone can get from runtime, and then based on that, the threat detections that we're adding and the different ways to extract the data to understand what models are being used, what tools are being used and then how they behave at runtime."
How Many AI Apps Are in Production Environments?
Deep runtime visibility can address vulnerability prioritization and attack prevention. For prioritization, firms can determine whether an application is actually executing the vulnerable function associated with a flaw rather than treating every detected vulnerability as equally urgent. For attack prevention, the platform can determine whether a particular library should be making a specific system call, he said.
"We can see what the actual functions that are being used are," Czerninski said. "And many times, 90% of the vulnerabilities aren't exploitable because they are not running the vulnerable function."
Oligo continues to see conventional cloud-native applications dominate production environments, but Czerninski said it's also seeing growing use of applications built around LLMs and agents capable of making tool calls. Czerninski said all of Oligo's customers have already adopted AI in some capacity, and the number of agents running in enterprise environments continues to increase.
"We're seeing more and more the use of AI applications with the standard LLMs, but also identical applications with tool calls," Czerninski said. "And many times we're seeing our customers surprised with how many applications that they have, how many agents they have running in their environment without them knowing."
Czerninski said Oligo intends to use the funding to broaden the coverage and deployment options for its exploit-blocking capabilities. One use case is persistent protection against unknown vulnerabilities in software libraries that repeatedly produce security flaws. Another is virtual patching when a new CVE is disclosed. Oligo can issue a dedicated protection designed to block exploitation of that vulnerability.
"Relying just on hygiene and relying on post-exploit detection of that is just not relevant anymore," Czerninski said. "In today's world, you have to start with actually blocking the exploit, and only then patching and doing the routine hygiene that is always important."