DKDKCISSP
← Cybersecurity on the GroundCHALLENGE

The Client Insists on the Old TLS 1.0 Connection

By Deepak Kumar, CISSP

The problem: Your client’s old billing system can only connect to ours using TLS 1.0, an old way of locking the connection that attackers can now break. Your own rule says TLS 1.2 or newer. The project team says, “The client insists.” Security says, “We cannot allow that.” The old lock stays in place, and nobody has signed for it.

Words used here: TLS is the lock that protects data while it travels between two systems, like the padlock you see in a web browser. TLS 1.0 is a very old version of that lock, retired years ago because attackers can now break it. TLS 1.2 is the newer, safe version. A client requirement is something the client asked for in the contract or in the project.

Think of a fire door propped open

A restaurant guest asks the owner to keep the fire door open, because it is more convenient. The door is the fire exit, and it is meant to stay shut. The owner could say yes to keep the guest happy, but then the door stays open for everyone, all night, with nobody having decided it.

The fire door propped open
Fire exit door, meant to stay shut
Can we keep this open?
Guest
That is the fire exit.
Restaurant owner
Convenient for one person, risky for everyone.

What it looks like at work

Our app sends customer files every night to the client’s billing system. The client’s billing system is old and can only talk using TLS 1.0. Our rule says the minimum is TLS 1.2. The client says, “Our billing system cannot be upgraded this year. Please keep it as it is.” The project team agrees, to avoid a fight, and the connection goes live. Security hears about it later, and says it breaks the rule. Both teams quote a rule, and nobody checks what the contract actually says.

How an old TLS 1.0 connection stays in place
  1. 1Client asksKeep the old TLS 1.0 lock
  2. 2SecurityAttackers can break it. Not allowed.
  3. 3Project teamThe client insists.
  4. 4StuckEach side quotes its own rule
  5. 5ResultTLS 1.0 stays, nothing signed
Nobody decided. TLS 1.0 just stayed, and nobody signed for it.

Both sides are half right. The client is right that it is their system, and that they cannot always upgrade fast. Security is right that TLS 1.0 is a real risk, and it affects our customer files too. What is missing is a written decision, with the risk explained to the client in plain words.

You will notice it when:

  • “The client insists” is the only reason given for keeping TLS 1.0.
  • Nobody has read what the contract says about the connection.
  • The old connection is live, and no document says who agreed to it.
  • Security hears about it after it is live.
  • The client has never been told what the risk is.

What exactly needs fixing

The first fix is not technical. It is a written decision that explains the risk to the client, and that someone signs. This card shows the whole problem on one page:

An old TLS 1.0 connection stays because the client asked
WHAT IS BROKEN

Our link to the client's billing system uses TLS 1.0, an old lock attackers can break, with nothing signed.

WHERE IT IS

The nightly file link between our app and their billing system.

WHAT COULD GO WRONG

An attacker on the network can read or change files in transit.

WHAT IT COSTS US
  • Data exposed
  • Contract dispute
  • Unclear blame
  • Audit finding
THE FIX, IN THREE MOVES
  1. 1
    Read the contract
  2. 2
    Offer 3 options
  3. 3
    Get it in writing
WHO FIXES IT

Project head, security

BY WHEN

Client reply in 2 weeks

A blank copy of this card is in the Tools section.

Why it happens

  • “Client requirement” sounds final. So people stop asking what the contract really says. Often it says the system must connect to the client’s billing system. It does not say it must use TLS 1.0.
  • Nobody wants to push back on a client. Especially a big one.
  • The client may not know the risk. Nobody explained it in their words.
  • The project team is measured on dates. An argument costs days.
  • Security hears late. So it can only say no.
  • There is no standard way to record an exception. So it never gets written.

What happens if you ignore it

An old lock stays on the door that carries customer files, and nobody can say who allowed it.

  • An attacker on the network breaks the old lock and reads or changes the files in transit.
  • After an incident, each side blames the other, and nothing is written down.
  • An auditor finds TLS 1.0 and the missing approval.
  • The client says, “You never told us this was risky.”

At a glance

QuestionAnswer
How likely is it to hurt us?Quite likely. Old locks like TLS 1.0 are the first place attackers look.
Worst case?Customer files are read or changed in transit, with no record of who agreed.
What does it cost?Clean-up, a dispute with the client, and a failed audit.
What if we wait?TLS 1.0 becomes normal, and harder to change.
What does the fix cost?One honest talk with the client, and a short signed note.

How to fix it, step by step

Turn “the client insists” into a decision that is explained, chosen, and written down.

  1. Read the contract wording. What does it really say? “Must work with the client’s billing system” is not the same as “must use TLS 1.0.”
  2. Describe the risk in the client’s words. What could happen to their data, their customers, their name. No technical names.
  3. Offer three options. The client upgrades to TLS 1.2 by a date. Or we keep TLS 1.0 on one walled-off gateway. Or the client accepts the risk in writing.
  4. Make the walled-off gateway real. Put TLS 1.0 only on a small separate gateway, allow only the client’s address to reach it, and use TLS 1.2 on our side behind it. Watch it closely.
  5. Ask for the decision in writing. A short email or a signed note, with a date.
  6. Set a review date. An exception without an end date becomes permanent. For example, 90 days (set your own).
  7. Record it. One line in the exceptions list, with the owner and the review date.
  8. Look again at the review date. Ask if the client can now upgrade.
Three options for TLS 1.0, and one must be written down
A. Client upgradesMove to TLS 1.2 by an agreed date.
B. Walled-off gatewayKeep TLS 1.0 on one walled-off gateway.
C. Client acceptsA signed note with the risk and a review date.
Never leave it silent. Always pick one, in writing.

The picture shows the three options. The one thing not allowed is silence.

Who to bring in: The head of the project, the account or relationship manager, security, and the client’s technical contact.

Tools and templates

What to check in the contract

QuestionWhy it matters
Does it name TLS 1.0, or only say “work with our billing system”?Often the contract is looser than people think
Who is responsible for the client side of the connection?Decides who must upgrade it
Is there a clause about security or data protection?May already require a safe version
What does it say about changes?Shows how to raise a change request

Exception record

FieldWrite here
What the exception isExample: TLS 1.0 on the connection to the client’s billing system
Why it is neededThe client’s reason
The riskIn one sentence
The safety layerWalled-off gateway, one allowed address, watched
Who acceptedName and role, on both sides
Review dateA date, not “later”

Blank finding card

FieldWrite here
What is brokenOne line, in plain words
Where it isThe system, team, or process
What could go wrongIn one sentence
What it costs usMoney, time, a leak, lost trust
The fixThe exact action
Who fixes itOne name or one team
By whenA date, not “soon”

Email to the client

Subject: The old TLS 1.0 connection, and three ways forward

Hi [name]. We understand that your billing system needs the older TLS 1.0 way of connecting. We want to make sure it is safe for both of us. TLS 1.0 is a very old lock that attackers can now break, which could put your customer files at risk. We see three options: you upgrade to TLS 1.2 on a date we agree, we keep TLS 1.0 on one walled-off gateway, or you accept the risk in writing with a review date. Could we talk for 20 minutes this week to choose one?

Field tip

Do not ask, “Can we stop the client from asking?” Ask, “What does the contract say, and who will sign for this risk?”

Words used in this chapter

  • TLS: the lock that protects data while it travels between two systems.
  • TLS 1.0: a very old version of that lock that attackers can now break.
  • TLS 1.2: the newer, safe version.
  • Gateway: a small separate system that sits between two systems and passes data between them.
  • Client requirement: something the client asked for in the contract or in the project.
  • Exception: an agreed, written reason why a rule does not apply, for a set time.