ISO 27001 Control A.5.20: Addressing Information Security Within Supplier Agreements
A supplier assessment tells you what a supplier says it does. A contract is where you get to write down what it must do. A.5.20 is about making sure the security expectations you identified in your supplier process actually appear in the agreement, in terms both sides understand. It is the 20th of 37 organizational controls in our walk through Annex A.
Most organizations sign dozens of contracts without anyone reading the security clauses, because the supplier’s standard terms are accepted as they come. That is understandable, and for low-risk suppliers it may be fine. For the suppliers who hold your data or run part of your operation, it is worth knowing exactly what has been promised, and what has not.
What the control requires
Annex A control 5.20 of ISO 27001:2022 states that relevant information security requirements shall be established and agreed with each supplier based on the type of supplier relationship.
The key elements:
- Relevant requirements - only the requirements that matter for what the supplier does, not a standard fifty-page schedule for everyone
- Established and agreed - you define them, and the supplier accepts them in writing
- Each supplier - every supplier gets considered, even if the outcome for some is a simple confidentiality clause
- Based on the type of supplier relationship - a hosting provider, a consultant and a courier need different terms
A.5.20 is a preventive control in ISO/IEC 27002:2022. Annex A states the control; ISO 27002 gives guidance, with a long list of possible content: a description of the information to be provided and how it will be accessed, classification and labelling alignment, legal and regulatory requirements, rules for acceptable use, incident handling, training expectations, subcontracting conditions, screening of the supplier’s personnel, rights to audit, and what happens at the end of the contract. It stresses that the list is a menu, not a mandatory template.
How to implement supplier agreements
Start from your supplier tiers
The register and risk tiers from information security in supplier relationships tell you how much contract effort each supplier deserves. A practical model is to create two or three standard requirement packs:
- Baseline for suppliers with minimal access: confidentiality, compliance with your reasonable security rules on your premises and prompt notification of anything affecting your information
- Standard for suppliers who process internal information or have limited system access: the baseline plus defined security measures, breach notification, return or deletion of data and restrictions on subcontracting
- Enhanced for suppliers who host or process confidential or personal information or have privileged access: the standard pack plus audit or assurance rights, specific technical controls, business continuity commitments, detailed incident procedures and exit assistance
Keeping packs in a shared folder means procurement and legal teams can attach the right one in minutes. Align the wording with your own classification of information so a supplier knows what “confidential” means to you.
Cover the clauses that matter most
Whatever the tier, certain topics come up again and again:
- Confidentiality and permitted use. What the supplier can do with your information, and what it cannot, with obligations that survive the end of the contract. For individuals, see confidentiality or non-disclosure agreements.
- Security measures. The controls expected, such as encryption, access control, logging and vulnerability management, expressed in terms you can verify.
- Incident notification. How quickly the supplier tells you about a security incident affecting your information, to whom and with what detail. Choose a realistic window and name a contact.
- Location and subcontractors. Where information is stored and whether the supplier may use others to handle it, with a requirement to pass down equivalent obligations and tell you of changes.
- Access and transfer. How information moves, in line with your information transfer rules, and how supplier staff get access.
- Assurance and audit. The right to see reports, certificates or to audit, proportionate to the risk.
- Exit. Return or secure deletion of information, removal of access and a reasonable transition period.
Where the supplier processes personal data for you, privacy law in many places requires specific terms in the contract. The details differ by jurisdiction, so involve your privacy or legal adviser rather than relying on a security checklist alone.
Deal with the supplier’s standard terms
Large providers rarely negotiate. If you cannot change the terms, do not ignore the gap. Read what the agreement does promise, such as a security addendum, a shared responsibility model or published certifications, compare it with your requirement pack, and record the difference as a risk with a decision: accept, reduce through your own controls, or choose another supplier. Many cloud services publish a security schedule that covers more than people expect, and noting where it is makes later reviews quick.
Make the agreement operational
A clause nobody remembers is worth nothing. Give the relationship owner a one-page summary of the key obligations, such as the incident notification window and renewal date, and store the signed agreement where it can be found. Keep acceptance records and requested changes. Note renewal dates in a calendar so that terms are reviewed before they roll over automatically, which is also an opportunity to revisit access rights granted to the supplier.
Finally, remember that agreements are a tool, not a shield. A well-drafted clause does not prevent an incident; it only tells you what you can expect afterward. Pair the contract with the practical steps in your own environment, such as limiting what you send, encrypting it and keeping your own copies, so that you are not relying on a signature alone. The strongest position combines sensible terms, good technical hygiene and a relationship in which problems are raised early.
Related controls and clauses
A.5.19 connection. Information security in supplier relationships identifies the suppliers and risks that the agreement addresses.
A.5.14 connection. Information transfer agreements often form part of the supplier contract.
A.6.6 connection. Confidentiality or non-disclosure agreements are the individual-level counterpart to contract confidentiality clauses.
A.5.12 connection. Classification of information gives suppliers shared terms for how to treat your information.
A.5.11 connection. Return of assets applies when supplier staff hold your equipment.
Clause 8.1 connection. Clause 8.1, Operational planning and control, requires that outsourced processes relevant to the ISMS are controlled, which is exactly what the agreement provides.
Forward reference. Managing information security in the ICT supply chain (A.5.21) and monitoring, review and change management of supplier services (A.5.22) follow in the next posts.
What auditors check
Agreements for key suppliers. Auditors pick several suppliers from your register, especially higher-risk ones, and ask to see the contract or addendum.
Relevance to the relationship. They look for security terms that match the service: data handling for processors, access rules for remote support, on-site rules for facilities providers.
Traceability from risk to requirements. The path from the tier and risk assessment to the clauses should be visible, even if informal.
Handling of non-negotiable terms. Where a supplier would not accept your terms, they look for a recorded risk decision.
Incident and exit terms. Expect questions about notification obligations and what happens to your data at termination.
Version control. Signed copies, dates and renewal tracking show the agreements are managed rather than lost in mailboxes.
Common mistakes to avoid
One giant questionnaire as a substitute for a contract. Answers in a spreadsheet do not bind anyone. Put the commitments in the agreement.
Over-engineering for small suppliers. Heavy schedules for low-risk suppliers waste goodwill and time. Use the baseline pack.
No incident notification clause. Without it you may learn of a breach from the news. Name a contact and a timeframe.
Silent subcontracting. Your supplier’s supplier handles your data and you do not know who they are. Ask for notice and flow-down.
Ignoring auto-renewal. Agreements that roll over for years without review keep outdated terms. Diarize renewals.
Assuming legal has it covered. Contracts are often drafted without security input. Make sure someone responsible for security reviews the key ones.
How 27kay can help
We help organizations turn supplier expectations into short, practical requirement packs that legal and procurement teams can reuse. As part of ISO 27001 implementation, we review your critical agreements, identify the gaps and prepare the evidence an auditor will ask for. For the full picture, see our ISO 27001 knowledge hub.
If your most important supplier had a breach tomorrow, would your contract tell you what they must do? Get in touch - we will help you find out and fix it calmly.