1. Who owns the problem until we can work again?
Ask them to walk through an ordinary request, a major business interruption, and a suspected security incident. Who receives the request? Who investigates? Who coordinates with the application supplier? Who keeps your business informed?
Ask what changes when the first technician needs help. Escalation should bring the right expertise or authority without leaving you to restart the explanation. Clarify the owner and next update rather than accepting “we will escalate it” as the result.
2. What does your service target actually measure?
Ask for the Service Level Target (SLT), its priority definitions, support calendar, and clock rules. A receipt email, a meaningful response, a workaround, a permanent resolution, and closing a record are different events.
Ask them to explain a missed target and what happened next. Confirm after-hours arrangements separately from automated monitoring. Request the written scope; do not assume that a target guarantees recovery by that time or includes coverage not stated in the agreement.
3. Can we see a sanitized service report?
Request a report that identifies its time period, covered population, exclusions, open work, dependencies, and follow-up actions. Ask what each figure means. An attractive chart is not useful if nobody can explain which tickets were counted.
Ask for overdue actions and evidence of verification—not only tickets marked closed. When a report cannot support response times or target attainment, the provider should say so. Protecting another client's privacy is appropriate; concealing how the service is measured is a different issue.
4. What evidence supports the security claims?
Bring your cyber-insurance application and requirements into the discussion. Ask which controls your business represented as implemented, which devices and users are in scope, who verifies them, and what happens when coverage changes. Your provider's service list is not your insurance policy.
Request examples of deployment coverage, current protection status, training completion, access reviews, and backup completion records. A completion record is not a restore test, and it is not a promise that the provider runs restore tests. Ask how exceptions are handled and how you receive notice. A purchased license or a green dashboard alone does not answer every one of those questions.
NIST's small-business guide provides a framework for discussing security responsibilities, and the FTC advises businesses to consider the coverage they actually need with an insurance adviser. [1, 2]
5. What do we control, pay for, and get back if we leave?
Ask who owns the company accounts, domain, documentation, and purchased equipment. Confirm how authorized people regain access and how provider access ends. Ask whether outside support partners are used, what they can access, and who remains accountable.
Make the provider distinguish technical requirements, support standards, and purchasing policies. When they require replacement software or hardware, ask why existing equipment cannot remain and what the alternatives cost.
Review onboarding, projects, renewals, after-hours work, and offboarding charges. Ask for a relevant reference with permission, rather than demanding another client's confidential incident details.
Turn the answers into an evaluation record
| Record | Example of useful evidence |
|---|---|
| Claim and scope | What service is promised, for which users and systems? |
| Evidence reviewed | A defined report, workflow, test record, or written provision. |
| Gap and owner | What remains unresolved, who will answer, and by when? |
This is not an interrogation designed to reject every provider. It is a way to expose differences that a price comparison misses. An honest limitation with a clear plan is more useful than an absolute promise.
Blue Tree Technology® should be evaluated on the same basis: defined work, credible evidence, accountable people, and a transition you understand.
Verification sources
[1] NIST: Small Business Quick-Start Guide. [2] FTC: Cyber Insurance.
