The problem: A business team needs a new backup service. Security writes two must-haves: backups must be encrypted, and the data must stay in the European Union. Procurement collects three bids and picks the cheapest. To fit the contract template, the security lines are shortened and then removed. The contract is signed. At the next audit, the backups are found to be unencrypted.
Words used here: procurement is the team that buys goods and services for the company. A bid is a supplier’s offer with a price. A tender is the process of asking several suppliers to bid. A must-have is a requirement that has to be met, or the product cannot be used. Encryption scrambles data so only those with the key can read it.
Think of a helmet with no strap
A site manager has to buy 50 safety helmets. One supplier is much cheaper than the others, and he orders those. When they arrive, the helmets have no chin strap. The safety officer says so. The manager says, “It was the cheapest.” The supplier did not hide anything, and the manager did not mean any harm. The strap was on the first list. It dropped off before the order went in.
The security requirement is the chin strap.
What it looks like at work
The first request lists price, support hours, and two security needs. Three suppliers bid. Supplier B’s price is about 30 percent lower than the others. These are example numbers. The contract template has a short list of fields and no space for a long security section, so the security needs are summarised as “industry-standard security.”
The business owner signs, pleased to have saved money. Nobody from security sees the final contract. Six months later, the auditor asks to see how backups are encrypted. The supplier’s standard service stores them unencrypted, in another region, and the contract says nothing different.
- 11. RequestPrice, support, and two security needs
- 22. Three bidsSupplier B is about 30 percent cheaper
- 33. TemplateNo room, so it says “industry standard”
- 44. SignedSecurity never sees the final contract
- 55. AuditBackups unencrypted, in another region
Both sides have a fair point. Procurement is asked to save money and has to compare many bids fairly, and the contract template is its tool. Security is right that some requirements are not negotiable. Neither wanted the strap removed. It slipped out between two documents.
You will notice it when:
- Security needs appear in the request and then become “standard security” in the contract.
- Security sees the bids after the choice is made.
- Price is the only column in the comparison.
- Contracts are signed before security has read them.
- The auditor finds a requirement that was never in the contract.
What exactly needs fixing
The fix is not to buy the most expensive supplier. It is to make security needs a pass-or-fail gate before price is looked at, and to check that each one is written into the contract. This card shows the whole problem on one page:
Encryption and EU-only storage were in the request but not in the signed backup contract.
The tender, the contract template, and the sign-off step.
Unencrypted backups are exposed, with a contract that gives no remedy.
- Failed audit
- Possible rule breach
- Costly switch later
- Trust lost
- 11. Pass-or-fail gateMust-haves are checked before price, and a failing bid is out
- 22. Security signs offOne line on the approval form before signing
- 33. A clause for eachEach must-have is its own contract clause, with evidence
Who fixes it: procurement and the security lead
By when: gate in use for the next tender
A blank copy of this card is in the Tools section.
Why it happens
- Price is easy to compare. Security needs are not.
- The contract template has no room for them. So they get shortened.
- Security is not in the room at the end. It sees the request, not the contract.
- There is pressure to show savings. A lower price is a visible result.
- A must-have is written like a wish. “Should be encrypted” is easy to drop.
What happens if you ignore it
The company owns a service that fails its own rules, and cannot change it without cost.
- The audit finds a gap, and the contract gives no right to fix it.
- Data sits in the wrong place or unprotected.
- Changing supplier later costs more than the saving.
- Security stops trusting the process, and procurement stops asking.
At a glance
| Question | Answer |
|---|---|
| How likely is it to hurt us? | Likely, wherever price is the main deciding column. |
| Worst case? | Unencrypted backups are exposed, with a contract that gives no remedy. |
| What does it cost? | A failed audit, a possible rule breach, and a costly switch later. |
| What if we wait? | The next contract repeats it. |
| What does the fix cost? | A one-page gate and a sign-off before signing. |
How to fix it, step by step
Pass-or-fail first, security signs off, then each clause is checked.
- Write the must-haves as pass-or-fail. “Backups are encrypted” and “data stays in the EU.” Not “should”.
- Check them before price. Any bid that fails a must-have is out, however cheap.
- Compare price only among those that pass.
- Ask suppliers to answer in writing. With evidence, such as a certificate or a diagram.
- Put each must-have into the contract as its own clause. Not as “industry standard.”
- Make security sign off before signing. One line on the approval form.
- Review a sample of contracts every six months. To see if requirements stayed in.
The picture shows the order: pass-or-fail first, security signs off, then each clause is checked. The first step stops the cheapest-but-unsuitable bid from ever reaching the price comparison.
Who to bring in: Procurement (runs the gate), the security lead (writes the must-haves and signs off), the business owner (agrees the trade-offs), and legal (checks the clause wording).
Tools and templates
Must-have gate
| Must-have | Evidence needed | Pass / fail | Contract clause |
|---|---|---|---|
| Backups encrypted at rest | Written statement and certificate | Clause number | |
| Data stored in the EU only | Region list from supplier | Clause number | |
| We can audit or receive audit reports | Latest report | Clause number |
Blank finding card
| Field | Write here |
|---|---|
| What is broken | One line, in plain words |
| Where it is | The system, team, or process |
| What could go wrong | In one sentence |
| What it costs us | Money, time, a failed audit, lost trust |
| The fix | The exact action |
| Who fixes it | One name or one team |
| By when | A date, not “soon” |
Email to start the talk
Subject: Making security must-haves a gate in our tenders
Hi. On the backup service, two security requirements were in our first request but not in the signed contract. I would like us to try a small change: security must-haves become pass-or-fail before we read price, and security signs off before any contract. Can we meet for 30 minutes this week? I am not looking to slow you down. I am looking for a way to buy well and keep the protections we asked for.
Field tip
Before a contract is signed, ask: “Which line in here says the thing we said was a must-have?” If nobody can point to it, it is not in.
Words used in this chapter
- Procurement: the team that buys goods and services for the company.
- Bid: a supplier’s offer with a price.
- Tender: the process of asking several suppliers to bid.
- Must-have: a requirement that must be met.
- Encryption: scrambling data so only those with the key can read it.
- Clause: one numbered line of a contract.