Ensure Consistency Across Ingested Data for Analyzer Development #12562
Labels
enhancement
New feature or request
Integration:crowdstrike
CrowdStrike
Integration:m365_defender
Microsoft M365 Defender
Integration:microsoft_defender_endpoint
Microsoft Defender for Endpoint
Integration:panw_cortex_xdr
Palo Alto Cortex XDR
Integration:sentinel_one
SentinelOne
Integration:trend_micro_vision_one
Trend Micro Vision One
Team:Security-Service Integrations
Security Service Integrations team [elastic/security-service-integrations]
Team:Sit-Crest
Crest developers on the Security Integrations team [elastic/sit-crest-contractors]
Uh oh!
There was an error while loading. Please reload this page.
Ensure Consistency Across Ingested Data for Analyzer Development
Description
To support the development of the analyzer, we need consistency in the ingested data across CrowdStrike, SentinelOne, and Microsoft Defender for Endpoint. Specifically, the following fields should be consistently available and mapped to ECS.
Requirements
Ensure all three integrations provide the following fields:
process.entity_id
process.parent.entity_id
process.name
event.module
event.kind
Impact
Next Steps
The text was updated successfully, but these errors were encountered: