Security Headers
HTTP response headers that harden the browser's handling of a site.
What it is
A set of response headers (such as HSTS, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, and Content-Security-Policy) that instruct the browser to enforce protections against downgrade, sniffing, framing, and injection.
Why it matters
They are cheap, high-use defense-in-depth, so their presence and correctness are a quick early read on an application's security posture during a review or response.
In practice
An HSTS header forcing browsers to use HTTPS so a user cannot be silently downgraded to plain HTTP.
What to look for
- Missing CSP, HSTS or frame-ancestors.
- Headers set on some pages but not others.
- Headers that leak server versions.
Common mistake
Adding headers once and never checking. Deploys and CDN changes can drop them.
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
- Content Security Policy: A header that restricts which sources a page may load and run.
- Cross-Origin Resource Sharing: Headers that relax the same-origin policy for chosen origins.
- Clickjacking: Tricking users into clicking hidden elements via overlaid framing.