By problem

Solutions

Six things that go wrong in your visitors' browsers, and what the controls browsers enforce do about each. Every page follows the same order: the attack, what the browser reports, what HeaderHawk does with the report, and where CSP alone is not enough.

What client-side security is covers the layer these attacks land in, and every control for it.

What these pages are not claiming

HeaderHawk receives violation reports. It is not in your visitors' request path, it does not run on your pages, and it never blocks anything. When something is blocked, your own policy header did it, in the visitor's browser. Report-only mode, where every rollout starts, blocks nothing. Each page describes what becomes visible, not what becomes impossible.