-
Notifications
You must be signed in to change notification settings - Fork 294
Audit log for blocked transactions missing Portion K population. #180
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
Comments
Other Q's I have are what are all the values in the audit log reference file when in Concurrent if someone can link me to any further docs on some of the not straightforward values? Example
Mostly curious what the 118 is, the 0, and the 2218.00000(microsecond or millisecond to execute the checks?) |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days |
still a nice to have thing working in the audit logs. |
Sorry @jeremyjpj0916. The "nostale" tag has been set for this one and it's now reopened. We'll get to this one when possible. Thank you |
The K part of the audit log is missing the implementation - It is marked as TODO on the code. |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days |
ping. |
Uh oh!
There was an error while loading. Please reload this page.
Currently setting:
Based on table I should be seeing this kinda info:
On a given random blocked transaction I ended up getting this log:
/tmp/audit/20200213/20200213-2334 $ cat 20200213-233405-158163684568.835438
Luckily Section H does have all the details from the tx it seems so audit log was bringing value because it seems like H is made up of two parts strung together Part 1: New info around the block that does NOT get printed out to NGINX stderr + Just the stderr print statement I see in typical logs when audit is disabled. Section H luckily does including the CRS error code: 920470 in that top half, which after reviewing the 3.2/master branch and the 3.3/dev branch of CRS it showed they had fixed up the regex of the rule in a way that my Content-Type header was no longer being blocked! Which was awesome to just patch that rule over and continue testing and finally generate a valid OAuth2.0 token not getting blocked by the WAF.
My ask here would be ModSec does parse and grab all the matching id's that lead to a block in section K cleanly printed, makes for easy copy paste searching in the repo's to figure out what rules to inspect for FP's and aligns with the current documentation on all the fields.
Note, I had to use the pending outstanding PR fix to capture blocked tx's in the audit log. Glad that was out there or I woulda been rekt, can't use a WAF without some form of audit inspection for blockings.
Version: Master branch right now of the ngx connector + libmodsec 3.0.4
The text was updated successfully, but these errors were encountered: