HighFile-scopePHP Plug & play

Enforce HTTPS, HSTS, and secure sessions

Force HTTPS via middleware, set HSTS, and configure session cookies with secure=true, http_only=true, same_site=lax or strict in config/session.php.

Why this matters

Meets SOC 2 encryption-in-transit and session hardening requirements.

Side-by-side examples engineers can pattern-match during review.

Avoid

$response->header('Set-Cookie','sid=1');

Prefer

config(['session.secure'=>true,'session.http_only'=>true,'session.same_site'=>'lax']);

Good

URL::forceScheme('https')

Bad

config(['session.secure'=>false])

From the same buckets as this rule.

Critical
Encrypt sensitive data at rest with KMS and rotate keys
Use envelope encryption (AES-256-GCM) with cloud KMS-managed CMKs for databases, object storage, and backups. Rotate CMKs at least annually and rotate DEKs per object/file.
compliance-soc2-essentialssecrets-credentials+1
Critical
Enforce TLS 1.2+ and HSTS on all external endpoints
Public services must require TLSv1.2 or higher and set HSTS (max-age ≥ 15552000, includeSubDomains). Reject plaintext HTTP and weak ciphers; cookies must be Secure and HttpOnly with SameSite set.
compliance-soc2-essentialssecurity-hardening+1
Critical
Use a secrets manager and 90-day rotation policy
All credentials (API keys, DB passwords, tokens) must be stored in a secrets manager with automatic rotation ≤ 90 days; forbid hardcoded or .env-committed secrets via CI checks.
compliance-soc2-essentialssecrets-credentials+1