01Description
The application did not set one or more recommended HTTP security headers, including Content-Security-Policy, X-Content-Type-Options and Referrer-Policy.
02Impact
Security headers provide defense in depth. Without a Content Security Policy, any cross-site scripting flaw is easier to exploit; without X-Content-Type-Options, browsers may interpret content as a different type; without a referrer policy, sensitive URLs may leak to third parties.
03Severity
Typically
Low
Typically Low. Low as a standalone finding. Raise it where a missing control would have prevented a confirmed vulnerability, for example a missing CSP alongside cross-site scripting.
04How to verify
- 1Inspect response headers on key pages and API responses.
- 2Evaluate any existing Content Security Policy for unsafe directives such as 'unsafe-inline' and wildcard sources.
- 3Record missing or weak headers per response type.
Testing note: only test systems you are authorized to test, within the agreed scope and rules of engagement. Verification steps are written for professional testers and avoid destructive techniques.
05Remediation
- 1Introduce a Content Security Policy, starting in report-only mode, and tighten it to remove unsafe-inline and broad sources.
- 2Set X-Content-Type-Options: nosniff and a Referrer-Policy such as strict-origin-when-cross-origin.
- 3Set frame-ancestors in the CSP to control framing.
Draft findings like this from your own evidence
Book a demo