entityanalytics_ad: Add mail and userPrincipalName fields#17758
Merged
maxcold merged 4 commits intoelastic:mainfrom Mar 16, 2026
Merged
entityanalytics_ad: Add mail and userPrincipalName fields#17758maxcold merged 4 commits intoelastic:mainfrom
maxcold merged 4 commits intoelastic:mainfrom
Conversation
Add two LDAP attributes to support entity resolution matching: - `mail` → mapped to `user.email` (ECS) for email-based matching - `userPrincipalName` → stored as `entityanalytics_ad.user.user_principal_name` for UPN-based name matching Both fields are added to `related.user` for cross-source correlation. No Beats/Agent changes needed — attributes already fetched by default.
Contributor
✅ Vale Linting ResultsNo issues found on modified lines! The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale. |
💚 Build Succeeded
|
andrewkroh
added
documentation
|
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
|
Package entityanalytics_ad - 0.18.0 containing this change is available at https://epr.elastic.co/package/entityanalytics_ad/0.18.0/ |
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
4 participants
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.
Proposed commit message
entityanalytics_ad: Add mail and userPrincipalName fields
Add two LDAP attributes to the Active Directory Entity Analytics integration to support entity resolution matching across identity providers (AD, Okta, Entra ID):
mail→ mapped touser.email(ECS) — enables email-based entity matchinguserPrincipalName→ stored asentityanalytics_ad.user.user_principal_name— enables UPN-based name matching via source event queriesBoth fields are added to
related.userfor cross-source correlation. No Beats/Agent changes needed — the AD input already fetches all LDAP attributes by default.Checklist
changelog.ymlfile.Author's Checklist
elastic-package test pipeline)elastic-package buildsucceedsHow to test this PR locally
cd packages/entityanalytics_adelastic-package buildelastic-package test pipelineuser.emailis populated frommailattributeuser_principal_nameappears in outputrelated.userincludes both valuesRelated issues
mailattribute to entityanalytics_ad integration kibana#256317 (Addmail)userPrincipalNameattribute to entityanalytics_ad integration kibana#256331 (AdduserPrincipalName)