Fig 與 Elastic 合作,協助安全團隊防止偵測覆蓋出現隱性缺口
Fig and Elastic partner to help security teams prevent silent gaps in detection coverage
Fig 與 Elastic 合作推出整合方案,協助安全團隊在環境變更時維持偵測覆蓋。Fig 透過 Security Data Lineage 梳理資料來源、管道、欄位與偵測規則之間的依賴,識別受影響的偵測並建議修正方案。整合現已推出,團隊可在部署前驗證變更。
Security teams rely on detection rules to identify suspicious activity across increasingly complex technology environments. But even when those rules remain active, changes to the underlying data can quietly undermine their effectiveness. A vendor updating its log format, a new data source entering the environment or a pipeline modification can leave detection logic without the information it needs to identify threats.
Addressing this challenge, Fig has announced an integration partnership with Elastic designed to help security teams maintain detection coverage as their environments evolve. The integration combines Elastic Security’s open, agentic security operations platform with Fig’s capabilities for mapping detection dependencies, identifying breaks and validating changes before they reach production.
The partnership aims to give security operations teams greater visibility into the relationship between their data infrastructure and the detection rules that depend on it.
The problem with detection rules that stop working
Detection engineering involves more than creating rules that identify suspicious behavior. Those rules depend on data arriving in specific structures, containing particular fields and values that allow security teams to recognize potentially malicious activity.
When those dependencies change, detection coverage can deteriorate without producing an obvious warning. Data may continue flowing, and detection rules may remain enabled, even though the information required to identify an attack is no longer available.
These changes are not necessarily caused by mistakes. Organizations regularly modify their data pipelines to improve performance, introduce new vendors or accommodate evolving infrastructure requirements. However, changes made outside security teams’ direct control can have downstream consequences for detection engineering.
This is where Fig’s integration with Elastic is designed to help. Rather than treating data infrastructure and detection rules as separate components, the integration connects changes upstream to the detections that depend on them.
Mapping the dependencies behind security coverage
Fig connects to an Elastic environment through a read-only API key and retrieves its configuration. Its deterministic Security Data Lineage then maps the relationships between data sources, pipelines, mappings, fields and detection rules.
This creates a dependency map that allows engineers to understand what each detection rule requires before making changes to the environment. When a source, pipeline or mapping changes, Fig identifies the affected detections and pinpoints where the data flow has broken.
The platform also recommends fixes, giving engineers information they can use to investigate the underlying issue and evaluate potential repairs.
For Gal Shafir, Co-Founder and CEO of Fig, the partnership addresses two complementary areas of security engineering.
“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.”
The distinction is important as organizations introduce new data sources and continuously adjust the infrastructure supporting their security operations.
Bringing validation into the deployment process
Elastic provides prebuilt integrations and research-backed detection rules to help organizations establish security coverage from the beginning. Its Automatic Import and AI Agent capabilities also help teams develop new integrations and custom rules as their requirements expand.
Fig complements these capabilities by allowing engineers to test changes against their organization’s actual data and environment context before deploying them.
Once changes have been validated, teams can ship them as code through continuous integration and continuous delivery workflows. Version control and one-click rollback provide additional control over deployment.
Jamie Hynds, Director of Product at Elastic, highlighted the importance of maintaining visibility as security environments change.
“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 more reliable security operations
The integration also addresses organizations migrating from another security information and event management platform. Elastic’s Automatic Migration translates existing detection rules, while Fig checks those translated rules against the data available in Elastic before cutover.
The process identifies rules that require rework and recommends fixes, helping engineering teams align detection logic with the destination environment before completing the transition.
The Fig and Elastic integration is now available. Security teams can book a demonstration through fig.security to see how Fig maps their Elastic environment.
As security environments continue to evolve, maintaining effective detection coverage requires more than keeping rules active. It also requires understanding the data dependencies behind them and validating changes before they affect production.
來源:TNW · thenextweb.com