-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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 Event Log integration module for Elastic Agent #20886
Comments
Pinging @elastic/ingest-management (Team:Ingest Management) |
@dancs85 Is under our radar, we want to do some refactor of Winlogbeat/filebeat to add to the elastic agent. But having better windows support is one of our priority. |
Pinging @elastic/integrations-services (Team:Services) |
Wait, I've misread the ask, the elastic-agent does support the winlog input, we need to have an official integration. |
The windows package already makes use of the winlog input in Agent. For Sysmon and others we should consider separate integrations. But on the Beats/Agent side itself I think we are done. |
Describe the enhancement:
The Elastic Agent should have a module that replicates the functionality of Winlogbeat, including the Powershell, Security and Sysmon modules. If possible, Sysmon itself should be able to be bundled in (if licencing allows) as this will populate a lot of the information the SIEM app uses.
Describe a specific use case for the enhancement or feature:
The Windows event logs are used in both Observability and Security arenas.
Bundling sysmon will cover users who don't opt to use the Elastic Endpoint module (I believe Sysmon/Elastic Endpoint generate very similar logs)
The text was updated successfully, but these errors were encountered: