Security operations platforms have become increasingly sophisticated, offering organizations integrations, detection rules and automation capabilities to identify threats across their environments. Yet building an effective security operations program involves another challenge: ensuring that the infrastructure supporting those capabilities remains reliable as organizations make changes.
Fig and Elastic are addressing this through a new integration partnership that connects security data infrastructure with detection engineering. As first reported by SiliconANGLE, the collaboration brings together Elastic Security’s open, agentic security operations platform and Fig’s capabilities for mapping data dependencies, identifying broken detection relationships and validating changes before production deployment.
The goal is to help security teams build, ship and run detection and response workflows while maintaining control over how changes affect security coverage.
Connecting Data Infrastructure With Detection Engineering
Detection rules are only as reliable as the data they receive. A rule designed to identify suspicious activity may depend on specific fields, values and structures within incoming logs. When those elements change, the rule can lose its effectiveness even if it remains enabled.
This creates a challenge for security operations teams because the infrastructure behind detection rules is rarely static. Vendors update schemas and APIs, organizations introduce additional data sources, and engineering teams modify ETL tools and pipelines to meet changing operational requirements.
These adjustments can create silent gaps in detection coverage. The data continues to arrive, but the information required by individual rules may no longer be present.
Fig’s integration is designed to make these relationships visible within Elastic environments. Through a read-only API key, Fig retrieves configuration information and builds a map of how data sources connect through pipelines, mappings and fields to the detection rules that use them.
Its deterministic Security Data Lineage provides engineers with a view of these dependencies, helping them understand the potential consequences of infrastructure changes.
From Identifying Breaks to Recommending Fixes
The integration goes beyond documenting data relationships. When a source, pipeline or mapping changes, Fig identifies which detection rules are affected and pinpoints where the data flow has broken.
Engineers can then investigate the issue with a clearer understanding of the dependencies involved. Fig also recommends fixes, allowing teams to assess potential repairs in the context of their existing environment.
Gal Shafir, Co-Founder and CEO of Fig, described the complementary roles of the two platforms.
“Elastic gives security teams control over their data, and Fig gives them control over the engineering around it,” said Shafir. “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.”
This approach connects the technical work of maintaining data pipelines with the operational requirement of preserving detection coverage.
A More Controlled Way to Deploy Changes
Elastic Security already provides prebuilt integrations and research-backed detection rules that help organizations establish coverage from day one. As environments grow, its Automatic Import and AI Agent capabilities help teams build additional integrations and custom rules.
Fig adds a validation layer to this process by testing changes against the organization’s data and environment context before they reach production.
Once engineers have assessed and validated their changes, they can deploy them as code through continuous integration and continuous delivery. Version control and one-click rollback give teams additional mechanisms for managing changes and responding when adjustments need to be reversed.
Together, the capabilities establish a workflow in which engineers can understand dependencies, evaluate proposed changes and manage deployments with greater visibility into their effects on detection coverage.
Jamie Hynds, Director of Product at Elastic, emphasized that maintaining this visibility is increasingly important as organizations modify their security data infrastructure.
“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,” said Hynds.
Making Security Platform Migration More Predictable
The partnership also supports organizations transitioning from another security information and event management platform to Elastic Security.
Elastic’s Automatic Migration translates existing detection rules into the destination platform. However, translated rules still need to be checked against the data available in the new environment.
Fig performs this validation before cutover, identifying rules that require rework and recommending fixes. This helps engineering teams determine where translated detection logic needs to be adjusted to match the available data.
The same validation capabilities can also support existing Elastic users introducing new sources or expanding their detection use cases.
Now Available to Elastic Users
The Fig and Elastic integration is now available. Security teams can book a demonstration at fig.security to see how Fig maps their Elastic environment.
By connecting data lineage, detection dependencies and deployment validation, the partnership gives security engineers a more structured way to manage the changes that influence detection coverage.
