Before you sign with a managed service provider, get four things in writing: who owns each security task, what access the provider gets, how you can see their activity and how you can leave. Rankings can help you find names, but these answers decide whether a provider fits. As CISA puts it, "Outsourcing IT services does not absolve executives of risk management responsibilities."
What does a managed service provider take off your plate?
An MSP runs agreed parts of your IT for a recurring fee. That often means help desk, patching, monitoring, backups and account administration. The word that matters is agreed. Anything not written down is likely to stay with you, even if you assumed otherwise.
So start with your own list before you talk to anyone. Write down your critical systems, who uses them, where the data sits and what a day of downtime would cost you. CISA suggests the same starting point: know your most critical assets and how they are protected. A provider cannot price or protect what you have not described.
Also check whether outsourcing still saves money once security is included. A low monthly fee can look different after you add the security work the base plan leaves out.
Who owns each security task?
This is the question that prevents the worst surprises. NSA and CISA describe cloud security as a shared responsibility, and the same thinking applies to outsourced IT. Some tasks belong to the provider, some to you and some to both.
Ask for a responsibility matrix. The ND-ISAC MSP questionnaire, written to help small and midsize businesses vet providers, includes an example and asks whether the MSP has one. Ours would need one line for each of these:
- Patching servers, laptops and business applications
- Reviewing security alerts, including nights and weekends
- Testing backup restores, not just running backups
- Creating and removing user accounts when staff join or leave
- Leading the response during an incident
If a provider cannot show who does what, treat that as your answer. A named owner for every line is the minimum.
How much access should the provider get?
Less than most providers ask for by default. An MSP usually holds privileged access to many customers at once, which makes it an attractive target. CISA advises least privilege: the minimum rights for the shortest time needed. It also advises agreeing privilege levels before the contract is awarded and reviewing them regularly.
In practice, we would ask for these controls:
- Named accounts for each technician, with no shared logins
- Multi-factor authentication on every administrator and remote access path
- Access granted when needed and removed after, where the tools allow it
- MSP accounts limited to the systems that provider actually manages
The same discipline applies to any tool you connect to core systems. Our guide on checking AI connector permissions in a CRM uses the same logic for a different kind of access.
Can you see what the provider does?
You should be able to, without asking permission. CISA advises customers to require records of when accounts are accessed, by whom and what was done. It also advises getting direct access to security logs from the systems the provider manages, and keeping your own offsite backups and activity logs.
NSA and CISA add that customers should choose providers that offer visibility into their work in your environment, protect critical logs from tampering and set alerts for unusual activity.
Test this before you sign. Ask the provider to show you a sample report and explain how you would get raw logs on a bad day. If the only answer is a monthly summary PDF, you will be relying on their account of events during an incident.
What should the contract say?
A sales deck is not an obligation. CISA's list of terms to request is a practical starting point, and we would have counsel review the final version. Look for:
- Service levels that treat operations and security separately
- Incident handling, how fast you are told and what happens after an outage
- How your data is kept apart from other customers' data
- Staff vetting, and notice of any subcontractors
- A transition plan, plus your input on maintenance windows
Then ask about insurance and business history, as the ND-ISAC list does. Check cyber coverage limits, ask for references and ask whether ownership has changed in the past year. Those facts tell you how the provider is likely to hold up under pressure.
How do you leave if it goes wrong?
Plan the exit while everyone is friendly. The ND-ISAC list asks about offboarding, data retention and how data is destroyed. We would add four questions of our own:
- Who holds the administrator credentials and domain registrations?
- Are licenses in your name or the provider's?
- Will documentation and network diagrams be handed over in a usable form?
- How much notice and help do you get during a handover?
We wrote more on this in our handover test for outsourced applications. The short version: if your team could not take over with what is written down today, you do not have an exit yet. Fix that early, because it gets harder and more expensive later.
Should you start from a top 10 list?
Use lists to find names, not to decide. A ranking cannot know your systems, your compliance duties or how much risk you can accept. Two providers that look alike on a list can differ a great deal on who answers an alert at 2 a.m.
A better method is to shortlist three providers and send each the same written questions. Compare the answers side by side, and give extra weight to specific answers backed by a sample document. Vague answers at the sales stage rarely get more precise once you are a customer.
Frequently asked questions
An MSP mainly runs IT operations such as support, patching and backups. An MSSP focuses on security services such as monitoring and threat response. Many firms offer both, so read the scope rather than the label.
No. The provider takes on tasks, but your business still answers for its own risk decisions and its data. CISA says this plainly in its guidance for MSP customers, which is why oversight and logs still matter after you sign.
Ask where your data lives, who can access it and how that access is tracked. Then ask for a responsibility matrix. Those answers show quickly whether the provider has thought through your setup.
Hold a business and security review on a set schedule, and review MSP accounts and privileges regularly. Quarterly is a reasonable starting point for many companies, with an extra review after any incident or major system change.
Sources
- CISA: Risk Considerations for Managed Service Provider Customers (2021)
- NSA and CISA: Mitigate Risks from Managed Service Providers in Cloud Environments (2024)
- ND-ISAC: MSP Shopping Questionnaire (revised August 2025)
Is your MSP leaving gaps between your systems?
We build the integrations and automations that connect your business systems, so access, records and handoffs stay clear whoever runs your IT.
See API integration services
