Fig announced an integration partnership with Elastic on November 19, 2026, the company said in a press release. Fig helps security operations (SecOps) engineers map detection dependencies, identify breaks and validate changes before they reach production. The integration connects Fig with Elastic Security, which Elastic describes as an open, agentic security operations platform. It is designed to let security teams build, ship and run detection and response while seeing how changes to their data affect what they can detect.

First reported by SiliconANGLE, the partnership deals with a practical concern for organizations that rely on detection rules to flag suspicious activity. Those rules work only when the data feeding them arrives in the structure they expect, and that structure can shift over time. Fig and Elastic link upstream data changes to the downstream detections that rely on them, which gives engineers control over each change that touches security coverage.

What the Fig and Elastic Integration Does

Elastic Security gives customers a starting point through prebuilt integrations and detection rules that help establish coverage from day one. Fig picks up from there and helps SecOps engineers safeguard and expand that coverage as their environments evolve. Elastic Security supplies the platform and its prebuilt content, and Fig focuses on the dependencies that tie upstream data changes to the detections built on that data.

Gal Shafir, co-founder and chief executive officer of Fig, summed up how the two companies divide the work. "Elastic gives security teams control over their data, and Fig gives them control over the engineering around it," Shafir said.

Why Detection Coverage Can Erode Without Warning

Detection rules depend on specific fields and values to recognize an attack. A vendor may update its log format, a team may bring a new source online, or an upstream pipeline may be reshaped to manage cost and performance. In each case, the information a rule needs may stop arriving in the form it expects. These changes may be intentional and beneficial, but they often happen in tools owned by different teams.

The result is drift. Data keeps flowing and rules stay active, yet a rule can lose the information it needs to catch the attacks it was written to detect. The partnership is designed 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.

How Fig Maps an Elastic Environment

Fig connects to Elastic through a read-only application programming interface (API) key and retrieves the configuration of the Elastic environment. From that configuration, Fig's deterministic Security Data Lineage maps each source through pipelines, mappings and fields to the detection rules that use them.

With that map in place, engineers can see what each rule relies on before a change goes live. When a source, pipeline or mapping changes, Fig identifies the affected detections, pinpoints where the flow broke and recommends a fix. Engineers can then use that context to investigate the issue and assess the proposed repair.

Jamie Hynds, director of product at Elastic, explained the value from Elastic's side of the partnership. "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. ETL stands for extract, transform and load.

Testing Changes and Shipping Them as Code

Elastic's prebuilt integrations and research-backed detection rules provide broad coverage out of the box. Elastic's Automatic Import feature and its artificial intelligence (AI) Agent help teams build new integrations and custom rules as their requirements grow. Fig works alongside those capabilities by testing changes against the organization's own data and environment context before anything reaches production.

Once a change is validated, engineers can ship it as code using continuous integration and continuous delivery (CI/CD), with version control and one-click rollback. Taken together, these steps form an engineering workflow that ties each planned change to its expected effect on detection coverage. Teams can assess dependencies, test adjustments and manage deployment as they add sources, refine pipelines or expand use cases. Shafir presented that workflow as a way to keep pace without giving up visibility. "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.

Support for Organizations Moving to Elastic Security

The integration also covers platform migrations. 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 validation helps engineers see where translated detection logic and the destination environment's data need to be aligned before switching over. Existing Elastic users can apply the same checks when they introduce sources or change detection use cases.


This article was published under HackerNoon's Business Blogging program.