The Website Security Checklist Every Business Needs in 2026

Most websites are insecure not because security is hard, but because nobody made a checklist. These twenty-three items prevent 95% of real-world attacks. None of them require a security specialist — your developer should be doing all of them already.

Authentication and sessions

  1. Passwords hashed with bcrypt or argon2 (never MD5/SHA1).
  2. Rate limiting on login endpoint (5 attempts per minute).
  3. 2FA available, mandatory for admin accounts.
  4. Session cookies HttpOnly, Secure, SameSite=Lax.
  5. Sessions invalidated on password change and logout.
  6. Password reset tokens expire in 30 minutes.

Input validation

  1. All user input validated server-side (client validation is UX, not security).
  2. SQL injection prevented via parameterized queries / Eloquent / Prisma.
  3. XSS prevented via proper output encoding.
  4. CSRF tokens on all state-changing requests.
  5. File uploads scanned, type-checked, size-limited, stored outside web root.

Transport and storage

  1. HTTPS everywhere with HSTS preload.
  2. TLS 1.2 minimum (1.3 preferred).
  3. Sensitive data encrypted at rest.
  4. Secrets in environment variables, never in code.
  5. Database backups encrypted and tested quarterly.

Headers and policies

  1. Content-Security-Policy header configured.
  2. X-Content-Type-Options: nosniff.
  3. X-Frame-Options: SAMEORIGIN.
  4. Referrer-Policy: strict-origin-when-cross-origin.

Operational

  1. Dependencies updated monthly. Use Dependabot or Renovate.
  2. Logs structured and shipped to a separate system (logs are evidence in a breach).
  3. Incident response plan written before you need it.

If your site fails any of these, book a security review. I deliver a written report with prioritized fixes within 1 week.

Ready to Start Your Project?

If this article was helpful, imagine what we could do together. Get a free 30-minute consultation and an honest recommendation for your project — no sales pitch.

Book Free Consultation