- Notifications
You must be signed in to change notification settings - Fork 513
crowdstrike: fix handling of network direction #12508
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
101bf00 to d9ddf43 Compare 🚀 Benchmarks reportTo see the full report comment with |
| Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
kcreddy left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It would be nice to hear from user on #12476 (comment)
packages/crowdstrike/data_stream/fdr/elasticsearch/ingest_pipeline/outbound_network.yml Outdated Show resolved Hide resolved
packages/crowdstrike/data_stream/fdr/elasticsearch/ingest_pipeline/outbound_network.yml Outdated Show resolved Hide resolved
packages/crowdstrike/data_stream/fdr/elasticsearch/ingest_pipeline/default.yml Outdated Show resolved Hide resolved
| Waiting for @monkeyonbranch. Setting as draft to avoid accidental merge. |
9444961 to 77e1e98 Compare Assume that network direction that is no inbound can be validly semantically represented as outbound using the ECS fields available. This is probably not true; documented values of the ConnectionDirection are 0 - outbound, 1 - inbound, 2 - neither, and 3 - both[1]. Adhering strictly to inbound/outbound makes it impossible to map the data to ECS since neither and both would only be expressible as unknown. [1]https://docs.panther.com/data-onboarding/supported-logs/crowdstrike/falcon-data-replicator#crowdstrike.networkconnect
77e1e98 to 07ef3af Compare 💚 Build Succeeded
History
cc @efd6 |
|
| Sorry for the long wait. Sometimes life happens. |
| Thanks @monkeyonbranch. If there are any issues with the heuristic we are using, please file a new issue. |
Assume that network direction that is not inbound can be validly semantically represented as outbound using the ECS fields available. This is probably not true; documented values of the ConnectionDirection are 0 - outbound, 1 - inbound, 2 - neither, and 3 - both[1]. Adhering strictly to inbound/outbound makes it impossible to map the data to ECS since neither and both would only be expressible as unknown. [1]https://docs.panther.com/data-onboarding/supported-logs/crowdstrike/falcon-data-replicator#crowdstrike.networkconnect
Assume that network direction that is not inbound can be validly semantically represented as outbound using the ECS fields available. This is probably not true; documented values of the ConnectionDirection are 0 - outbound, 1 - inbound, 2 - neither, and 3 - both[1]. Adhering strictly to inbound/outbound makes it impossible to map the data to ECS since neither and both would only be expressible as unknown. [1]https://docs.panther.com/data-onboarding/supported-logs/crowdstrike/falcon-data-replicator#crowdstrike.networkconnect
| Package crowdstrike - 1.49.1 containing this change is available at https://epr.elastic.co/package/crowdstrike/1.49.1/ |




Proposed commit message
Assume that network direction that is no inbound can be validly semantically represented as outbound using the ECS fields available. This is probably not true; documented values of the ConnectionDirection are 0 - outbound, 1 - inbound, 2 - neither, and 3 - both[1].
Adhering strictly to inbound/outbound makes it impossible to map the data to ECS since neither and both would only be expressible as unknown.
[1]https://docs.panther.com/data-onboarding/supported-logs/crowdstrike/falcon-data-replicator#crowdstrike.networkconnect
Checklist
changelog.ymlfile.Author's Checklist
How to test this PR locally
Related issues
Screenshots