Choose a managed IT and security provider on five things: the strength of its own security, service levels written into the contract, clarity about who does the fixing, reporting that shows you real risk, and exit terms that let you leave cleanly. A long list of services matters far less than how well those five are handled.
A managed provider will hold privileged access to your email, devices, cloud services and data. That makes it one of the most important suppliers you will appoint, and one of the most attractive targets for attackers. This article gives you criteria you can use with any provider, including us.
Executive Summary & Key Takeaways
- Start with the provider’s own security. It holds the keys to your systems, so its weaknesses become yours.
- Get response times, resolution targets and incident notification in writing, with a clear split of responsibilities.
- Ask who actually does the remediation work, and whether security fixes are included or charged separately.
- Good reporting shows risk and progress, not just ticket counts.
- Agree exit terms before you sign: data, credentials and documentation should come back to you in a usable form.
1. The provider’s own security
Your provider’s access is a route into your organisation. The government’s factsheet on the Cyber Security and Resilience Bill notes that providers’ widespread and trusted access to client networks has made them an increasingly attractive target, with a “one to many” impact when one is compromised (Relevant managed service providers factsheet, DCMS and DSIT, retrieved 10 November 2026).
The NCSC’s guidance for SMEs recommends using providers with recognised certifications such as Cyber Essentials Plus, and notes that ISO 27001 or SOC 2 also show an organisation takes information security seriously (NCSC: Choosing a managed service provider, retrieved 10 November 2026). Certificates are a starting point, not proof. Ask:
- Which certifications do you hold, what is in scope, and can we see current evidence?
- How do your engineers access our systems? Is multi-factor authentication enforced on every account that can reach us?
- Do your staff have standing admin rights to our environment, or is access granted when needed and logged?
- Will you tell us, contractually, if you suffer an incident that could affect us?
- Do you use subcontractors or offshore staff to deliver any part of the service?
The NCSC specifically advises applying least privilege to provider access and enforcing two-step verification on it (NCSC: Choosing a managed service provider, retrieved 10 November 2026). A provider that resists these questions is telling you something.
2. Service levels you can hold them to
Service level agreements (SLAs) turn promises into obligations. As a benchmark, the NCSC’s guidance describes a response time of one business day as standard for general requests and under one hour for urgent issues, with two to three business days a reasonable starting point for resolving routine medium-priority problems. It also notes that faster response times will usually cost more (NCSC: Choosing a managed service provider, retrieved 10 November 2026).
Look beyond the headline numbers:
- Response versus resolution. A fast acknowledgement means little if fixing the problem has no target.
- Security incidents. How quickly will they tell you about a suspected breach, and what happens in the first hours?
- Patching. The NCSC recommends patching critical and high-risk vulnerabilities within 14 days of an update being released (NCSC: Choosing a managed service provider, retrieved 10 November 2026). Ask whether that is in the contract.
- Hours of cover. “24/7” can mean a monitored queue, an on-call engineer or an automated alert. Ask which.
- Service credits. What happens when targets are missed, and how is performance reported?
3. Who does the fixing
This is the question that most often separates providers, and the one buyers forget to ask. Many services detect and report problems well, but leave the remediation to you or charge for it as extra project work.
Ask the provider to walk you through a realistic example: a critical vulnerability on a firewall, a compromised mailbox or a laptop that has stopped receiving updates. Who notices? Who fixes it? Is it covered by the monthly fee? How long does it take?
The NCSC recommends a responsibility matrix that sets out what the provider does and what is expected of you (NCSC: Choosing a managed service provider, retrieved 10 November 2026). Insist on one. It should also cover end-of-life systems: someone needs to track when products stop receiving security updates and plan their replacement, and the contract should say who.
4. Reporting that shows risk, not activity
Ticket counts and uptime percentages tell you the service is busy. They do not tell you whether you are more secure than last quarter.
Useful reporting covers, at minimum:
- patch and update compliance across devices and servers
- backup success rates and the date of the last tested restore
- users with admin rights and accounts that should have been removed
- security alerts and how each was resolved
- open risks, agreed priorities and progress against them
The NCSC lists similar measures for infrastructure health reports and points out that insurers may ask for recent health or configuration reports after a claim (NCSC: Choosing a managed service provider, retrieved 10 November 2026). Ask to see a sample report before you sign. If it would not help you answer a question from your board or your insurer, it is not good enough.
5. Contract terms and a clean exit
The best time to plan your exit is before you start. The NCSC advises agreeing contract duration, renewal and termination terms that give you flexibility if your business changes direction or you are unhappy with service quality (NCSC: Choosing a managed service provider, retrieved 10 November 2026).
Check that the contract covers:
- Ownership. You, not the provider, should own your domain, cloud tenants and top-level admin accounts.
- Handover. Documentation, configuration and credentials returned in a usable form, with a defined period of support during transition.
- Data. Return and deletion of your data, including backups and logs, at the end of the contract.
- Liability. Clear agreement on who is accountable for vulnerabilities, damage and incident impact.
- Logs. How long security logs are kept, and whether you or an incident responder can access them.
A quick comparison checklist
| model | Strong answer | Warning sign |
|---|---|---|
| Own security | Current certification with relevant scope, MFA and least privilege on all access | "We are certified" with no detail on scope or access controls |
| SLAs | Response and resolution targets by priority, incident notification times | Response times only, or no written targets |
| Remediation | Named responsibilities, fixes included or clearly priced | "We will alert you" with no commitment to fix |
| Reporting | Risk, patching, backups and access, with trends | Ticket counts and uptime only |
| Exit | Documented handover, you own admin accounts | Provider holds sole admin access to your tenant |
Supplier reviews are still uncommon. The government’s breaches survey found that only 15% of businesses formally reviewed the cyber security risks posed by their immediate suppliers, rising to 48% of large businesses (Cyber Security Breaches Survey 2025/2026, DSIT and Home Office, retrieved 10 November 2026). Your managed provider should be the first supplier you review. For the wider picture, see our guide to third-party cyber risk.
Common mistakes
- Choosing on price and service list alone. Cheap and broad often means monitoring without remediation.
- Not checking the provider’s own security. Its access to your systems is a risk you are accepting.
- Accepting SLAs that only cover response time. You need resolution targets and incident notification too.
- Letting the provider hold your only admin credentials. You should always be able to regain control of your own systems.
- Never reviewing the service after signing. Hold quarterly reviews against the reporting you agreed.
Frequently asked questions
Should we use one provider for everything or several specialists?
One provider reduces gaps between suppliers and gives you a single point of accountability. Several specialists can give more depth in each area but need someone to coordinate them. Whichever you choose, commission independent testing from a party that does not run your systems.
Will the Cyber Security and Resilience Bill regulate our provider?
Possibly. The Bill would bring medium and large managed service providers into the Network and Information Systems Regulations, with the Information Commission as regulator, but small and micro providers would be exempt unless designated as critical suppliers. As at 10 November 2026 the Bill is in the House of Lords and the duties would start through secondary legislation after Royal Assent. Our article on the Cyber Security and Resilience Bill covers it in more detail.
How long should a managed services contract be?
Long enough for the provider to stabilise and improve your estate, and short enough that you can leave if the service is poor. Whatever the term, look for a notice period and exit process you could realistically use, and avoid automatic renewals you will not notice.
Should we ask for references?
Yes. The NCSC recommends asking for references or testimonials from other clients, particularly SMEs (NCSC: Choosing a managed service provider, retrieved 10 November 2026). Ask referees how the provider handled a real incident, not just how friendly the service desk is.
Getting started
Use the questions above with every provider on your shortlist and compare the answers side by side. Falx is Cyber Essentials Plus certified, and our Continuous Operations model runs IT with security at the centre, including managed services for day-to-day support. If you would like to put these questions to us, talk to our team.

Ashley Argyle
Writing about cyber security and technology at Falx.





