Open herrBez opened 2 years ago
Pinging @elastic/security-external-integrations (Team:Security-External Integrations)
@herrBez Are you able to obtain a sanitized copy of the complete documents that show this behaviour, preferably with event.original
if possible.
Hi @efd6, sorry for the late response. I hope that the message field is sufficient.
Thanks @herrBez. The pipeline looks like it is doing what is intended from the PANW documentation for the Threat log data there. The docs describe the relevant fields as "Sender (sender)" -> "Specifies the name of the sender of an email." and "Recipient (recipient)" -> "Specifies the name of the receiver of an email.", but these fields in the messages have the text "social-networking,low-risk" (which also appears in many other fields in ways that don't really make sense). Do we know where this field value is coming from?
Hi! We just realized that we haven't looked into this issue in a while. We're sorry! We're labeling this issue as Stale
to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1
. Thank you for your contribution!
According to the documentation the PANW integration (in particular, the Threat dataset) populates the (non-ECS?) fields
source.user.email
anddestination.user.email
, which should be two EMail addresses.The information added in these two fields are the "Sender" and "Recipient" of the Palo Alto's Threat Log Field Documentation, which are ambiguously documented as:
and
respectively.
A customer noted that the field is (sometimes?) filled with information that are not EMail Addresses. Some examples are reported in the following:
EXAMPLE 1
EXAMPLE 2
source.user.email
contains a valid URL