A.5 Organizational controls

A.5.22 Monitoring, review and change management of supplier services

Not mandatory by default – decided in your SoA

What it means in plain language

Monitor and review supplier security performance over time and manage changes to their services.

Is it mandatory? Not automatically. You must consider this control in your Statement of Applicability (6.1.3 d). Include it if your risk assessment, laws, contracts or business needs require it; if you exclude it, write down a justification an auditor will accept.

Why this control matters

The operational priority is what happens after onboarding: how the organization keeps watch on supplier security performance, verifies continuing suitability, and reacts to service changes that alter risk. Practitioners need to distinguish routine service management from security-specific review, showing where performance data, contractual triggers, and re-assessment points belong.

Common auditor findings to check for

Potential gaps to test in your own environment, not a claim about observed audit frequency.

  • Supplier performance is reviewed for cost and uptime, but security metrics, incident history, or certificate expiry are not checked against the agreed risk treatment.
  • A supplier changes hosting region, support model, ownership, or subcontractors, yet no formal security re-assessment is opened before the change is accepted.
  • The Supplier Register exists, but entries are stale, missing review dates, change notices, evidence links, or escalation decisions for critical services.

How you can implement it

Tools and review intervals are examples; choose them according to risk, obligations and your operating environment.

  • Maintain a live Supplier Register owned by procurement or vendor management, with security fields for service criticality, data handled, contract end date, attestations, incidents, SLA breaches, and next review date. Security should define the review triggers, but service owners must validate whether the supplier still meets operational and control expectations.
  • Set an illustrative review cadence by criticality: more frequent for high-risk or regulated suppliers, and lighter for low-risk services. Review certificates, penetration-test summaries where provided, support-ticket trends, incident reports, and material changes to architecture, location, or subcontractors. Record whether the review confirms continued acceptance or opens a remediation action.
  • Treat supplier change notices as security events when they affect hosting, identity federation, encryption, logging, support access, or data location. Require a named risk owner to assess whether the change alters the original approval basis. If the supplier cannot explain the change or provide evidence, escalate to contract management, legal, and business continuity owners.
  • Link monitoring outputs to management review and corrective action so repeated supplier issues are visible at governance level. Use action owners and due dates for overdue attestations, unresolved incidents, or expired assessments. Where appropriate, suspend privileged integrations or restrict data sharing until the supplier re-establishes acceptable security posture.

What an auditor will ask to see

  • Supplier Register entries showing review dates, certificates checked, incidents logged, and named risk owners.
  • Change notices from suppliers with documented impact assessments and approval or escalation decisions.
  • Meeting notes or dashboards summarizing SLA breaches, security incidents, and remediation commitments for key suppliers.
  • Action tracker items for overdue evidence, failed reviews, or temporary service restrictions pending re-assessment.

Baseline documents in the kit

These free kit documents help you document or evidence A.5.22. Each one is tailored to your organization when you build your kit.

Connect this work to your ISMS

Review the dependencies with A.5.19 — Information security in supplier relationships and A.5.31 — Legal, statutory, regulatory and contractual requirements. Keep the ownership and evidence consistent across these activities.

NIS2 and ISO/IEC 27001: reuse controls and check legal gaps for the wider implementation context.

Use the SIG and CAIQ questionnaire accelerator to find supporting documents. A mapping is a starting point: verify your actual operating evidence before answering a buyer.

For help adapting this to your environment, explore ISO/IEC 27001 consulting, starting with a free one-hour consultation.

Get these documents tailored to your organization

109 ready-to-edit documents, including all 19 mandatory ones, tailored from a short scoping questionnaire and linked to your risk register and SoA.

Start free

Plain-language interpretation by an ISO/IEC 27001 lead implementer, not the official text of ISO/IEC 27001:2022.