-
Notifications
You must be signed in to change notification settings - Fork 8
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
Endpoint.Ports includes extraneous events #9
Comments
Hi Skye, do you by any chance have an anonymized data sample you could share so I can look into this? |
I will create one. I will try to get a sample of each of the body.properties.ActionType values. |
//Identifies potential DNS tunnelling over HTTPS //Advanced Hunting query |
@SkyeLowry I'm doing some cleanup and want to get this fixed. Do you have the samples? |
The events from body.category="AdvancedHunting-DeviceNetworkEvents" includes all events, though body.properties.ActionType has values:
ConnectionSuccess
NetworkSignatureInspected
ListeningConnectionCreated
ConnectionFailed
InboundConnectionAccepted
ConnectionFound
ConnectionRequest
ConnectionAcknowledged
ConnectionAttempt
I am not certain which events should be included, though I do see "NetworkSignatureInspected" results in CIM events that don't seem to relate to the uses of the data model.
The problems this is creating shows up in this example:
The report [Endpoint - Listening Ports Tracker - Lookup Gen] from SA-EndpointProtection then adds those events to the listeningports_tracker lookup but those events are not listening ports, and result in entries with transport=null in the output.
Also, state=listening makes sense for an ActionType of ListeningConnectionCreated. I think when ActionType=ConnectionSuccess|InboundConnectionAccepted the state should be established. (I don't know what other field values are possible.
I think process_id could map to body.properties.InitiatingProcessId, process_guid could have a match, though I am not sure which value.
The text was updated successfully, but these errors were encountered: