Case 722F6B · Cryptography · L2 Practitioner

TLS 1.0 Still Live on Payments

Practise as: Incident drillLevel: L2 Practitioner

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.

  1. 01 What happened?
  2. 02 What is the impact?
  3. 03 What do you do?
What a strong answer covers

Try it out loud first. Then check yourself:

  1. TLS 1.0/1.1 are deprecated (RFC 8996); RSA key exchange has no forward secrecy and 3DES has a 64-bit block (Sweet32).
  2. Real-world exploitability is limited, but it is a compliance failure: PCI DSS does not allow early TLS for cardholder data.
  3. Before cutting, check LB logs for the negotiated protocol and cipher per client so you know which legacy integrations will break.
  4. 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.
  5. 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?

Go deeper

More Cryptography cards

All Cryptography cards →

cardosec draws a security topic and gives you a clock: explain it out loud with no notes, then see what you covered and what you missed. Free during early access.

Reviewed 2026-10-09