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

[FEATURE] SYSMON - Add Sysmon version number to all (or more) events #820

Open
Vilv3 opened this issue Aug 9, 2024 · 4 comments
Open

[FEATURE] SYSMON - Add Sysmon version number to all (or more) events #820

Vilv3 opened this issue Aug 9, 2024 · 4 comments

Comments

@Vilv3
Copy link

Vilv3 commented Aug 9, 2024

Hi,

In an environment where many endpoints are being monitored via Sysmon, it's currently quite difficult to keep track of version numbers, since the only event where current version numbers are reported is the "Sysmon state change" event which is usually generated after an upgrade or fresh install.

Would it be possible to add a version number to all events created by Sysmon? Or at least more than the one that exists currently. This would mean that one could only check the latest event and see which version is in use on said endpoint.

Thanks!

@foxmsft
Copy link
Collaborator

foxmsft commented Aug 9, 2024

Interesting suggestion. Would adding an extra field to each event be suitable?

@Vilv3
Copy link
Author

Vilv3 commented Aug 9, 2024

Hey,

I think so. Not quite sure I understand your question correctly, but as long as the current version number could be parsed out of a raw log (some event created by Sysmon), then this would solve the "issue". :)

Thanks.

@NWiBGRsK
Copy link

Actually the "Version" of the executable and the "SchemaVersion" are present in "Event ID 4: Sysmon service state changed". Therefore you should be able to get a current value with every reboot (checked with version 14.16 and 15.15).

@Vilv3
Copy link
Author

Vilv3 commented Nov 12, 2024

@NWiBGRsK Hi, yes, and therein lies the issue, only being able to see the running version on a state change event. Particularly on servers that don't get rebooted often this is unideal from a monitoring/upkeep perspective, although not a major problem.

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

No branches or pull requests

3 participants