Oligo Raises $60 Million for Runtime Security

The cybersecurity landscape is witnessing a pivot from static code analysis toward more dynamic, real-time protection strategies. This shift was underscored recently by Oligo Security’s announcement of a $60 million Series B funding round. The investment, aimed at scaling the company’s runtime security platform, highlights a growing industry consensus: identifying vulnerabilities in source code is no longer sufficient if organizations cannot secure the software as it actually executes in production environments. By focusing on the "runtime" phase, Oligo intends to provide a final line of defense against the increasingly sophisticated exploits targeting modern software supply chains.

To understand the significance of this funding, one must look at the historical progression of Application Security (AppSec). For years, the industry relied on Software Composition Analysis (SCA) tools that scanned repositories for known vulnerabilities (CVEs) in open-source libraries. However, this approach led to "vulnerability fatigue," where security teams were overwhelmed by thousands of alerts, many of which represented code that was present in the library but never actually invoked by the application. This noise created a dangerous gap, allowing critical threats to hide in plain sight while developers chased harmless shadows. High-profile incidents like the Log4j crisis demonstrated that knowing a vulnerability exists is only half the battle; knowing if it is being actively exploited in a live environment is the true priority.

Oligo’s technical approach centers on the concept of application-level visibility. Unlike traditional perimeter defenses or static scanners, their platform monitors how an application interacts with its dependencies during execution. By establishing a baseline of "normal" behavior for third-party libraries, the system can detect when a library attempts to perform unauthorized actions, such as accessing sensitive files, opening unexpected network connections, or executing malicious commands. This granular control allows organizations to adopt a "zero-trust" posture at the library level, ensuring that even if a developer inadvertently includes a compromised package, the damage is contained by runtime constraints.

The business mechanics of this $60 million raise suggest a maturing market for runtime security. Investors are betting that the next generation of Chief Information Security Officers (CISOs) will prioritize "reachability" and "exploitability" over simple vulnerability counts. By narrowing the focus to only the code that is actually running, Oligo claims it can reduce the security alert backlog by up to 80%. For a global enterprise, this represents more than just a security upgrade; it is a significant operational efficiency play, freeing up engineering resources that were previously wasted on manual triage.

The implications for the broader cybersecurity market are profound. Oligo’s expansion puts pressure on established players like Snyk, Checkmarx, and Palo Alto Networks to bolster their own runtime capabilities. We are likely entering a phase of rapid consolidation where static analysis tools must integrate deeply with runtime protection to remain competitive. Furthermore, as regulatory frameworks like the U.S. Executive Order on Cybersecurity and the EU’s Cyber Resilience Act begin to demand more robust Software Bills of Materials (SBOMs), the ability to verify those components in real-time will become a compliance necessity rather than a luxury.

Looking ahead, the primary metric for success will be how effectively runtime security can combat "zero-day" threats—vulnerabilities that have not yet been cataloged or patched. As attackers increasingly target the development pipeline itself, the ability to observe and block anomalous behavior in the execution environment is the industry’s best hope for resilience. Watch for Oligo to use this capital to deepen its integration with cloud-native ecosystems like Kubernetes and serverless architectures. The ultimate goal is a seamless security layer that protects software from the moment it is compiled to the moment it is retired, turning the "black box" of third-party code into a transparent and controlled asset.