November 18, 2026

Fig + Elastic: Embrace open data, engineer it with confidence

Fig and Elastic are partnering so security teams can build, ship and run detection and response, with control over every change.

Fig

Blog
Fig and Elastic are partnering so security teams can build, ship and run detection and response, with control over every change.

Elastic Security gives security teams an open, agentic security operations platform, with prebuilt integrations and detection rules that cover them from day one. Fig helps SecOps engineers keep that coverage intact as data changes, and ship every new change with confidence. When something breaks, Fig shows exactly where and how to fix it.

Every detection depends on its data arriving as expected, and that data rarely sits still. Vendors update log formats, new sources come online, and upstream pipelines reshape data for cost and performance. Most of that reshaping is deliberate and useful, but it often happens upstream, in tools that are often owned by different teams. When data structures, fields or values change, the data keeps flowing and the rule keeps firing, but it silently stops catching the attack it was built for. All while the SOC still believes itโ€™s fully covered. This is Drift, and it happens to every security team, whatever platform they run on.

Fig gives SecOps engineers control over every detection flow, from source to rule. Through a read-only API key, it pulls your full Elastic configuration down to the inch, and deterministic Security Data Lineage maps every source through pipelines, mappings and fields to the detections that use it. Engineers build, ship and observe every change from that map. When a change breaks a detection, Fig pinpoints where in the flow it broke and recommends the fix.

Fig has always been stack-agnostic, and that includes stacks you build yourself. Elastic gives you control over your security data. Fig gives you control over the engineering needed to realize its full potential.

“Our partnership with Fig brings validation and transparency to security data lineage. By mapping how upstream data changes impact downstream coverage, Fig gives SecOps teams using Elastic the visibility and control they need to iterate quickly and adapt their environments with confidence.”ย  – Mandy Andress, Elastic, CISO

See your environment from source to detection

Fig maps your Elastic environment from each data source to every detection that uses it. You know what each rule relies on before a change goes out.

Find and fix what breaks, wherever it breaks

When a source, pipeline or mapping changes anywhere, Fig shows the affected detections and how to fix them. So teams see issues right away, and resolve them the same day.

Build and ship changes that fit your environment

Elasticโ€™s prebuilt integrations and research-backed detection rules give you broad coverage out of the box, and Elasticโ€™s Automatic Import and AI Agent help you build new integrations and custom rules as you grow. Fig works alongside them, testing changes against your full data and environment context before production, then shipping them as code, with true CI/CD, full version control and one-click rollback. 

Embrace Elastic Security with resilience, confidence and control

When you move to Elastic Security from another SIEM, Elasticโ€™s Automatic Migration translates your existing detection rules. Fig then checks each translated rule against the data in Elastic before cutover and flags any that need rework and recommends the right fix, so you can switch over when youโ€™re ready. If youโ€™re already on Elastic and adding sources or use cases, Fig runs the same checks before each change goes live.

Get started

The Fig + Elastic integration is available [date]. To see how Fig maps your Elastic environment, book a demo.

See Fig in action