We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
There escaping doesn't seem consistent with [the CEF standard].(https://kc.mcafee.com/resources/sites/MCAFEE/content/live/CORP_KNOWLEDGEBASE/78000/KB78712/en_US/CEF_White_Paper_20100722.pdf)
For example, there's no | character escaping in the prefix fields. There's also no '=' escaping in the extension fields. The following:
|
CEF:0|security|threatmanager|1.0|100|detected a = in message|10|src=10.0.0.1 act=blocked a \\= dst=1.1.1.1
produces the fields:
"fields": { "src": "10.0.0.1", "act": "blocked a", "\\": "", "dst": "1.1.1.1" },
When it should, I think, produce:
"fields": { "src": "10.0.0.1", "act": "blocked a \\", "dst": "1.1.1.1" },
The text was updated successfully, but these errors were encountered:
Fixed issue solzimer#9 with CEF escaping
7d607b8
Hi @hanvyj sorry for being soooo late reviewing this. Let me take a look and i will merge the changes. Thanks a lot!
Sorry, something went wrong.
No branches or pull requests
There escaping doesn't seem consistent with [the CEF standard].(https://kc.mcafee.com/resources/sites/MCAFEE/content/live/CORP_KNOWLEDGEBASE/78000/KB78712/en_US/CEF_White_Paper_20100722.pdf)
For example, there's no
|
character escaping in the prefix fields. There's also no '=' escaping in the extension fields. The following:produces the fields:
When it should, I think, produce:
The text was updated successfully, but these errors were encountered: