TLS dan transport for Fastly
high5 checks
TLS protects credentials and session cookies in transit. A valid chain, a modern protocol and no downgrade path are the baseline.
What Fastly must have
- Certificate chain validates against public trust stores
- Expiry monitored automatically, no manual renewal
- TLS 1.2 and 1.3 only; 1.0 and 1.1 disabled
- HTTP redirects to HTTPS with a permanent redirect
- No mixed content on any page
How to fix it
- 1Enable auto-renewal with your host or CDN and alert at 21 days remaining
- 2Force HTTPS at the edge and remove any route that serves plain HTTP
Fastly context
Edge cloud and CDN with VCL configuration.
Review VCL for cache poisoning and ensure the origin only trusts Fastly IPs.