ISO 27001 Control A.5.19: Information Security in Supplier Relationships
Very few organizations run on their own systems alone. Cloud platforms host your data, payroll providers hold employee records, developers work through external tools, and cleaners have keys to your office. Each of these suppliers extends the reach of your information security risks beyond your own walls, and you remain accountable for what happens. A.5.19 starts a group of four supplier controls in Annex A, and it is the 19th of 37 organizational controls in the series.
This control is the foundation: before you can write contracts, monitor services or manage a supply chain, you need a clear picture of who your suppliers are, what they can touch and how much risk that represents. The effort should follow the risk. A supplier of office plants is not the same as a provider of your customer database.
What the control requires
Annex A control 5.19 of ISO 27001:2022 states that processes and procedures shall be defined and implemented to manage the information security risks associated with the use of supplier’s products or services.
The key elements:
- Processes and procedures - a repeatable approach to choosing, onboarding, managing and ending supplier relationships, not a one-off questionnaire
- Defined and implemented - written down and actually used for real suppliers
- Information security risks - the risks to your information from a supplier’s access, handling or failure
- Supplier’s products or services - covering software, cloud services, outsourced functions, consultants, contractors and physical services alike
A.5.19 is a preventive control in ISO/IEC 27002:2022. Annex A states the control; ISO 27002 gives guidance, including identifying and documenting the types of supplier that can affect your information security, a standard way of evaluating suppliers, minimum requirements for each type, and handling the incidents and contingencies that involve suppliers. It also encourages awareness among your own staff about how they deal with suppliers. The following controls in the series, covering agreements, the ICT supply chain and monitoring, build on this base.
How to implement supplier information security
Build a supplier register
Start with a list. Pull together everyone who supplies you with anything that touches information or the systems that hold it: finance and procurement records, the cloud accounts on your credit card, the applications your teams adopted without telling anyone. For each supplier, note what they provide, what information or systems they access, who in your organization owns the relationship and when the contract renews.
The register is the backbone of the process and the first thing auditors ask for. It also reveals “shadow” suppliers, which are services adopted by teams without review. A good approach is to ask each team lead to list the tools and external parties they rely on, then compare with finance records. Add a simple rule that no new supplier handling non-public information is engaged without a short review. This connects to the inventory of information and other associated assets, where supplier-hosted systems also belong.
Tier suppliers by risk
Not every supplier deserves the same scrutiny. A simple tiering model keeps the work manageable:
- High - suppliers who host or process confidential or personal information, have privileged access to your systems or whose failure would stop the business
- Medium - suppliers with limited access to internal information or whose services support important but replaceable functions
- Low - suppliers with no access to information or systems
Use your risk assessment approach and your classification of information to assign tiers. Then match the due diligence to the tier. High-risk suppliers might need a security questionnaire, evidence such as an ISO 27001 certificate or a SOC 2 report (read it, including the scope and exceptions), and a review of their subcontractors. Low-risk suppliers might need nothing beyond the register entry. Be careful with certificates: a certificate shows that a management system was assessed against a scope, not that every service you use is within it, so check the scope against what you are buying.
Define minimum requirements and a standard process
Write down what you expect from suppliers at each tier, such as how they protect your data, how they report incidents, where information is stored and how it is returned or deleted at the end. Turn the expectations into a standard onboarding step: request, risk review, approval, contract, access set-up. Build in the information exchange rules from information transfer and limit supplier access according to access control and access rights, with end dates for accounts.
Include individuals working for suppliers on your premises. They should be covered by confidentiality or non-disclosure agreements and the on-site rules for secure areas, and equipment they bring or take away follows your rules for security of assets off-premises.
Plan for supplier failure and exit
Ask what happens if a key supplier suffers an incident, goes out of business or raises its prices beyond reach. For high-tier suppliers, note the alternatives, the way to export your data and the person who decides. Agree how the supplier will tell you about incidents and how you will tell them. At the end of the relationship, make sure access is removed, assets are returned and information is returned or deleted, and keep the evidence. Check any data protection obligations with your privacy adviser, since terms for handling personal data on your behalf vary by jurisdiction.
Keep the tone of all this collaborative. Most suppliers are used to security questions and respond well to clear, proportionate ones. If you ask for something unusual, explain why. Suppliers who treat your questions seriously are usually the ones you want to keep, and those who dodge them tell you something too. Share what you learn internally, so that the next team choosing a similar tool does not start from zero.
Related controls and clauses
A.5.9 connection. The inventory of information and other associated assets should include assets held by suppliers.
A.5.14 connection. Information transfer defines how information moves to and from suppliers.
A.5.15 and A.5.18 connection. Access control and access rights govern supplier access, which should be time-limited and reviewed.
A.6.6 connection. Confidentiality or non-disclosure agreements bind supplier staff who see your information.
Clause 4.2 connection. Clause 4.2, Understanding the needs and expectations of interested parties, lists suppliers among the parties whose requirements you consider.
Clause 6.1 connection. Clause 6.1, Actions to address risks and opportunities, is where supplier risks are assessed and treated.
Forward reference. Addressing information security within supplier agreements (A.5.20), managing information security in the ICT supply chain (A.5.21) and monitoring, review and change management of supplier services (A.5.22) complete the group over the next few posts.
What auditors check
A supplier register. Auditors ask for the list of suppliers, your tiering and how you decided which suppliers matter.
Risk-based due diligence. They sample high-risk suppliers and look for evidence of evaluation before engagement, such as questionnaires, reports and review notes.
A defined process. They check that onboarding steps exist and that recent suppliers went through them, including approval before access was granted.
Supplier access. Expect questions about who from suppliers has access, how it is approved and when it ends.
Exit arrangements. They may ask what happened to access and data when a supplier was last replaced.
Staff awareness. Interviews with procurement and team leads show whether the process is known and followed or bypassed.
Common mistakes to avoid
Treating all suppliers alike. Sending a long questionnaire to every vendor wastes effort and buries the important ones. Tier them.
Relying on a certificate alone. Check scope, date and exceptions. A certificate for one product line says little about another service.
Shadow IT. Teams adopt tools with a credit card and nobody reviews them. Compare the register with finance records regularly.
No owner on your side. Every supplier needs a named person responsible for the relationship, otherwise no one notices changes.
Forgetting exit. Many organizations plan onboarding carefully and never think about getting data back. Ask about it at the start.
One-time assessment. Supplier risk changes. A review done at signing and never again will not hold up, which is why monitoring matters.
How 27kay can help
We help organizations build supplier management that is proportionate, so you spend your time on the few suppliers that matter. As part of ISO 27001 implementation, we create the register and tiering with you, design lightweight due diligence and prepare the evidence an auditor will ask for. For the full picture, see our ISO 27001 knowledge hub.
Do you know which three suppliers could do you the most damage if something went wrong? Get in touch - we will help you find them and decide what to do about it.