Managed service provider security review of an IT team working at their desks

June 19, 2026 | Risk Management

Securing Managed Service Providers (MSPs): Protecting Your Supply Chain

Your MSP holds the keys to your environment. Learn the managed service provider security questions to ask and the standards to demand.

A managed service provider (MSP) usually holds more access to your environment than any single employee. It runs your endpoints, administers your cloud tenants, manages your backups and often sits behind your help desk. If an attacker compromises the MSP, the attacker inherits that access, and your own controls may never get a chance to react.

That makes MSP security a supply chain problem, not just a procurement detail. You remain accountable to regulators, customers and auditors for what happens to your data, even when someone else's staff and tools touch it. This article covers what to ask, which standards carry weight, and how to structure the relationship so the risk stays visible.

Why MSPs are a concentrated risk

Most MSPs run a small number of management tools across many customers. Remote monitoring agents, remote access software and shared administrative accounts are efficient for the provider. They also mean one stolen credential or one compromised tool can reach many customer environments at once. Attackers know this, which is why service providers are a recurring target.

Three features make the risk different from an ordinary software vendor:

  • Privileged access. MSP technicians often hold domain administrator or global administrator rights.
  • Persistent connectivity. Agents and remote tools stay connected around the clock, so there is no moment when the access is "off".
  • Delegated trust. Your security team usually treats MSP traffic as legitimate, so malicious activity can blend in.

Ask these questions before you sign

A security questionnaire is a starting point, but the answers matter more than the form. Push for specifics on the following.

Access and identity

  • Is multi-factor authentication enforced for every technician, including on the remote management tools?
  • Do technicians use named accounts, or shared credentials? Shared accounts make it impossible to tell who did what.
  • Is privileged access granted just in time, and who approves it?
  • How quickly is access removed when a technician leaves or changes role?

Segregation of customers

  • Is your environment managed with credentials that are unique to you, or does one credential span many customers?
  • How does the MSP separate customer data in its own tooling, ticketing and backups?

Monitoring and response

  • Does the MSP log and review administrative activity in your environment, and can you get those logs?
  • What is the contractual timeline for telling you about a security incident that affects your data or access?
  • When did the MSP last test its own incident response plan?

Their own supply chain

  • Which subcontractors and software providers does the MSP depend on to deliver your service?
  • Will the MSP notify you before it adds a subprocessor that touches your data?

Standards and reports worth asking for

Independent evidence beats self-description. Ask for the following, and read them rather than filing them.

  • A SOC 2 report. This is an attestation report issued by an independent CPA firm, not a certification. A Type II report covers how controls operated over a period of time. Check the scope: it must cover the services and systems that actually serve you, and any exceptions noted by the auditor deserve a follow-up conversation.
  • ISO/IEC 27001 certification. Ask for the certificate and the Statement of Applicability, which shows which controls are in scope.
  • Penetration test summaries. A recent test of the MSP's own environment and management tooling tells you more than a policy document.
  • Sector-specific evidence. If the MSP touches protected health information, HIPAA requires a business associate agreement. If it touches cardholder data, PCI DSS requires you to manage service providers and understand which requirements they cover and which remain yours.

For defense contractors, the question is sharper. An external service provider that handles controlled unclassified information, or that provides security protection for systems that do, can fall inside the scope of your CMMC assessment. Confirm this early, because it affects what the MSP must demonstrate and what you must document. Our CMMC readiness page explains how scoping works in practice.

Financial entities in the EU face additional expectations under DORA, which has applied since January 17, 2025. It treats ICT service providers as a managed risk, with contractual requirements and exit planning. If that applies to you, your MSP contract needs to reflect it.

Write the controls into the contract

Good answers in a sales call mean little if the contract is silent. Work with counsel to make sure the agreement covers:

  • Minimum security requirements, including MFA, logging and privileged access controls.
  • Incident notification within a defined number of hours, and the information the MSP must provide.
  • Your right to receive current audit reports and, where appropriate, to audit the MSP.
  • Flow-down of the same requirements to subcontractors.
  • Data return and deletion at the end of the relationship, with written confirmation.
  • Cooperation with your regulators, auditors and customers when they ask questions about the service.

Keep the relationship under review

An MSP review done once at signing goes stale. Treat your provider as a tiered vendor with a review schedule that matches its access. At a minimum:

  • Collect updated audit reports each year and read the changes.
  • Review the list of MSP accounts in your environment every quarter and remove any you cannot justify.
  • Log and alert on administrative actions by MSP accounts, using your own tooling, not only theirs.
  • Include the MSP in your incident response exercises so both sides know who calls whom.

Also plan for the day the relationship ends or the MSP is compromised. Keep an independent record of your environment, such as asset inventories and configuration baselines, and keep at least one set of administrative credentials that you control. If everything depends on the provider, you cannot recover without them.

Where to start

  1. List every provider with administrative access to your systems, including ones that were set up years ago and forgotten.
  2. Check MFA and named accounts for every MSP technician login, starting with your most critical systems.
  3. Request current independent evidence, such as a SOC 2 report or ISO/IEC 27001 certificate, and confirm its scope matches your services.
  4. Review the contract for incident notification, subcontractor flow-down and data return terms, and fix the gaps at renewal or sooner.
  5. Run a joint incident exercise so you learn how the provider behaves under pressure before you need it to.

If you want a second set of eyes on your provider relationships, our due diligence team can help, or get in touch.

Written By: Ken Pomella