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

[Winlogbeat] Event ID reuse in the Security channel causes wrong enrichment #27288

Closed
andrewkroh opened this issue Aug 9, 2021 · 2 comments · Fixed by #29781
Closed

[Winlogbeat] Event ID reuse in the Security channel causes wrong enrichment #27288

andrewkroh opened this issue Aug 9, 2021 · 2 comments · Fixed by #29781
Assignees

Comments

@andrewkroh
Copy link
Member

The Active Directory Federation Service (AD FS) can publish events to the Windows Security log. Some of the event IDs that it uses overlap with event IDs used by other publishers to the Security channel. This causes a problem with the Security module for Winlogbeat because it assumes the content of an event based on its event ID.

In most systems there are two publishers to the Security channel - Microsoft-Windows-Eventlog and Microsoft-Windows-Security-Auditing, and their event IDs do not collide. Because their can be collisions the Security module should also check the winlog.provider_name field because making assumptions about the winlog.event_id value.

As an example event ID 1102 from Microsoft-Windows-Eventlog collides with 1102 from the AD FS log. So when the module processes 1102 from AD FS it gets marked event.action: audit-log-cleared.

@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Aug 9, 2021
@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Aug 9, 2021
@elasticmachine
Copy link
Collaborator

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

@willemdh
Copy link

Noticed this for some time, thanks for creating the issue @andrewkroh

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants