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

Windows Security Event Solution based Analytics should use ASim #11553

Open
PCNZ opened this issue Dec 11, 2024 · 0 comments
Open

Windows Security Event Solution based Analytics should use ASim #11553

PCNZ opened this issue Dec 11, 2024 · 0 comments
Assignees
Labels

Comments

@PCNZ
Copy link
Contributor

PCNZ commented Dec 11, 2024

Is your feature request related to a problem? Please describe.
When logs are collected by WEC (i.e. forwarded via a Windows Server) the security logs land in the WindowsEvent table instead of the SecurityEvent table.
This means the OOB analytics do not work and ignore these logs.

Describe the solution you'd like
Update the analytics included with the Windows Security Events solution to use ASIM, as per Microsoft's own recommendations here.
https://techcommunity.microsoft.com/blog/fasttrackforazureblog/windows-events-how-to-collect-them-in-sentinel-and-which-way-is-preferred-to-det/3997342

Describe alternatives you've considered
Modifying the analytics directly in each Sentinel instance is wasted effort, these OOB analytics should already be using ASIM.

Additional context
For example ASimAuthenticationMicrosoftWindowsEvent should be used for the analytic "SecurityEvent - Multiple authentication failures followed by a success"

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

No branches or pull requests

5 participants