Case 722F6B · Cryptography · L2 Practitioner
TLS 1.0 Still Live on Payments
Live alertThe quarterly external scan flags pay.example.com on your load balancer accepting TLS 1.0 and 1.1 plus TLS_RSA_WITH_3DES_EDE_CBC_SHA; the PCI assessor visits in three weeks.
- 01 What happened?
- 02 What is the impact?
- 03 What do you do?
What a strong answer covers
Try it out loud first. Then check yourself:
- TLS 1.0/1.1 are deprecated (RFC 8996); RSA key exchange has no forward secrecy and 3DES has a 64-bit block (Sweet32).
- Real-world exploitability is limited, but it is a compliance failure: PCI DSS does not allow early TLS for cardholder data.
- Before cutting, check LB logs for the negotiated protocol and cipher per client so you know which legacy integrations will break.
- Switch to a TLS 1.2+ policy with ECDHE and AEAD suites (and TLS 1.3), roll out with comms to affected partners, then rescan.
- Root cause: drifted defaults. Pin TLS policy in infrastructure as code and scan every public endpoint, not just this one.
If the interviewer pushes back
- A large partner still runs a client that only speaks TLS 1.0. What options do you have that do not weaken the main endpoint?