The Blueprint

Suppliers and third parties.

The suppliers you depend on: knowing who they are, checking them before you sign, binding them to security in contracts, reviewing the critical ones, and leaving cleanly when a relationship ends.

SUP 16 requirements

Foundation

RW-SUP-01A list of your suppliers

What
Keep a list of your suppliers that records what each one provides, what data or access it has, how much harm its failure would cause you and so which of them are critical.
Why
You can only guard against the suppliers you know about, and recording which ones hold your data or could stop your business shows you where checks, contract terms and fallback plans will matter most.
Protects
Confidentiality · Integrity · Availability

Read the guide: Post-quantum cryptography: the questions to ask your suppliers

RW-SUP-02Supplier access limited to the job

What
Give a supplier access to your systems only for the work you've agreed with them, keep a record of what they do while connected, and remove the access as soon as that work is finished or the person using it stops working on it.
Why
Attackers often get in through a supplier's remote access because it is trusted, broad and rarely watched, so access that's confined to the task and switched off afterwards leaves them much less to use.
Protects
Confidentiality

Read the guide: The tool that can reach every computer

RW-SUP-03Contracts that bind suppliers to security

What
Make sure your contracts with suppliers that handle your data or systems cover how they must protect them, how quickly they must tell you about a breach, your right to check, and the return or deletion of your data at the end, and where a supplier offers only standard terms, check those terms cover these points before you sign.
Why
A contract is often your only lever over a supplier, and clear security terms oblige them to protect what you've entrusted to them, warn you in time to act when something goes wrong and give your data back when you part company.
Protects
Confidentiality · Integrity · Availability

Read the guide: Post-quantum cryptography: the questions to ask your suppliers

RW-SUP-04Agreements in place before personal data is shared

What
Sign a written data processing agreement with every supplier that will handle personal data on your behalf before you share any of it with them.
Why
Data protection laws in most countries hold you responsible for what your suppliers do with personal data, and an agreement signed beforehand commits them to protecting it and using it only as you instruct, which protects both the people concerned and your organisation.
Protects
Confidentiality

Established

RW-SUP-05Suppliers checked before signing

What
Check a new supplier's security, and the security of the software or service it will provide, before you sign with them, in proportion to the data and access they will have.
Why
It's far easier to walk away from a weak supplier, or to insist on improvements, before a contract is signed than after your data and systems have come to depend on them.
Protects
Confidentiality · Integrity · Availability

Read the guide: Post-quantum cryptography: the questions to ask your suppliers

RW-SUP-06Critical suppliers reviewed

What
Review each critical supplier's security regularly, including their certificates, any incidents they've had and how well they've kept to the contract.
Why
Suppliers change over time through cost cutting, takeovers and new subcontractors, so regular reviews spot a supplier whose security is slipping while there's still time to raise it with them or make other plans.
Protects
Confidentiality · Integrity · Availability

Read the guide: Post-quantum cryptography: the questions to ask your suppliers

RW-SUP-07Supplier risks in your risk register

What
Record the security risks that each critical supplier brings in your risk register, and assess and treat them alongside your other risks.
Why
Problems at a supplier can harm you as much as anything inside your own walls, so managing them in the same register gives them the same scrutiny and ownership, and lets leaders weigh them against every other risk you face.
Protects
Confidentiality · Integrity · Availability

Read the guide: When the platform everyone uses stops

RW-SUP-08Supplier changes assessed

What
Assess how any significant change at a critical supplier, such as a takeover, a new subcontractor or your data moving to another country, affects your security, and decide how to respond.
Why
A supplier you checked carefully at the start can become a quite different proposition after a takeover or a change of hosting, and looking at such changes as they happen stops your risk rising without anyone noticing.
Protects
Confidentiality · Integrity · Availability

RW-SUP-09An exit plan for each critical supplier

What
Keep an exit plan for each critical supplier, including cloud services, that sets out how you would get your data back and move to an alternative.
Why
Suppliers fail, get bought, raise prices or suffer long outages, and knowing in advance how to retrieve your data and where to go next stops you being trapped with a supplier that can no longer serve you safely.
Protects
Availability

Read the guide: When the platform everyone uses stops

RW-SUP-10Relationships ended cleanly

What
Remove a supplier's access, get back your equipment and data, and obtain written confirmation that any copies they kept have been deleted, whenever a supplier relationship ends.
Why
Former suppliers who still hold access or copies of your data are a risk that nobody is watching any more, so closing everything off at the end means nothing is left behind that could later be lost, stolen or misused.
Protects
Confidentiality

RW-SUP-11Software and equipment from trusted sources

What
Obtain software, updates and equipment only from the maker or another source you trust, and check that they are genuine and unaltered before using them.
Why
Attackers hide malware in fake downloads, tampered installers and lookalike packages, so taking software only from sources you trust, and checking its signature, stops you installing their code for them.
Protects
Integrity

RW-SUP-12Security set for software built for you

What
Set out the security standards that software a supplier builds for you must meet, and check that it meets them before you accept it.
Why
Software written for you by someone else becomes your problem once it's live, so agreeing security standards at the start and testing against them before handover saves you inheriting weaknesses that you'd then have to pay to fix.
Protects
Integrity

RW-SUP-16Only approved online services for work

What
Let staff hold or share work information only in online services, such as file-sharing, messaging and note-taking apps, that are on your approved list, and look regularly for any others in use.
Why
When staff use their own choice of online services, your information ends up in places you haven't checked, can't see and can't get back. Keeping work to approved services means you know where it is and can protect it.
Protects
Confidentiality

Advanced

RW-SUP-13Subcontractors known and held to the same standard

What
Require your critical suppliers to tell you which subcontractors they use for your services and to hold those subcontractors to security standards as strong as their own.
Why
Many supplier breaches start at a smaller firm two or three steps down the chain, so knowing who handles your service and making sure the same protections reach them closes a gap you would otherwise never see.
Protects
Confidentiality · Integrity · Availability

RW-SUP-14Sanctions and ownership checks

What
Screen critical suppliers against sanctions lists, and for ownership or control by foreign states or other parties of concern, before signing and at intervals afterwards.
Why
A supplier that becomes subject to sanctions or falls under hostile control may have to be dropped overnight, or could be forced to hand over your data, so finding out early gives you time to plan a way out.
Protects
Confidentiality · Availability

RW-SUP-15Critical suppliers in your incident plans

What
Agree with each critical supplier how you will work together during an incident or outage, and write their contacts and role into your incident and recovery plans.
Why
When a supplier's service is caught up in an incident, time lost finding the right person or arguing over who does what can cost hours, so settling it beforehand means you can act together straight away.
Protects
Availability

Read the guide: The tool that can reach every computer