Individual skill
performing-security-headers-audit
Auditing HTTP security headers including CSP, HSTS, X-Frame-Options, and cookie attributes to identify missing or misconfigured browser-level protections.
internal/tools/skills/data/web-application-security/performing-security-headers-audit/SKILL.md
Source commit d42f381ad34843e71a42658e5c57290c713e85af
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 7, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,313
- Repository last updated
- Nov 7, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- cybersecurity Repository topic
- security Repository topic
- bug-bounty Repository topic
- automation Repository topic
- autonomous-pentesting Repository topic
- ai-agent Repository topic
- ai-security Repository topic
- ethical-hacking Repository topic
- golang Repository topic
- penetration-testing Repository topic
- penetration-testing Declared skill tag
- security-headers Declared skill tag
- csp Declared skill tag
- hsts Declared skill tag
- owasp Declared skill tag
- web-security Declared skill tag
- hardening Declared skill tag
- security Derived category
- testing Derived category
- security-application Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
Read excerpt
# Performing Security Headers Audit
## When to Use
- During authorized web application security assessments as a standard configuration review
- When evaluating browser-level protections against XSS, clickjacking, and data leakage
- For compliance assessments requiring security header implementation (PCI DSS, SOC 2)
- When performing initial reconnaissance to identify easy-win security improvements
- During CI/CD pipeline security gate checks for new deployments
## Common Misconfigurations & Verification
- **CSP in `Report-Only` mode**: a rich-looking policy that enforces nothing. If only `Content-Security-Policy-Report-Only` is present, XSS is unmitigated. Verify the enforcing `Content-Security-Policy` header exists, not just the report-only twin.
- **`unsafe-inline`/`unsafe-eval` or wildcard `*` in `script-src`**: neuters the policy against XSS. Also flag a CSP with **no `object-src 'none'` and no `base-uri 'self'`** — both are common bypass gaps even in otherwise-strict policies.