ISO 27001 Control A.5.22: Monitoring, Review and Change Management of Supplier Services
Choosing a good supplier and signing a sound contract is only the beginning. Over the following months and years, the supplier changes its staff, its platform, its subcontractors and perhaps its owner, and so do you. If nobody is watching, the assurance you gathered at the start slowly goes stale. A.5.22 is the control that keeps supplier oversight alive. It is the 22nd of 37 organizational controls in our walk through Annex A, and it closes the supplier group that began with A.5.19.
Many organizations do the first half of the supplier life cycle diligently and the second half barely at all. The good news is that monitoring does not need to be heavy. It needs to be regular, risk-based and recorded.
What the control requires
Annex A control 5.22 of ISO 27001:2022 states that the organization shall regularly monitor, review, evaluate and manage change in supplier information security practices and service delivery.
The key elements:
- Regularly - on a defined schedule, not only after something goes wrong
- Monitor, review, evaluate - collecting information about how the supplier performs, examining it and judging whether it is still acceptable
- Manage change - controlling changes to the supplier’s services, to your agreements and to the supplier’s own practices
- Information security practices and service delivery - both how securely the supplier works and whether it delivers what was agreed
In ISO/IEC 27002:2022, A.5.22 is attributed as both a preventive and a detective control, because reviewing suppliers can prevent problems and also reveal ones that have already begun. Annex A states the control; ISO 27002 gives guidance, including monitoring service performance levels, reviewing supplier reports and audit evidence, handling incidents and problems that involve the supplier, checking that the supplier maintains its own supplier management, and making sure that a person on your side is responsible for each relationship.
How to implement supplier monitoring and review
Set a review rhythm that matches the tier
The risk tiers from information security in supplier relationships tell you how often to look. A reasonable starting pattern is:
- High-risk suppliers - reviewed at least annually, with regular service meetings and a check after any significant change or incident
- Medium-risk suppliers - reviewed annually or at renewal, using a lighter checklist
- Low-risk suppliers - a light check at renewal, or when something visibly changes
Put the schedule in a shared calendar owned by someone, usually the relationship owner with support from security. A schedule that only exists in a policy will not run itself.
Decide what to look at
A review should be a short list of concrete questions, not an essay. Useful sources include:
- Service performance - availability, response times, support tickets and any breaches of agreed service levels
- Security assurance - new certificates or audit reports (check the scope and any exceptions), penetration test summaries and answers to a refreshed questionnaire
- Incidents - notifications the supplier sent you, and whether they were timely and complete, against the terms in addressing information security within supplier agreements
- Changes on the supplier side - new subprocessors, changes of hosting location, acquisition, major product changes or staffing changes in the team supporting you
- Access - the accounts and permissions the supplier holds, reconciled against access rights and removed where no longer needed
- Public information - news of breaches or vulnerabilities in their products, which is easy to check and surprisingly often skipped
Record the answers, the conclusions and any actions in the supplier file. Short meeting notes are fine.
Manage change on both sides
Changes can come from the supplier, such as a new version or a move to a different data center, or from you, such as using the service for more sensitive data than before. Either can alter the risk. Require suppliers, by contract, to notify you of relevant changes in advance, and define an internal step to assess them: does this change affect the security requirements, the tier or our own configuration? If the answer is yes, update the risk record and, if needed, the agreement.
Do the same for your own changes. When a team starts sending personal or confidential data to a tool that was approved only for low-risk use, that is a change in the relationship even though the supplier did nothing. Your change management approach for the ISMS, covered in clause 6.3, can cover such decisions.
Act on what you find
Monitoring only has value if it leads to action. Agree what happens when a review reveals a shortfall: ask the supplier for a remediation plan with dates, compensate with your own controls, reduce what you share with them or, as a last resort, plan an exit. Escalate repeated or serious problems to management, and make supplier performance an input to your management review. When a supplier relationship ends, close it properly: remove access, retrieve information and assets, and confirm deletion. Where a supplier incident occurs, handle it through your normal information security event reporting and incident routes, and use it to refresh your assessment.
A practical tip: attach a short review template to every high-risk supplier file, with the same eight or ten questions each year. Consistent questions make trends visible, such as slowly worsening response times or a rising number of subprocessors, and they save the reviewer from starting with a blank page. Where a supplier shares its own audit reports, agree that you will treat them as confidential and store them with restricted access, in line with your classification rules, so the supplier is comfortable sharing again next year.
Related controls and clauses
A.5.19 connection. Information security in supplier relationships provides the register and tiers that drive review frequency.
A.5.20 connection. Addressing information security within supplier agreements sets the obligations you are monitoring against.
A.5.21 connection. Managing information security in the ICT supply chain is why reviews should include subprocessors and upstream dependencies.
A.5.18 connection. Access rights reviews should include accounts held by suppliers.
Clause 9.1 connection. Clause 9.1, Monitoring, measurement, analysis and evaluation, expects you to evaluate how well your controls perform, and supplier review results are good evidence.
Clause 9.2 connection. Clause 9.2, Internal audit, can include supplier management in its scope.
Clause 9.3 connection. Clause 9.3, Management review, is the natural forum for escalating significant supplier issues.
Forward reference. Information security for use of cloud services (A.5.23) applies these ideas to one of the most common and important kinds of supplier.
What auditors check
Evidence of reviews. Auditors ask for the most recent review records for several key suppliers, including who performed them, what was examined and what was concluded.
A review schedule. They look for a defined frequency tied to risk, and test whether it was met.
Handling of supplier changes. Expect questions about the last time a supplier changed something relevant and how you found out and responded.
Service delivery records. For critical suppliers, they check service reports, incident records and any service level breaches with follow-up.
Follow-up actions. They look for issues found in reviews and evidence that they were tracked to completion.
Offboarding. They may sample a supplier that left and check that access was removed and information returned or deleted.
Common mistakes to avoid
Onboarding diligence only. An assessment from three years ago is not monitoring. Schedule recurring reviews.
Reviews with no outcomes. If every review concludes “no issues” without evidence, an auditor will doubt it was real. Record what you checked.
Nobody owns the relationship. Without a named owner, the review calendar goes unused. Assign one per supplier.
Ignoring your own changes. The risk may rise because you started sending more sensitive data, not because the supplier changed.
Missing the quiet changes. New subprocessors and hosting moves are often announced by email to an inbox nobody reads. Subscribe a shared address and check it.
Skipping offboarding. Dormant supplier accounts and data left behind create risk long after the contract ends.
How 27kay can help
We help organizations set up supplier reviews that take minutes for the few suppliers who matter and nothing for the rest. As part of ISO 27001 implementation, we build the review calendar and checklists with you, run the first round together and prepare the evidence an auditor will ask for. For the full picture, see our ISO 27001 knowledge hub.
When did you last check whether your most important supplier is still as good as the day you signed? Get in touch - we will help you make that a routine rather than a surprise.