CFG-002high SeveritySecurity Misconfiguration & Headers

Strict-Transport-Security (HSTS) Active with 1-Year Max Age

AI templates do not set HSTS headers, leaving browsers vulnerable to SSL stripping attacks on initial visits.

1-Click Fix Prompt for Cursor & Claude Code
Review my codebase for "Strict-Transport-Security (HSTS) Active with 1-Year Max Age" (CFG-002).
Issue: AI templates do not set HSTS headers, leaving browsers vulnerable to SSL stripping attacks on initial visits.
Remediation required: Configure Strict-Transport-Security: max-age=31536000; includeSubDomains; preload in your production host config.

Please:
1. Locate any occurrences of this issue across my repository.
2. Refactor the code to follow production standards without breaking existing functionality.
3. Provide a clear command or step to test and verify the fix.

Why AI Assistants Write This Bug

AI templates do not set HSTS headers, leaving browsers vulnerable to SSL stripping attacks on initial visits.

AI code generation prioritizes immediate syntax execution over production edge cases. When an assistant hits an undefined variable or strict type error, it frequently takes the path of least resistance rather than implementing standard pre-launch security patterns.

Code Comparison

Common AI Code PatternVulnerable
// Vulnerable AI-generated pattern for: Strict-Transport-Security (HSTS) Active with 1-Year Max Age
// Problematic pattern: AI templates do not set HSTS headers, leaving browsers vulnerable to SSL stripping attacks on initial visits.
Launch-Ready Fix
// Production-ready fix for: Strict-Transport-Security (HSTS) Active with 1-Year Max Age
// Recommended remediation: Configure Strict-Transport-Security: max-age=31536000; includeSubDomains; preload in your production host config.

Remediation & Verification Checklist

Remediation: Configure Strict-Transport-Security: max-age=31536000; includeSubDomains; preload in your production host config.
  1. Search your codebase for pattern matching "Strict-Transport-Security (HSTS) Active with 1-Year Max Age".
  2. Apply the recommended remediation: Configure Strict-Transport-Security: max-age=31536000; includeSubDomains; preload in your production host config.
  3. Run local build and test commands to ensure no regressions.
  4. Verify in your browser or with curl that the issue is resolved.
Audit All 108 Checks in One Click

Checking items one by one takes hours. Let us do it in 2 minutes.

With the Founder Pass ($15 one-time), we automatically scan your repository for this issue, plus all other 107 launch checks across secrets, Stripe webhooks, Supabase RLS, and security headers.