Listen to this Post
A New Chapter for Runtime Security
Cybersecurity is entering an uncomfortable new era. Attackers are becoming faster, software environments are becoming more complicated, and artificial intelligence is increasingly capable of helping adversaries discover weaknesses and develop attacks at machine speed. In that environment, simply finding vulnerabilities is no longer enough. Security teams need to know what is actually running, what is genuinely exploitable, and what can be stopped right now.
That changing reality is helping drive a major investment in runtime security company Oligo Security. On August 4, 2026, Oligo announced a new $60 million funding round, bringing its total capital raised to $140 million. The company says the new investment will support product innovation and global expansion across application security, cloud workloads, and AI systems.
SiliconANGLE
+1
The announcement is significant because Oligo is betting on a fundamental shift in cybersecurity: moving protection closer to the moment an application is actually executing. Instead of relying entirely on scanners and patching processes that happen before or after deployment, runtime security attempts to observe what happens inside production environments and intervene when malicious behavior appears.
The $60 Million Funding Round
Oligo’s latest financing adds another $60 million to the company’s funding history, taking its cumulative funding to approximately $140 million. Investors participating in the round include Ballistic Ventures, Canon Capital, Greenfield Partners, Lightspeed Venture Partners, Red Dot Capital and TLV Partners, along with angel investors including Eyal Waldman, co-founder of Mellanox Technologies.
ctech
+1
The new capital arrives after a period of strong growth for the company. According to reporting around the announcement, Oligo said its annual recurring revenue increased by 300% year over year, while its valuation more than doubled from its previous Series B round.
ctech
That growth suggests investors are seeing runtime security as more than another niche within the crowded cybersecurity market. The underlying thesis is that traditional vulnerability management is struggling to keep pace with modern software development.
Why Runtime Security Matters Now
Modern applications rarely consist of code written entirely by one organization. They depend on open-source libraries, third-party packages, cloud services, containers, APIs, frameworks and increasingly AI components.
That creates an enormous vulnerability-management problem.
A scanner may identify thousands of vulnerabilities across an environment, but not every vulnerable component is necessarily being executed. Security teams can therefore end up spending valuable time investigating theoretical risks while more meaningful threats compete for attention.
Oligo’s approach is to examine application behavior during execution and determine which vulnerable functions are actually being used. Its platform uses an eBPF-based sensor to observe library functions called by workloads in production.
SiliconANGLE
The distinction is important: a vulnerability that exists is not always the same thing as a vulnerability that is actively exploitable in a specific environment.
From Vulnerability Lists to Runtime Truth
Traditional security programs often begin with a list of CVEs. Organizations discover a vulnerability, determine which systems contain the affected software, assess severity and then begin the patching process.
That model remains necessary, but it has a major weakness: there can be a significant delay between discovery and remediation.
Attackers do not necessarily wait for defenders to complete that process.
Oligo’s strategy is based on adding another layer of visibility. Rather than asking only whether vulnerable software exists, runtime security can ask whether vulnerable code is actually executing and whether an attacker is attempting to manipulate it.
That changes the question from “Do we have this vulnerability?” to “Can an attacker exploit this vulnerability here and now?”
Virtual Patching Buys Defenders Time
One of the most interesting aspects of
There are situations where a security team cannot immediately deploy an official software fix. A patch may require extensive testing, a maintenance window, application changes or coordination across multiple teams.
During that period, the vulnerability can remain exposed.
Oligo’s runtime protection is designed to provide an additional defensive layer during that gap. Its Runtime Exploit Blocking technology focuses on malicious attack techniques rather than depending exclusively on individual CVE signatures. The company says this allows a single rule to address multiple vulnerabilities that share similar exploitation behavior.
oligo.security
This could become particularly valuable when defenders are dealing with zero-days or rapidly changing exploit techniques.
The Zero-Day Problem Is Getting Harder
Zero-days have always represented one of the most frightening scenarios for security teams because organizations can be attacked before a traditional patch exists.
The situation becomes even more complicated when attackers can automate parts of vulnerability research and exploit development.
AI does not automatically make every attacker highly capable, but it can reduce the time required for certain tasks. Code analysis, reconnaissance, vulnerability triage and exploit development can potentially be accelerated by increasingly capable models.
That creates an uncomfortable race.
If attackers can move from vulnerability discovery to exploitation faster than organizations can move from discovery to patch deployment, defenders need another mechanism for reducing that time advantage.
Runtime protection is one possible answer.
Oligo Is Expanding Into AI Security
Oligo’s strategy is not limited to traditional applications and cloud infrastructure. The company is also positioning its platform around AI systems.
That expansion reflects another emerging reality: AI infrastructure is becoming software infrastructure, and software infrastructure inherits many of the same security problems.
AI inference servers, model-serving platforms, Python environments, APIs, containerized workloads and third-party dependencies can all introduce attack surfaces.
Oligo has previously published research into vulnerabilities affecting AI inference infrastructure, including issues involving widely used AI projects and frameworks. Its research has highlighted how insecure code patterns can spread when projects reuse or copy components from one another.
oligo.security
AI Is Creating a Different Security Race
The cybersecurity industry spent years building tools around the idea that defenders needed to identify vulnerabilities faster.
AI changes that equation.
The question increasingly becomes whether attackers can discover and weaponize weaknesses faster than defenders can respond.
This is why runtime security could become strategically important. It does not necessarily attempt to win the speed contest by discovering every vulnerability first. Instead, it attempts to create a defensive control that remains active while applications are running.
That is a fundamentally different philosophy.
The Importance of Protecting Production Without Breaking It
Security tools sometimes create a difficult operational trade-off: aggressive protection can interfere with legitimate applications.
In production environments, shutting down a process to stop a suspected attack may itself create an outage.
Oligo’s Runtime Exploit Blocking technology is designed around the idea of blocking malicious behavior inside the application while keeping the underlying workload running. The company says its approach can stop exploit techniques without killing containers or processes.
oligo.security
+1
If that promise works consistently at enterprise scale, it could make runtime controls particularly attractive to organizations where availability is just as important as security.
The Funding Is Also a Market Signal
The $60 million investment is not simply a financial event for Oligo.
It is also a signal about where cybersecurity investors believe the market is heading.
Security teams are drowning in alerts, vulnerabilities and fragmented tools. Organizations increasingly need platforms that can prioritize what matters instead of simply generating more findings.
Runtime security fits that demand because it attempts to connect vulnerability intelligence with actual application behavior.
The broader industry is moving toward the idea that context is as important as severity.
A critical vulnerability that is never executed may deserve a different response from a lower-rated vulnerability that is actively being targeted inside a production application.
Oligo’s Earlier Strategy
Oligo was launched publicly in 2023 with $28 million in funding, backed by investors including Ballistic Ventures, Lightspeed Venture Partners and TLV Partners. The company described its mission as shifting application security toward runtime protection.
oligo.security
That original strategy has now evolved into a broader security platform covering applications, cloud environments and AI systems.
The expansion illustrates how the cybersecurity market itself is changing. What began as application security is increasingly connected to cloud security, supply-chain security, AI security and runtime defense.
These categories may eventually become less separate than they appear today.
Runtime Security Could Reduce Vulnerability Fatigue
Security teams have a limited number of people and an almost unlimited number of vulnerabilities to investigate.
Every major software ecosystem can generate new security findings. Open-source dependencies create additional complexity, while cloud environments can change continuously.
The result is vulnerability fatigue.
Organizations may know that thousands of vulnerabilities exist while lacking the resources to investigate every one with equal depth.
Runtime visibility offers a different prioritization model.
Instead of treating every vulnerability as equally urgent, security teams can focus more heavily on vulnerabilities connected to code that actually executes and behavior that indicates genuine exposure.
The Supply Chain Connection
Software supply-chain attacks have become one of the clearest examples of why traditional perimeter security is insufficient.
A legitimate package can become dangerous after a maintainer account is compromised. A trusted dependency can receive malicious code. A build pipeline can be manipulated without an obvious intrusion into the organization’s network.
Oligo’s own research into malicious npm packages has highlighted how attackers can compromise maintainer credentials and distribute malicious code through trusted software channels.
oligo.security
Runtime controls do not eliminate supply-chain risk, but they can provide an additional opportunity to detect suspicious behavior after malicious code reaches an environment.
Why Investors May Be Betting on This Model
Cybersecurity spending tends to follow painful operational problems.
Companies already spend enormous amounts of money on vulnerability scanners, endpoint protection, cloud security platforms and application security tools.
The challenge is that more tools do not necessarily mean better security.
A platform that can reduce the amount of noise while actively protecting production applications could potentially deliver value beyond simply generating another security dashboard.
That is likely one reason runtime security is attracting increasing attention.
Oligo’s AI Security Opportunity
AI infrastructure could become one of the
Organizations are deploying models into production, connecting them to databases, APIs and internal systems, and giving AI agents increasingly powerful capabilities.
That creates a new security boundary.
An AI system is not simply a model. It is often a collection of software, libraries, infrastructure, credentials, tools and external services.
If attackers compromise one part of that chain, the consequences can extend far beyond the model itself.
Runtime security could therefore become an important component of AI infrastructure defense.
The AWS and Government Angle
Oligo’s expansion also extends into major enterprise and government ecosystems.
The company says AWS selected it as the exclusive AI runtime security partner for AWS Security Hub Extended. Oligo has also joined Palantir’s FedStart Program as part of its effort toward FedRAMP High and DoD Impact Level 5 authorization.
Globes
Those relationships matter because government and highly regulated customers often require security controls that can operate reliably inside complex environments.
If Oligo successfully expands into those markets, the new funding could help turn runtime security from a specialized product into a broader enterprise security layer.
What Undercode Say:
Runtime Security Is Moving From Optional to Strategic
The biggest lesson from this funding round is not the $60 million figure itself. The more important story is the security philosophy behind it.
For years, vulnerability management has been dominated by scanning, scoring and patching.
That model is becoming harder to sustain.
Attackers Do Not Care About Vulnerability Backlogs
A company may have thousands of open vulnerabilities, but an attacker only needs one useful path.
This creates an asymmetry between defenders and attackers.
Defenders must understand an enormous environment. Attackers can search for the smallest opening that provides leverage.
Runtime monitoring attempts to narrow that gap by focusing on what actually happens during execution.
AI Makes Response Speed More Important
The rise of AI-assisted cyber operations could compress the time between discovery and exploitation.
That means organizations cannot depend entirely on lengthy remediation cycles.
Security controls that operate continuously inside production environments could become increasingly valuable.
Runtime Could Become the New Security Control Point
Firewalls protect networks.
Endpoint tools protect devices.
Cloud platforms protect infrastructure.
Application security tools protect software development.
Runtime security sits closer to the actual execution of code.
That position could become increasingly important as applications become distributed across cloud, containers, APIs and AI workloads.
Virtual Patching Is Not a Replacement for Real Patching
There is also an important limitation.
Virtual patching should not become an excuse to ignore permanent remediation.
Organizations still need to update vulnerable software, remove obsolete dependencies and fix insecure code.
Runtime controls should ideally provide a defensive bridge rather than become a permanent substitute for software maintenance.
The Biggest Challenge Will Be Accuracy
Runtime security sounds powerful, but its value depends heavily on precision.
If a system blocks legitimate behavior, production teams may disable the protection.
If it misses sophisticated attacks, customers may lose confidence.
The technology therefore has to balance security, visibility and operational stability.
That is much harder than simply identifying a CVE.
AI Security Could Expand the Market Dramatically
The AI security market is still developing.
As organizations move from AI experiments to production agents and autonomous workflows, the number of execution environments that need protection will increase.
That could create a major opportunity for companies capable of protecting AI applications at runtime.
The Investment Reflects a Larger Shift
The funding round suggests investors believe cybersecurity is moving toward active defense.
Passive visibility is no longer enough.
Organizations increasingly want technology that can identify suspicious behavior and take action before a vulnerability becomes a breach.
The Real Product Is Time
Perhaps the most valuable thing runtime security provides is not another vulnerability report.
It provides time.
Time between vulnerability disclosure and patching.
Time between attacker activity and detection.
Time between exploit development and remediation.
In cybersecurity, those seconds, minutes and days can determine whether an incident becomes a blocked event or a full-scale breach.
Deep Analysis: Why
Command 1 — Watch What Actually Executes
Security teams should prioritize vulnerabilities connected to code that is genuinely running in production.
Command 2 — Reduce Theoretical Risk
Not every scanner finding represents an immediately exploitable threat.
Runtime context can help distinguish theoretical exposure from active risk.
Command 3 — Protect The Patch Gap
Organizations should deploy runtime controls as a defensive layer while official patches are being tested and deployed.
Command 4 — Treat AI Infrastructure as Production Infrastructure
AI servers, model frameworks, APIs and agent environments need the same security discipline as conventional applications.
Command 5 — Prepare for Faster Exploitation
Security programs should assume that attackers will increasingly automate vulnerability research and operational tasks.
Command 6 — Protect Without Creating Outages
Runtime defense must be capable of stopping malicious activity without unnecessarily disrupting legitimate workloads.
Command 7 — Connect Vulnerability Intelligence With Behavior
A vulnerability’s severity is only part of the story. Execution context, accessibility and attacker behavior matter too.
Command 8 — Do Not Abandon Patching
Virtual patching buys time, but permanent remediation remains essential.
Command 9 — Measure Security by Outcomes
Organizations should evaluate whether a security platform reduces real exposure rather than simply increasing the number of alerts.
Command 10 — Expect Runtime Security to Expand
As cloud-native applications and AI systems become more complex, runtime visibility could become a standard component of enterprise defense.
✅ $60 Million Funding Round
Confirmed: Oligo Security announced a new $60 million financing round on August 4, 2026, bringing its reported total funding to $140 million.
ctech
+1
✅ Runtime Security Focus
Confirmed:
SiliconANGLE
+1
⚠️ AI-Powered Attacks
Partly confirmed: The broader claim that AI is accelerating offensive cybersecurity capabilities is a developing industry trend, but specific claims about attackers universally operating at “machine speed” should be treated as an assessment rather than a universally measurable fact.
Prediction
(+1) Runtime Security Will Become a Major Enterprise Security Layer
The most likely direction is continued growth in runtime security as organizations struggle with enormous vulnerability volumes, increasingly dynamic cloud environments and AI-powered applications.
(+1) AI Runtime Protection Will Become More Important
As AI agents gain access to tools, data and production systems, organizations will need security controls capable of monitoring what those systems actually execute.
(+1) Virtual Patching Will Gain Adoption
Companies will increasingly use virtual patching as a temporary defensive measure when traditional remediation cannot happen quickly enough.
(-1) Runtime Security Will Not Eliminate Vulnerability Management
Organizations will still need scanners, secure development practices, patching and software supply-chain controls. Runtime protection is more likely to become another critical layer than a complete replacement.
(+1) Investor Interest Will Continue
If
(+1) The Security Battle Will Move Closer to Code Execution
The deeper trend is clear: cybersecurity is moving from simply asking what vulnerabilities exist toward asking what is executing, what is being attacked, and what can be stopped immediately.
That shift could make runtime security one of the defining cybersecurity categories of the AI era.
▶️ Related Video (78% Match):
🕵️📝Let’s dive deep and fact‑check.
🎓 Live Courses & Certifications:
Join Undercode Academy for Verified Certifications
🚀 Request a Custom Project:
Secure, high-velocity infrastructure and disruptive technological engineering. Contact our engineering team for high-tier development and proprietary systems:
[email protected]
💎 Smart Architecture | 🛡️ Secure by Design | ⭐ Trusted by Thousands
References:
Reported By: x.com
Extra Source Hub (Possible Sources for article):
https://www.stackexchange.com
Wikipedia
OpenAi & Undercode AI
Image Source:
Unsplash
Undercode AI DI v2
🔐JOIN OUR CYBER WORLD [ CVE News • HackMonitor • UndercodeNews ]
📢 Follow UndercodeNews & Stay Tuned:
𝕏 formerly Twitter 🐦 | @ Threads | 🔗 Linkedin | 🦋BlueSky | 🐘Mastodon | 📺Youtube
