-
Notifications
You must be signed in to change notification settings - Fork 442
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
[o365] Add extra values to related.user
#8803
[o365] Add extra values to related.user
#8803
Conversation
related.url
related.user
🚀 Benchmarks reportTo see the full report comment with |
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
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.
LGTM after version bump change.
packages/o365/data_stream/audit/elasticsearch/ingest_pipeline/default.yml
Show resolved
Hide resolved
Co-authored-by: Dan Kortschak <90160302+efd6@users.noreply.github.com>
Co-authored-by: Dan Kortschak <90160302+efd6@users.noreply.github.com>
💚 Build Succeeded
History
|
Package o365 - 2.1.0 containing this change is available at https://epr.elastic.co/search?package=o365 |
Proposed commit message
Discussion
These changes were suggested by a user in #4319.
Available example data includes
o365.audit.Parameters.User
values such asAvailable example data shows the
o365.audit.Data.*
fieldsf3u
,suid
,tsd
andtrc
as having values that match the format of an email address. Theuser.email
anduser.id
fields could potentially be populated with these values, but given the undocumented and uncertain meaning of the fields, I have chosen to add values that appear to be email addresses torelated.user
to aid discovery, and I will leave any further interpretation of these values to integration users.Checklist
changelog.yml
file.Author's Checklist
How to test this PR locally
Related issues