oligo

Endor Labs & Oligo: Closing the Loop Between Secure Code and Secure Runtime

Endor Labs and Oligo keep pipelines fast and secure with unified reachability, real-time threat blocking, and safe, automatic fixes.

Written by

Published on
July 10, 2025

Updated on
August 25, 2025

1. Write Secure Code by Default with Endor Labs

Development starts in the IDE or in tools like Cursor. Endor Labs runs as an MCP server that feeds the assistant live vulnerability data. Unsafe patterns are flagged before the engineer even commits.

At build time the Endor Labs platform:

The result is a repo that already meets most security policy requirements before CI starts.

2. Tie Dev-Time and Run-Time Reachability Context with Both Endor Labs and Oligo

During CI the pipeline Oligo produces a detailed SBOM based on what’s actually running. Endor Labs ingests SBOM for package IDs, licenses and known CVEs, and blends those results with its own static reachability graph.

After deployment the signed container runs under Oligo’s runtime sensor. Oligo records every loaded class and executed function. When a vulnerable path executes, the sensor sends two facts to Endor Labs:

  1. The signature of the affected image.
  2. The exact path that was executed at runtime.

Endor maps this event back to the repository, branch and call-tree inside its static analysis. Engineers can now see one finding that shows both static and runtime evidence instead of two disjointed alerts.

3. Instantly Block Threats with Oligo and Accelerate Fixes with Endor Patches

Runtime Prevention:

Using Deep Application Inspection, Oligo can detect when a vulnerable function is being exploited in real time. When it does Oligo can block malicious function calls immediately - stopping the exploit, and without impacting the application shielding the service until a fix can be implemented.

Remediation:

Teams hit remediation SLAs while avoiding the regressions that often follow a full upgrade. Customers using this flow reduce remediation work by 70–80 % and close CVEs 6.2 × faster.

End-to-End Benefits

Need How the integration delivers
Secure code by default Endor MCP blocks risky code and guides safe choices before commit.
Unified reachability context Static call-graphs (Endor) + live execution data (Oligo) identify the small set of CVEs that matter.
Real-time threat blocking Oligo shields exploitable paths the moment they execute.
Fast, non-breaking fixes Endor Upgrade Impact Analysis or minimal Endor Patches remediate without large upgrades or rewrite work.

Wrapping Up…

Endor Labs secures what engineers create. Oligo secures what actually runs. Together they form one loop:

Security stays continuous, contextual and inside the developer workflow, without slowing the pipeline or filling Jira with noise.

What's next?

When you're ready to take the next step in securing your software supply chain, here are 3 ways Endor Labs can help:

Explore the Secure Code Prompt Library
Take a tour of Endor Labs
Book a Demo

Contents

1. Write Secure Code by Default with Endor Labs

2. Tie Dev-Time and Run-Time Reachability Context with Both Endor Labs and Oligo

3. Instantly Block Threats with Oligo and Accelerate Fixes with Endor Patches

End-to-End Benefits

Share This Resource