-
Notifications
You must be signed in to change notification settings - Fork 467
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
Microsoft 365 Integration audit data #8935
Comments
@tandemkid can you confirm which version of the integration you're running? We just release v2.0 last week with improved mappings for the o365.audit.data fields. @chrisberkhout could you confirm if the recent update covers the sample event above, to parse the email address, subject, etc? |
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
The version was 1.29.2. We just upgraded to 2.10. We will see if there is
any change.
Let's cyber together,
tevin manuel
Chief Security Advisor & Founder
316.247.0560
Wichita, KS
[image: Tandem] <https://www.tandemcyber.co/>
tandemcyber.co <https://www.tandemcyber.co/>
…On Mon, Jan 22, 2024 at 04:30 jamiehynds ***@***.***> wrote:
@tandemkid <https://github.com/tandemkid> can you confirm which version
of the integration you're running? We just release v2.0 last week with
improved mappings for the o365.audit.data fields.
@chrisberkhout <https://github.com/chrisberkhout> could you confirm if
the recent update covers the sample event above, to parse the email
address, subject, etc?
—
Reply to this email directly, view it on GitHub
<#8935 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A4RKUXZT23RBPILT4QQMPGLYPZLVNAVCNFSM6AAAAABCCU6OJGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBTHEYDMNBVHA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@tandemkid @jamiehynds Yes, the recent updates cover this. The known subfields of For more detail on these changes please refer to: |
Thank you for the clarification and for updating the integration to support
this additional data.
…On Mon, Jan 22, 2024 at 8:19 AM Chris Berkhout ***@***.***> wrote:
@tandemkid <https://github.com/tandemkid> @jamiehynds
<https://github.com/jamiehynds> Yes, the recent updates cover this.
The known subfields of Data that we identified are indexed as their
corresponding types in o365.audit.Data.* (this includes all fields in the
example above). The full data object is also available in
o365.audit.Data.flattened. The email address in Data.tsd will be copied
into related.user.
For more detail on these changes please refer to:
- #8571 <#8571>
- #8803 <#8803>
—
Reply to this email directly, view it on GitHub
<#8935 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A4RKUX2JM3GFAMZA66ZSEUTYP2GRDAVCNFSM6AAAAABCCU6OJGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBUGM2DQMJUGQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
I don't know what the functionality is supposed to be for the o365.auidt.Data field; however, the o365 module isn't parsing "o365.audit.data" into separate fields. If this is by design, we request that this information be parsed into separate fields so that rules can highlight the desired fields and that alerts can be created more efficiently.
In this case, we would want the reported email and subject to have their own fields, just like the other data.
Vivek Zaveri [email protected]","sip":"40.107.236.100","srt":"1","trc":"redacted.edu","ms":"[External]RE: Bruce? ",
The text was updated successfully, but these errors were encountered: