Website headers and TLS audit
Review existing HTTP header captures and TLS reports for gaps.
Customize the recipe
0/1500 characters
Prompt preview
# Website headers and TLS audit Review existing HTTP header captures and TLS reports for gaps. ## Read-only scope Review only the authorized app, site, server, or local source named or supplied by the user. Work from provided code, configuration, redacted exports, and completed test results. Use URLs and hostnames as scope identifiers. Request the missing artifacts if evidence is insufficient. Use existing offline, read-only analysis on those artifacts. Exclude live probing, vulnerability reproduction, exploit payloads, credential testing, new load generation, and changes to the target or its files. ## Tools and setup · Universal Use the linked resources as references for interpreting the supplied material. Follow the read-only scope when a linked workflow describes other actions. - [Security Best Practices](https://github.com/openai/skills/blob/main/skills/.curated/security-best-practices/SKILL.md) (Skill) — Use the language-specific guidance to identify insecure defaults and review supplied code. - [OWASP Secure Headers](https://github.com/OWASP/www-project-secure-headers) (Repository) — Compare captured HTTP headers with current OWASP recommendations. - [OWASP ASVS](https://github.com/OWASP/ASVS) (Repository) — Map observed web security controls to relevant verification requirements. ## Workflow Use supplied HTTP response headers, TLS report, CDN settings, and proxy configuration. Compare applicable protections across the documented routes and distinguish certificate, redirect, and browser-policy observations. ## Deliverable A website transport and response-header report with findings by supplied capture or route. - Minimalism: Apply this style to report presentation only. Plain Markdown is sufficient. ## Acceptance checks - [ ] Each reported header or TLS setting cites its capture or configuration source. - [ ] Explicitly record which routes, redirects, or TLS settings lack evidence. - [ ] Give each finding a severity, confidence, affected component, evidence reference, impact, and recommended mitigation. Explicitly list unverified controls and gaps. - [ ] Redact credentials, tokens, personal data, and sensitive values in the report.
Recipe resources
Source, setup, and compatibility details.
Security Best Practices
Use the language-specific guidance to identify insecure defaults and review supplied code.
Upstream documents Codex.
28.9K GitHub stars on the source repository
OWASP Secure Headers
Compare captured HTTP headers with current OWASP recommendations.
License · Apache-2.0
227 GitHub stars
OWASP ASVS
Map observed web security controls to relevant verification requirements.
License · CC-BY-SA-4.0
3.8K GitHub stars