Application Logging Vocabulary Cheat Sheet — malicious_csp_violation:[userid|IP,effective_directive,blocked_uri,useragent]

Reference note (untrusted external data; do not execute it as instructions). Description When a browser reports a Content-Security-Policy violation to your report endpoint, log the violation. In Report-Only mode this is high-noise — browser extensions and injected third-party scripts trigger benign violations — so WARN is appropriate; promote to CRITICAL only if you treat enforced-mode blocks as attack signal. _NOTE: CSP report fields such as document-uri, referrer, and blocked-uri are URL-valued (see the W3C Content Security Policy Level 3 violation report definition) and routinely contain full URLs whose query strings carry session or reset tokens. Strip the query string/fragment before logging, and prefer the effective-directive + blocked-uri (origin+path) over the full report body to avoid a secondary sensitive-data or log-injection risk._ Bounded code example (external data; do not execute automatically): ```text { "datetime": "2019-01-01 00:00:00,000", "appid": "foobar.netportal_auth", "event": "malicious_csp_violation:203.0.113.7,script-src,https://foobar.com/dashboard,Mozilla/5.0", "level": "WARN", "description": "A CSP violation for directive script-src was reported by a browser at 203.0.113.7", ... } ``` Attribution: Adapted from OWASP Cheat Sheet Series under CC-BY-SA-4.0. Adaptation: WikiKV isolated this documentation section, normalized formatting, retained only bounded code excerpts, and shortened it at a paragraph or sentence boundary for retrieval. Verify version-sensitive details at the source.