Content Security Policy
Also called CSP.
A header that restricts which sources a page may load and run.
What it is
A response-header policy that tells the browser which origins are allowed to supply scripts, styles, frames, and other resources for a page, and can forbid inline script entirely. It acts as a defense-in-depth control.
Why it matters
A well-built CSP sharply limits the impact of XSS and clickjacking, so reviewers check both that one exists and that it is not undermined by unsafe-inline or wildcard sources.
In practice
A policy that only permits scripts from the site's own origin, neutralizing an injected inline payload.
What to look for
- unsafe-inline or unsafe-eval in script-src.
- Broad sources such as https: or *.
- Violation reports showing blocked scripts.
Common mistake
Deploying a policy with unsafe-inline. It undoes most of the protection against XSS.
Practice it nearby
CyberKit has no tool for this term itself. These are the closest places to practice it.
- Email Header Analyzer
Walk the Received chain, and read the SPF, DKIM and DMARC verdicts.
- Phishing Case
A reported invoice email: pull the deciding values out of its raw headers, and say what they establish.
In the field
Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.
-
Burp Suite Commercial
An intercepting proxy for testing web apps by hand and with its scanner.
-
ZAP Open source
An open source web app scanner and proxy, often run in CI pipelines.
-
Cloudflare WAF Commercial
Blocks common web attacks at the edge while the code gets fixed.
Read next
- Cross-Site Scripting: Injecting attacker script that runs in other users' browsers.
- Security Headers: HTTP response headers that harden the browser's handling of a site.
- Clickjacking: Tricking users into clicking hidden elements via overlaid framing.