-
Notifications
You must be signed in to change notification settings - Fork 519
Sonicwall Global Category fixes, and add rule UUID #15853
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
Conversation
|
💚 CLA has been signed |
|
I have completed the Contributor Agreement. |
|
Pinging @elastic/integration-experience (Team:Integration-Experience) |
qcorporation
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You will also need to update the manifest.yml file with the new version 1.19.3
|
Is there anything else I need to do for this to be reviewed and merged in? |
Were these values ever correct? I looked back at Sonic OS 6.x and I can't find any mentions of the old gcat mappings. 6.5.4 is the first version I see mentioning gcat categories and they are the same that you've listed in the PR. I'm fine with correcting invalid mappings, but if they actually changed between 6.x and 7.x, then that would constitute a breaking change in the integration. |
I just looked back at them myself, and you are correct, the first them that gcat mappings are mentioned is in the 6.5.4 Log Events Ref Guide which was published in June of 2021. I do not think these were ever mapped correctly in the integration. |
taylor-swanson
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall, changes seem fine to me (aside from the changelog).
The pipeline test expected files will need to be updated, which can be done by running:
cd packages/sonicwall_firewall
elastic-package test pipeline --generate
If you don't have an environment set up, I can certainly run that command and update the test files, just let me know.
@taylor-swanson I do not have an environment setup, would you mind doing that for me please? Thank you |
|
/test |
🚀 Benchmarks reportTo see the full report comment with |
💚 Build Succeeded
|
|
Package sonicwall_firewall - 1.21.0 containing this change is available at https://epr.elastic.co/package/sonicwall_firewall/1.21.0/ |
se label this PR with one of the following labels, depending on the scope of your change:
Proposed commit message
Bug Fixes
This PR corrects the gcat (Global Category) mapping for Sonicwall messages, as they changed from version 6.x of SonicOS to 7.x. This documented on page 105. This also corrects a incorrect event action for log event [#]36 should be listed as
packet-dropped, which is documented on page 12.Enhancement
Added is a new ecs field called
rule.uuidthat adds the rule UUID when it appears in the log. This makes it alittle eaiser to identify rule hits, as the rule name (mapped torule.id) can sometimes cover many rules, if they have the same name.Checklist
changelog.ymlfile.Author's Checklist
How to test this PR locally
Install the SonicWall integration, and configure to receive logs. After make the following changes to the
logs-sonicwall-logingest pipline.rule.idmapping, add in the mapping forrule.uuidmessage-codesupdate 36 fromconnection-closetopacket-dropped.Related issues
N/A
Screenshots
N/A