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] Update Sysmon module for v12/13 #21172

Closed
andrewkroh opened this issue Sep 18, 2020 · 8 comments
Closed

[Winlogbeat] Update Sysmon module for v12/13 #21172

andrewkroh opened this issue Sep 18, 2020 · 8 comments

Comments

@andrewkroh
Copy link
Member

Sysmon v12 added event ID 24 which is a ClipboardChanged event. The Winlogbeat Sysmon module should be updated to handle this event ID.

When the clipboard changes the contents are archived to file and an event is generated with information about the activity. The event includes a hash that can be used to access the archived file.

@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Sep 18, 2020
@elasticmachine
Copy link
Collaborator

Pinging @elastic/siem (Team:SIEM)

@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Sep 18, 2020
@willemdh
Copy link

@andrewkroh In the meantime Sysmon13 has been released.

This update to Sysmon adds a process image tampering event that reports when the mapped image of a process doesn’t match the on-disk image file, or the image file is locked for exclusive access. These indicators are triggered by process hollowing and process herpaderping. This release also includes several bug fixes, including fixes for minor memory leaks.

@MikePaquette
Copy link

@jamiehynds Is this on your radar?

@jamiehynds jamiehynds changed the title [Winlogbeat] Update Sysmon module for v12 [Winlogbeat] Update Sysmon module for v12/13 Jan 20, 2021
@jamiehynds
Copy link

@MikePaquette absolutely - I've added it to our planning board.

@andrewkroh what do we need to proceed we adding support for new events added in Sysmon v12/13? I assume some sample events in XML?

@andrewkroh
Copy link
Member Author

#18094 can be used as a guide for this update. Basically add support for the two new event IDs and then diff the schema to look for changes to the existing IDs. For any event IDs that are new or changed, export sample events to an .evtx file to create tests for.

Then lastly, sync the changes to the package in elastic/integrations.

@botelastic botelastic bot added needs_team Indicates that the issue/PR needs a Team:* label and removed needs_team Indicates that the issue/PR needs a Team:* label labels Feb 15, 2021
@botelastic
Copy link

botelastic bot commented Feb 15, 2021

This issue doesn't have a Team:<team> label.

@elasticmachine
Copy link
Collaborator

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

@jamiehynds
Copy link

Closing this issue in favor of: #24217

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

No branches or pull requests

5 participants