added get_actor_user method to data model #1343
Merged
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.
Background
A customer was receiving alerts from the out-of-the-box (OOTB) detection
GCP IAM serviceAccounts getAccessToken Privilege Escalation
. The alert message included[GCP]: [<ACTOR_NOT_FOUND>] performed [GenerateAccessToken] on project
, which indicated that Panther's data model did not recognize the actor correctly.Upon investigation, we found that the issue arose because the GCP Audit schema in Panther was only mapping the
principalEmail
field as theactor_user
, while for third-party identity callers, GCP populates theprincipalSubject
field instead ofprincipalEmail
. This behavior is confirmed by the GCP documentation.Changes
get_actor_user
to useprincipalSubject
foractor_user
field whenprincipalEmail
is not presentget_actor_user
method to 'username' field since it was also mapping toprincipalEmail
previouslyGCP IAM serviceAccounts getAccessToken Privilege Escalation
to use theactor_user
udm fieldTesting
make lint
,make test
Principal Subject Used