Skip to content
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

[system] Improve user mappings in security #1944

Merged
merged 1 commit into from
Oct 19, 2021

Conversation

marc-gr
Copy link
Contributor

@marc-gr marc-gr commented Oct 19, 2021

What does this PR do?

Ports changes from elastic/beats#26509 to improve user mappings for security events.

Checklist

  • I have reviewed tips for building integrations and this pull request is aligned with them.
  • I have verified that all data streams collect metrics or logs.
  • I have added an entry to my package's changelog.yml file.
  • If I'm introducing a new feature, I have modified the Kibana version constraint in my package's manifest.yml file to point to the latest Elastic stack release (e.g. ^7.13.0).

@elasticmachine
Copy link

Pinging @elastic/security-external-integrations (Team:Security-External Integrations)

@elasticmachine
Copy link

elasticmachine commented Oct 19, 2021

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Start Time: 2021-10-19T12:01:35.767+0000

  • Duration: 30 min 6 sec

  • Commit: e7f9f30

Test stats 🧪

Test Results
Failed 0
Passed 267
Skipped 0
Total 267

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

Copy link
Member

@P1llus P1llus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Small comments, else it looks LGTM

Comment on lines +2578 to +2581
if (ctx?.event?.code == null ||
!["4648", "4688"].contains(ctx.event.code)) {
return;
}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we maybe move this out of the script itself? That way it never has to actually execute if its part of the processor conditions.

Comment on lines +2869 to +2872
- set:
field: user.target.name
copy_from: winlog.event_data.OldTargetUserName
ignore_empty_value: true
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Isn't this already set to another value higher up?

@marc-gr marc-gr merged commit bedab6d into elastic:master Oct 19, 2021
@marc-gr marc-gr deleted the security-enhancements branch October 19, 2021 12:37
eyalkraft pushed a commit to build-security/integrations that referenced this pull request Mar 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request Integration:system System
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants