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

securityonion-elsa-extras: update sysmon parser #782

Closed
dougburks opened this Issue Jul 19, 2015 · 6 comments

Comments

Projects
None yet
2 participants
@defensivedepth

This comment has been minimized.

Show comment
Hide comment
@defensivedepth

defensivedepth Jul 21, 2015

Sysmon 3.1 was released yesterday, and this parser may require another edit to be compatible with both 3.0 & 3.1, so please hold on this for now.

defensivedepth commented Jul 21, 2015

Sysmon 3.1 was released yesterday, and this parser may require another edit to be compatible with both 3.0 & 3.1, so please hold on this for now.

@dougburks

This comment has been minimized.

Show comment
Hide comment
@dougburks

dougburks Jul 21, 2015

Contributor

Will do, thanks!

Contributor

dougburks commented Jul 21, 2015

Will do, thanks!

@defensivedepth

This comment has been minimized.

Show comment
Hide comment
@defensivedepth

defensivedepth Jul 23, 2015

I have confirmed that this parser is compatible with both 3.0 & 3.1. It can be released.

Thanks,

defensivedepth commented Jul 23, 2015

I have confirmed that this parser is compatible with both 3.0 & 3.1. It can be released.

Thanks,

@defensivedepth

This comment has been minimized.

Show comment
Hide comment
@defensivedepth

defensivedepth commented Aug 9, 2015

New PR, sorry for the confusion:

Security-Onion-Solutions/securityonion-elsa-extras#8

@dougburks

This comment has been minimized.

Show comment
Hide comment
Contributor

dougburks commented Aug 22, 2015

@dougburks

This comment has been minimized.

Show comment
Hide comment

@dougburks dougburks closed this Sep 12, 2015

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