COMMUNIQUÉ DE PRESSE

Fig and Elastic Partner to Address the Engineering Challenges Behind Modern Security Operations

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


Security teams are under pressure to expand detection coverage while managing increasingly complicated data environments. New sources, changing vendor schemas and evolving pipelines can introduce problems that are difficult to identify through conventional monitoring. Even when detection rules remain enabled, changes to the information feeding them can quietly reduce their effectiveness.

Fig is partnering with Elastic to address this engineering challenge, bringing its detection dependency mapping and validation capabilities to Elastic Security's open, agentic security operations platform. The integration, as first reported by SiliconANGLE, is designed to help security teams understand how changes to their data environments affect detection coverage and manage those changes before they reach production.

The collaboration reflects a practical concern for security operations teams: maintaining detection coverage requires ongoing engineering work, not simply deploying rules and assuming they will continue functioning as intended.

The Complexity Behind Maintaining Detection Coverage

Detection rules operate according to specific data requirements. They need particular fields, values and structures to identify suspicious activity. If those requirements are no longer met, a rule may stop detecting the behavior it was designed to catch.

The problem is that the underlying data infrastructure is constantly changing. A vendor might update its logging format, an organization might introduce another data source, or an engineering team might restructure a pipeline to improve cost and performance.

These changes can happen across different teams and systems, making it difficult for security engineers to understand their downstream consequences. Data can continue flowing normally while detection rules lose access to critical information.

This is the type of silent degradation that Fig's integration with Elastic aims to address.

Following the Data Behind Every Detection

Fig connects to an Elastic environment using a read-only API key and retrieves its configuration. It then uses its deterministic Security Data Lineage to map the relationships between sources, pipelines, mappings, fields and detection rules.

For security engineers, this provides a way to understand the dependencies behind their detection coverage rather than examining individual rules in isolation.

When a source, pipeline or mapping changes, Fig identifies the affected detections and pinpoints where the data flow has broken. It also recommends fixes, giving engineers a starting point for investigating and resolving the issue.

Gal Shafir, Co-Founder and CEO of Fig, sees the integration as a way to give security teams more control over the engineering processes surrounding their data.

“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.”

Extending the Elastic Security Workflow

Elastic Security provides prebuilt integrations and research-backed detection rules that help organizations establish broad coverage from the outset. As their environments and requirements develop, Elastic's Automatic Import and AI Agent help teams build additional integrations and custom rules.

Fig complements these capabilities by introducing environment-specific validation before changes reach production. Engineers can test adjustments against their organization's data and configuration, allowing them to assess their potential effects before deployment.

The integration also supports continuous integration and continuous delivery workflows. Validated changes can be shipped as code, with version control and one-click rollback providing additional control over the deployment process.

Jamie Hynds, Director of Product at Elastic, emphasized the importance of maintaining visibility across constantly changing environments.

“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.

Supporting Organizations Moving to Elastic

The partnership also has a role in security platform migrations. Organizations moving from another security information and event management platform can use Elastic's Automatic Migration to translate existing detection rules.

Fig then checks those translated rules against the data available in Elastic before cutover. If a rule requires additional work, the platform flags it and recommends fixes so engineers can align detection logic with the destination environment.

The same validation process can be applied by existing Elastic customers when adding data sources or expanding detection use cases.

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.

Ultimately, the partnership addresses a part of security operations that can be overlooked: the engineering dependencies that determine whether detection rules remain effective after deployment.



Contact
Editorial Team
editor@tvc.partners


Disclaimer. This is a paid press release.