Add fields for detection of shadow AI authentication file events - #792
Open
fearful-symmetry wants to merge 3 commits into
Open
Add fields for detection of shadow AI authentication file events#792fearful-symmetry wants to merge 3 commits into
fearful-symmetry wants to merge 3 commits into
Conversation
pzl
reviewed
Aug 21, 2026
Member
There was a problem hiding this comment.
If you pull in the latest main, does this change go away?
I attempted to fix this issue in #779
Contributor
Author
There was a problem hiding this comment.
Ah, that did work!
pzl
approved these changes
Aug 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Change Summary
This adds two fields,
file.ai_agent.emailandfile.ai_agent.api_key_authto file events for detection of authentication flows (claude auth, etc) from endpoint. This also adds file modification events for platforms that don't already have them, as we'll need to report modification events for the given authentication stores.Sample values
Sample document:
Release Target
9.6.0
For mapping changes:
makeafter making the schema changes, and committed all changesmetadatachange, I also updated both transform destination schemas to match