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] Custom Event Channel support #317

Closed
jamiehynds opened this issue Oct 20, 2020 · 1 comment · Fixed by #794
Closed

[Windows] Custom Event Channel support #317

jamiehynds opened this issue Oct 20, 2020 · 1 comment · Fixed by #794
Assignees
Labels

Comments

@jamiehynds
Copy link

jamiehynds commented Oct 20, 2020

The Windows/System integrations currently support Application, System, Security, Sysmon and PowerShell events. To complete our winlogbeat migration, we need to ensure users can ingest events from channels outside of our supported channels. Example: Applications and Services Logs \Microsoft\Windows\Applocker\EXE and DLL.

Based on this design doc, our initial plan involved adding Custom Windows Events to the existing Windows integration, but given that multi-input is not currently a priority, this may not be feasible. This workaround may be an option: elastic/kibana#82783

If multi-input is a non-runner, the preference is to provide a Custom Windows Event integration whereby a user adds a single event channel per custom integration.

Acceptance Criteria

  • Users can ingest Windows Events from custom channels (Windows Integration vs Custom Windows Integration TBD)
  • Users can specify the ingest node pipeline to write to.
@masci
Copy link

masci commented Dec 1, 2020

@narph FYI

@masci masci added the Integration:windows Windows label Dec 24, 2020
@jamiehynds jamiehynds changed the title [Windows] Add option for additional event channels [Windows] Custom Event Channel support Mar 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants