-
Notifications
You must be signed in to change notification settings - Fork 522
[Jamf Protect 3.2.0] Enhancements to process mapping #15046
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
Conversation
|
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
|
/test |
🚀 Benchmarks reportTo see the full report comment with |
Co-authored-by: Krishna Chaitanya Reddy Burri <krish.reddy91@gmail.com>
Co-authored-by: Krishna Chaitanya Reddy Burri <krish.reddy91@gmail.com>
|
@kcreddy Thanks for the review - i've implemented the minor changes and those are ready to be reviewed. |
|
/test |
kcreddy
left a comment
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
|
@kcreddy i saw in SQ that the readme file was out of date - fixed that. |
|
/test |
💚 Build Succeeded
History
|
|
|
Package jamf_protect - 3.2.0 containing this change is available at https://epr.elastic.co/package/jamf_protect/3.2.0/ |
The Jamf Protect Telemetry data stream got enhancements in it's process audit tokens. - The audit token now contains a effective username (e_username) - The audit token now contains a executable path for the process (exec_path)




Type of change:
Proposed commit message
Check Jamf's release notes here
Checklist
changelog.ymlfile.How to test this PR locally
elastic-package test system