Why this choice matters
The business’s IT provider (MSP) holds more in its hands than it seems at first. It has access to the servers, email, backups and admin accounts, and it is often the only one who knows how everything is connected. When it works well, you hardly hear about it. When it works less well, that shows on the day the office is at a standstill, customer data is exposed or an inquiry arrives from the Privacy Protection Authority.
At the first meeting it is easy to be impressed by the price, the availability and the atmosphere. These things matter, but they do not tell you how the provider will behave on a hard day. The following questions are meant to check exactly that. They do not have a single “right” answer, but a vague answer is already information.
1. What happens when something gets stuck?
Ask to hear what a support request looks like from the moment it is opened until it is closed: where you turn, who answers, how you know it is being handled and what happens outside working hours. An organized provider can explain this simply, including the difference between a fault that stops the whole office and a regular request that can wait until morning.
Response times and priorities should be written into the agreement (SLA). The goal is for both sides to understand the same thing before the first fault. Ask also what happens when the person who knows your systems is on vacation or sick, and who continues the work without starting from scratch.
2. Who owns the documentation and passwords?
The network, servers, accounts and licenses belong to the business, and so does their documentation. Ask which documents the provider maintains: a network diagram, a list of equipment and licenses (asset inventory), the firewall settings, the permission structure and the access details for the admin accounts. Ask where the documentation is kept and whether you can get it at any moment.
The really important question is what happens if you part ways. A professional provider does not hold the business hostage (vendor lock-in). It hands over full documentation, helps with an orderly transfer to someone else and does not leave behind accounts that only it knows the password to.
3. How does the provider approach information security?
Information security is part of the daily work of every IT provider, even when the business is small. Most incidents that shut businesses down start with basic things: a leaked password, a server that was not updated, remote access left open to the internet or an employee who worked with admin rights for no reason. A provider that treats security as an optional extra leaves those doors open.
Ask to hear what the provider does by default, without you having to ask. For example:
- Two-factor authentication (MFA) for email, remote access and every admin account.
- Endpoint and server protection with an EDR system whose alerts someone actually follows.
- Permission management: separate admin accounts, a unique local administrator password on every computer (for example with LAPS) and role-based permissions (RBAC).
- Updates (patch management): a regular process for operating system, software, firewall and network equipment updates.
- Network separation (network segmentation): guests, cameras and printers on a network separate from the work network, using VLANs.
Ask also how the provider protects its own access to you. A provider that connects to many customers with the same password, or without two-factor authentication, becomes a weak point shared by all of them (supply chain risk).
4. What does the provider know about privacy and regulation?
Almost every business holds personal data: details of customers, employees and suppliers, and sometimes medical or financial information too. The Privacy Protection Law and its Privacy Protection Regulations (Data Security), 2017 apply to this data. Amendment 13 to the law, which came into force in August 2025, expanded the Privacy Protection Authority’s supervision and enforcement powers, including the imposition of financial sanctions.
The IT provider does not replace a legal advisor, but it is the one that actually implements much of what is required: access control, documentation of permissions, backup, logging and handling of security incidents (incident response). A provider that does not know these requirements may build a system that works well and still does not meet them, and the gap will show precisely on the day you need to show what was done.
Ask whether it knows the National Cyber Directorate guidance, how it documents its work, and whether it can work according to frameworks such as ISO 27001 or NIST CSF when the business is required to by a large customer, a tender or an insurance company.
5. When was a restore last tested?
Almost every provider will say there is a backup. The interesting question is when someone last restored from it (restore test), what was restored and how long it took. A report that the backup “succeeded” shows that the copy job ran. It does not show that you can get back to work from it.
Ask where the copies are, whether there is a separated copy (air-gapped) that a ransomware attack on the network will not reach, and who gets the alerts when a backup fails. From here it is easy to move to the broader question: how long the business can be down (RTO), how much data it can afford to lose (RPO), and what the plan is to get it back to work (DRP) within that time.
6. Who talks to the other suppliers?
An average office has several suppliers: an internet provider, an accounting software company, a phone system supplier, a printer company and sometimes a hosting provider for the website. When something does not work, each tends to point at the other, and the business is left in the middle with a phone in hand.
Ask whether the provider takes responsibility for coordination (vendor management): opens a ticket with the internet provider, talks to the software’s support team and makes sure the problem is fully solved. This saves management a lot of time, and also prevents a situation in which an outside supplier gets remote access to systems (third-party access) without anyone knowing about it or closing it at the end.
7. What gets done when nobody calls?
Much of an IT provider’s important work happens quietly: monitoring servers and disks, tracking backups, installing updates, replacing equipment before it fails (lifecycle management) and planning licenses and budget for next year. A provider that works only when you call it (break-fix) will always arrive after the fault.
Ask what is monitored, who gets the alerts and what reporting you will receive. A short periodic review, what was handled, what needs a decision and what is planned, helps management understand the state of IT and make decisions before they are forced on it.
Summary: how to use the questions
There is no need to examine a provider as if in a test. It is enough to ask, listen and notice where the answers become general. A few practical guidelines:
- Ask for response times, the scope of service and responsibilities to be written into the agreement (SLA).
- Make sure the documentation, the primary accounts and the domain are registered in the business’s name.
- Ask what is done for information security by default: MFA, EDR, permissions and updates.
- Check that the provider knows the Privacy Protection Law, Amendment 13 and the National Cyber Directorate guidance.
- Ask for documentation of the most recent restore test.
- Clarify who coordinates with other suppliers.
- Agree on what reporting you will receive and how often.
A provider that answers these questions clearly, including “we don’t do that, and here is who does”, is usually a provider you can build a long-term working relationship with.