TLS dan transport for Jenkins
high5 checks
TLS protects credentials and session cookies in transit. A valid chain, a modern protocol and no downgrade path are the baseline.
What Jenkins 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
Jenkins context
CI/CD automation server.
Jenkins holds deployment credentials — never expose it publicly without SSO and network restrictions.