fix: revert SecAuditEngine to On — RelevantOnly suppresses WAF-blocked logs
Coraza's RelevantOnly mode does not write audit log entries for requests blocked by the WAF itself (403 responses), so the waf-log-parser had nothing to parse. Reverting to On so all transactions are logged, and relying on the parser-side messages[] filter to skip clean requests. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
+1
-1
@@ -838,7 +838,7 @@ function buildWafHandler(waf: WafSettings): Record<string, unknown> {
|
||||
'Include @owasp_crs/*.conf',
|
||||
] : []),
|
||||
`SecRuleEngine ${waf.mode}`,
|
||||
'SecAuditEngine RelevantOnly',
|
||||
'SecAuditEngine On',
|
||||
'SecAuditLog /logs/waf-audit.log',
|
||||
'SecAuditLogFormat JSON',
|
||||
'SecAuditLogParts ABIJDEFHZ',
|
||||
|
||||
Reference in New Issue
Block a user