Weak cipher suites enabled

The endpoint accepts weaker CBC-era cipher suites. Modern public HTTPS endpoints should prefer AEAD suites such as AES-GCM or ChaCha20 and avoid keeping older CBC suites enabled unless there is a documented compatibility requirement.

What this usually means

• Compatibility profile is too broadThe front-end TLS policy is allowing older cipher suites for legacy clients.
• TLS 1.0 / 1.1 may still be activeOlder protocols often imply older suite families as well.

Fix path

• CloudflareMove away from the `Legacy` cipher profile. If you have Advanced Certificate Manager, configure the zone or hostname to `Modern`, `PCI DSS`, or a tighter custom cipher set. Cloudflare does not let you customize individual TLS 1.3 suites, but you can remove weaker TLS 1.0-1.2 suites.
• NginxSet `ssl_protocols TLSv1.2 TLSv1.3;`, define a modern `ssl_ciphers` list, and keep `ssl_prefer_server_ciphers on;` for TLS 1.2 and earlier.
• ApacheRestrict protocols to TLS 1.2 and TLS 1.3, tighten `SSLCipherSuite` to modern AEAD suites, and keep `SSLHonorCipherOrder on` for TLS 1.2 and earlier.
• IISDisable older protocols and remove weaker CBC suites from the SChannel cipher suite order so only modern suites remain enabled.

Safe rollout advice

• Drop legacy protocols firstRemoving TLS 1.0 and TLS 1.1 usually eliminates the weakest suites immediately.
• Prefer AEAD-only where possibleFor public sites, AES-GCM and ChaCha20 are the usual target. Only keep weaker suites if you have a documented compatibility dependency.

Verify after change

• Re-run TLS AdvisorThe accepted cipher suite inventory should stop listing weak suites in red.
• Cross-check with SSL LabsUse SSL Labs or another external scanner to confirm the public edge no longer advertises the weak suites.