Two proposals are on the desk. Both managed service providers promise 24/7 monitoring, a security operations center and enterprise-grade protection. One has a SOC 2 badge in its email signature. The CEO reading them is about to hand one of these companies administrative access to every computer, mailbox and backup the business owns, and nothing in either proposal is evidence. It’s adjectives. To evaluate an MSP’s security claims before you sign, ask for the documents behind the adjectives. This is the list.
Your provider’s security is your security
In May 2022, CISA, the NSA and the FBI issued a joint advisory with their counterparts in the United Kingdom, Australia, Canada and New Zealand on threats to managed service providers. Its core point: MSPs usually hold both trusted network connectivity and privileged access to customer systems, which is why attackers treat a vulnerable provider as a way into many companies at once. Verizon’s 2026 Data Breach Investigations Report found that breaches involving a third party now account for 48 percent of all breaches. IBM’s 2026 Cost of a Data Breach Report put the global average cost of a breach at $4.99 million, a record. When a provider’s technician account is compromised, the breach, the invoice and the notification letters are all yours.
Claims and evidence are different things
I run a managed services company, so I know how proposals get written. “Enterprise-grade” is not a control. “Compliant” is not a report. Evidence has three properties a claim doesn’t: a date, an author and a scope. I’ve made this argument in interviews; here is the list behind it.
The evidence list
- The full SOC 2 report, not the badge. A SOC 2 is a CPA firm’s examination of a provider’s controls for security, availability, processing integrity, confidentiality or privacy. Ask for the Type 2 report, which covers a period rather than a single date, and read the period, the systems in scope, the opinion and the exceptions. A provider without one should show a recent independent assessment and what it found.
- Proof that MFA is enforced on their own tools. The remote monitoring platform, ticketing system, documentation vault, email and backup console are the five systems an attacker wants most. Ask for a policy export showing MFA required on every account, and write it into the contract, as the joint advisory tells customers to do.
- How their people get into your network. Named accounts per technician, separate credentials per client, no shared admin login, no standing membership in your domain administrators group. Ask for the last access review and how fast a departed technician is removed from your systems. The identification and authentication questions I raised about AI agents apply to every human with a password to your environment.
- Logs you can see. Which logs are collected, how long they’re kept (the advisory says at least six months for the most important ones), who reviews them, and within how many hours the provider tells you about a suspected incident on its own infrastructure.
- A restore, not a backup. Everyone backs up. Ask for the date and duration of the last full test restore for a client your size, where the offline or immutable copy lives, and the recovery objectives in writing.
- Ninety days of patch reports. The 2026 DBIR found that 31 percent of breaches now begin with vulnerability exploitation, ahead of stolen credentials for the first time. Ask for a sample client’s patch report for the last quarter and the service level for critical patches, in days.
- The incident response plan and the last tabletop date. A plan that has never been exercised is a document. Ask when it was last tested and what changed.
- Their own cyber insurance certificate. Carrier, limits, and whether the policy responds to claims brought by clients. A provider that asks you to carry all the risk is telling you something.
- The subcontractor list. After-hours help desks, overseas engineering teams, the vendors behind their tools. The advisory asks customers to understand the supply chain risk tied to their MSP, and every name on that list has a path into your network.
- A contract that names who does what. Ownership of security roles in writing, breach notification in hours, a right to audit, and data return when you leave. If you hold controlled unclassified information for a defense contract, 32 CFR 170.19 puts your provider’s services inside your own CMMC assessment scope and calls for a customer responsibility matrix, so that matrix should exist before you sign.
What the answers tell you
Good providers aren’t offended by this list; most of it already sits in a folder because their insurer and auditor asked first. The red flags are consistent: a compliance claim with no report behind it, a shared admin account defended as efficiency, and the sentence “we’ve never had an incident,” which describes detection, not security. Send the list a week ahead and spend the meeting on two questions: walk me through the last incident you handled for any client, and show me how a technician’s access to my systems is removed on their last day. The answers, and how long it takes to find them, tell you more than the proposal did. If the proposal uses the words zero trust, here is what they should mean for a firm of fifty.
Frequently asked questions
Does an MSP need a SOC 2 report?
No law requires one for most private companies, but it’s the most common independent evidence that an outside CPA firm examined a provider’s controls. Without a SOC 2 report or ISO 27001 certificate, ask what independent assessment the provider has had, when, and what was found.
We hold CUI for a defense contract. Does our MSP need its own CMMC certificate?
Under 32 CFR 170.19, when a provider that is not a cloud service provider processes, stores or transmits CUI, its services are inside your CMMC assessment scope and are assessed as part of your assessment, documented in your System Security Plan and the provider’s customer responsibility matrix. The rule notes the provider may voluntarily seek its own certification to reduce the effort during yours.
What if our current provider can’t produce this evidence?
Give them 30 days and the written list. A provider that produces most of it is worth keeping and worth holding to the rest. One that can’t, or won’t, has answered the question. You now hold the evidence file your insurer, auditor and next acquirer will ask for.
If you’d like a second set of eyes on a proposal, my team at Stealth Technology Group runs this review inside our managed IT and security practice for mid-market companies in Tampa, Sarasota, Boston and Greater Philadelphia, and you can reach me directly here.
2 Responses