COMMUNIQUÉ DE PRESSE

Fig Partners With Elastic to Bring CI/CD, Version Control and One-Click Rollback to Detection Engineering

New York, United States, November 19th, 2026, FinanceWire


The language around the new partnership between Fig and Elastic comes from software delivery. Detection and response are things to build, ship and run, changes are tested before production, and validated work ships as code. Fig announced the integration partnership with Elastic on November 19, 2026, bringing that way of working to the detection rules organizations run in Elastic Security. SiliconANGLE was first to break the news.

Fig offers capabilities for mapping detection dependencies, identifying breaks and validating changes before they reach production. Elastic positions Elastic Security as an open, agentic security operations platform. Together, they give security teams visibility into how data changes affect security coverage, along with control over every change.

Complementary Roles for Fig and Elastic

The partnership is easiest to understand as a division of responsibilities. Elastic Security supplies prebuilt integrations and research-backed detection rules that provide broad coverage from day one. Elastic's Automatic Import feature and its artificial intelligence (AI) Agent help teams build new integrations and custom rules as their requirements grow. Fig's role is to help security operations (SecOps) engineers safeguard and expand that coverage as environments evolve, connecting upstream data changes to the downstream detections that depend on them.

Gal Shafir, co-founder and chief executive officer of Fig, captured the relationship in one sentence. "Elastic gives security teams control over their data, and Fig gives them control over the engineering around it," Shafir said. For Elastic customers, this means Fig works alongside capabilities they already use.

The Coverage Problem the Integration Addresses

The engineering Shafir mentions centers on dependencies. Detection rules need data to arrive in an expected structure, with the fields and values required to identify suspicious activity. That structure can change when vendors update log formats, when teams introduce new sources or when upstream pipelines reshape data for cost and performance. Such changes may be intentional and beneficial, and they often happen in tools owned by different teams.

When the data no longer carries what a rule needs, drift sets in. Data continues to flow and rules remain active, but they may lose the information needed to detect the attacks they were designed to catch. The partnership is meant to help Elastic users understand these dependencies, identify where a change has affected detection coverage and follow a clearer path from discovering an issue to addressing its cause. Fig does this by connecting to Elastic through a read-only application programming interface (API) key and retrieving the environment's configuration. Its deterministic Security Data Lineage then maps sources through pipelines, mappings and fields to the detection rules that use them.

Jamie Hynds, Director of Product at Elastic, explained why that tracing matters to Elastic's customers. "Environments never stop changing, from vendor schemas and APIs to ETL tools and pipelines. Fig traces those changes to the detection rules that depend on them, so SecOps teams can adapt quickly and maintain detection coverage with Elastic Security," Hynds said. In his remarks, ETL refers to extract, transform and load tools.

Bringing Software Delivery Discipline to Detection Changes

With the lineage in place, engineers can see what each rule relies on before a change goes live. When a source, pipeline or mapping changes, Fig identifies affected detections, pinpoints where the flow has broken and recommends a fix for engineers to investigate and assess. Fig also tests changes against the organization's own data and environment context before production.

The delivery step is where the parallels with software engineering are clearest. Engineers can ship changes as code using continuous integration and continuous delivery (CI/CD), with version control and one-click rollback. This connects a planned change to its expected effect on detection coverage, so teams can assess dependencies, test adjustments and manage deployment as they add sources, refine pipelines or expand use cases.

Shafir described the payoff in terms of pace. "Teams can see how every source connects to every detection, test each change against their own environment and ship it as code. That lets them move quickly without losing sight of their coverage," he said.

Migration as a Practical Use Case

The integration also has a role during platform transitions. For organizations moving from another security information and event management (SIEM) platform, Elastic's Automatic Migration translates existing detection rules. Fig then checks each translated rule against the data available in Elastic before cutover, flags rules that need rework and recommends fixes. This helps engineers see where translated detection logic and the destination environment's data need to be aligned before they switch over.



Contact
Editorial Team
editor@tvc.partners


Disclaimer. This is a paid press release.