Supplier risk: which suppliers could hurt you most, and how fast could you cut them off?

This quarter, list every supplier that holds admin access, tokens or a copy of your critical data, and make sure you can cut off each one's access within an hour. Then focus on that top tier: read their audit reports instead of sending questionnaires, fix the contract at renewal and plan for a week without them.

Reviewed
Next review
Version
1.1
Written for
IT, security, procurement and compliance leads in EU organizations, especially in Germany

If you only do five things

  1. List the suppliers that can reach your systems or data.

    Record each supplier with admin rights, remote access, API or OAuth tokens, or a copy of critical data, with an owner and a contact. Verizon found third-party involvement, including exploited vendor flaws, in 48% of breaches in its 2026 report, up from 30%1.

  2. Be able to cut any supplier off within an hour.

    For each top-tier supplier, write down how to disable its accounts, revoke its tokens and stop its remote access tool, and test it. Attackers used compromised Salesloft Drift tokens to export Salesforce data from 8 to at least 18 August 20252.

  3. Ask the top tier for audit reports, not questionnaires.

    Request the current SOC 2 Type 2 or BSI C5 report and read its scope, period and exceptions. Type 2 tests whether controls worked over time; Type 1 only checks their design3.

  4. Add five clauses at each renewal.

    Incident notice, vulnerability handling, audit rights, subcontractor rules, and exit with data return. NIS2's implementing rules make cloud providers and MSPs demand all five from their suppliers, where appropriate4.

  5. Plan for a week without each critical supplier.

    Decide how the business keeps running and keep your data exportable. In October 2025, a DynamoDB fault in one AWS region caused 14.5 hours of disruption that spread to EC2 and Lambda5.

Decide a supplier's tier

  1. Can it act inside your systems?

    Admin accounts, an RMM agent, a VPN account or an app with broad API scopes put a supplier in the top tier, whatever the contract is worth. An attacker who compromises an MSP can reach many of its customers' networks and data6.

  2. Does it hold data you must protect?

    Count personal, financial and confidential data, and the secrets hidden in it: the Drift attackers searched stolen Salesforce records for AWS keys, passwords and Snowflake tokens2.

  3. What stops if it is down for a week?

    If a critical process stops, the supplier is top tier even without any access to your systems.

  4. How hard is it to replace?

    A supplier you can't swap within weeks needs an exit plan and a tested data export. DORA makes financial entities weigh providers that are not easily substitutable as concentration risk7.

  5. Record the tier and review it.

    One yes answer makes a supplier top tier. Review tiers at least yearly and after significant changes, as ENISA advises8.

What to ask for and what to sign

  • Read the audit report, not the logo. Check that it covers your service, is current and tests whether key controls operate, as DORA requires for critical or important functions9. Get every later C5 report and run the customer controls it assigns you3.
  • Ask about the product, not just the company. CISA and the FBI suggest asking whether SSO and MFA come at no extra cost and whether SaaS security logs are kept for at least six months at no additional charge10.
  • Incident notice within hours. Require notice of incidents that put your systems at risk4 within a fixed time, such as 24 hours, or sooner if your own reporting clock is shorter. The GDPR sets processors no fixed deadline, so the EDPB suggests contracts require early notice12.
  • Vulnerabilities and audits. Require vulnerability handling and audits or audit reports4, and patches within the patching sheet's deadlines.
  • Subcontractors. Require the same security terms for subcontractors4 and notice of material changes with a right to object, as DORA requires for critical functions13.
  • Exit and data return. Require your data back in an easily accessible format on termination or insolvency, a transition period and incident help at a preset cost7. Remove supplier accounts and data flows at exit8.

Limit what suppliers can reach

  • Give MSP staff named accounts with MFA. Keep them out of internal admin groups, limit them to the systems the MSP manages and disable them when not in use14. No admin credential should serve several customers6.
  • Allow one remote access tool. Allowlist the approved RMM tool, block the ports of others and keep log deletion out of its reach6. In 2025, ransomware actors exploited unpatched SimpleHelp RMM to compromise a billing software provider's customers15.
  • Take Global Administrator away from Microsoft partners. Under Settings > Partner relationships, remove partner roles you don't need and ask for least-privilege GDAP roles16. Review them quarterly.
  • Limit OAuth consent. In Entra ID, let users consent only to verified publishers' apps for low-impact permissions, and send other requests to the admin consent workflow17. Give integrations the narrowest scopes and avoid Salesforce's full2.
  • Watch supplier activity. Alert on sign-ins by supplier accounts, new app consents and new RMM agents, and keep those logs for 12 months, as the logging sheet recommends.

When a supplier is breached

  1. Cut its access, then rotate.

    Using your supplier list, disable its accounts and apps, revoke its tokens2 and isolate its remote access server15. Replace keys and secrets tied to it or found in data it held2.

  2. Hunt in your own logs.

    Review sign-ins, API calls and queries by its accounts and apps from before the disclosure2.

  3. Which clocks have started?

    For personal data it processed for you, the GDPR's 72 hours generally start when it tells you12. The EU security laws sheet has the other clocks.

What changed in 2026

  • Manufacturers must now warn you about exploited flaws. Since 11 September 2026, the CRA requires makers of software and connected devices, but not of standalone SaaS, to tell impacted users about actively exploited vulnerabilities and severe incidents, also for products already on the market19. Give key vendors a monitored security contact.
  • Integration token theft hit another SaaS vendor. In June 2026, an attacker used a stolen GitHub token to plant code in Klue's integration service and collect customers' Salesforce OAuth tokens20.
  • The BSI published C5:2026. Final since March 202618, it has 168 criteria instead of 121 and applies to attestations from 1 June 20273. Ask cloud suppliers when their first report is due.

What you can skip

  • Your own 300-question questionnaire. Send low tiers a one-page form, or take the supplier's completed SIG or CAIQ, which ENISA names as evidence8.
  • Custom terms with hyperscalers. Compare their standard terms and audit reports with your clauses and record the gaps. ENISA suggests negotiating jointly8; DORA allows pooled audits9.
  • Mapping every fourth party. NIS2 and the BSIG address direct suppliers21; DORA adds subcontractors behind critical or important functions13. Ask the top tier which subcontractors touch your data.
  • A security rating feed before a supplier list. No outside score tells you who holds admin rights in your tenant.

Mistakes that cost the most

  • Assuming outsourcing moves the duty. The BSI says NIS-2 entities that outsource all IT remain responsible and that contracts alone aren't enough21. DORA keeps financial entities fully responsible too7.
  • Leaving access behind when a contract ends. CISA and partners note that disabling MSP accounts can be overlooked then14. Revoke its tokens too.
  • Tightening consent without cleanup. New Entra consent settings leave existing grants in place17. Revoke the ones you don't need.
  • Letting your MSP hold your only backups. One breach of its accounts then reaches both. Keep a copy it can't delete.

What this looks like at your size

Small team, no security staff

  • Require least privilege and 2-step verification on your IT provider's accounts11, and get a list of them.
  • Remove Global Administrator from Microsoft partners under Settings > Partner relationships16.
  • Agree how fast your provider reports incidents and ask for regular health reports11.

Growing, with IT or security staff

  • Keep the supplier list with tier, owner, access, data, contacts and contract dates, and review it yearly8.
  • Turn on the Entra admin consent workflow17 and review app permissions every quarter.
  • Write a one-page cut-off runbook per top-tier supplier and rehearse one each quarter.

Enterprise or regulated

  • Under DORA, keep the register of information and test exit plans for critical or important functions7.
  • Join pooled audits9 and include key suppliers in crisis exercises8.
  • Map which top-tier suppliers share a cloud region or subcontractor, and plan for that failure.