You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add a related.url field to facilitate searching for URLs that appear in various other fields of an event.
Motivation:
This was requested by a user in order to improve mappings for data sources that have multiple URL fields, such as data from the o365 integration.
The closest existing field is related.hosts, which is for "All hostnames or other host identifiers seen on your event. Example identifiers include FQDNs, domain names, workstation names, or aliases."
The addition of related.domain was suggested as an alternative to related.url. I have focused here on related.url as it is more distinct from the related.hosts use case.
Detailed Design:
A related.url field could be populated with the same kind of values as url.full when possible, or the same kind as url.original if that is the most complete value available.
Setting a field type of wildcard would match the url.full and url.original fields. A .text multi-field could be added.
Examples from o365 integration - not the most compelling, but this is what was readily available in test data
Summary
Add a
related.url
field to facilitate searching for URLs that appear in various other fields of an event.Motivation:
This was requested by a user in order to improve mappings for data sources that have multiple URL fields, such as data from the o365 integration.
The closest existing field is
related.hosts
, which is for "All hostnames or other host identifiers seen on your event. Example identifiers include FQDNs, domain names, workstation names, or aliases."The addition of
related.domain
was suggested as an alternative torelated.url
. I have focused here onrelated.url
as it is more distinct from therelated.hosts
use case.Detailed Design:
A
related.url
field could be populated with the same kind of values asurl.full
when possible, or the same kind asurl.original
if that is the most complete value available.Setting a field type of
wildcard
would match theurl.full
andurl.original
fields. A.text
multi-field could be added.Examples from o365 integration - not the most compelling, but this is what was readily available in test data
The text was updated successfully, but these errors were encountered: