Checking the security coverage you're paying for
Ask for evidence of sign-in protection, device coverage, email controls, patching and alert response, then assign owners to gaps in your IT agreement.

An IT agreement may name security software without explaining which accounts and devices it covers, who reviews its alerts or what happens when a control fails. Those details determine what you’ve bought and what your business still needs to handle.
Use a coverage review to compare the agreement with the systems you use. Bring a current account and device inventory, the service schedule and the person who can approve changes. Ask for dated evidence and record any exceptions, including systems managed by another supplier.
1. Check sign-in coverage
Ask which services enforce multi-factor authentication (MFA), which methods are allowed and whether administrators use separate accounts. Include the domain registrar, backup console and finance applications as well as email.
Microsoft’s authentication-strength guidance distinguishes phishing-resistant methods from other forms of MFA. Ask whether supported applications require those methods and how enrolment and account recovery work. A policy screenshot alone won’t show whether all the intended users are covered.
Request a list of excluded accounts with an owner, reason and review date. Emergency access needs a tested design; don’t remove an exception without understanding how administrators would regain access during a failure.
2. Match managed devices to your inventory
Compare the management report with the computers and phones used for work. Look for a device that hasn’t checked in, a new laptop that was never enrolled or a contractor’s computer accessing sensitive files.
For each device category, agree what the provider checks: operating-system support, updates, encryption, endpoint protection and configuration. Ask what happens when a check fails. A notification to the owner and a restriction on application access are different actions.
Personal-device rules also need a clear boundary around what IT can see and change. Our BYOD guide covers that ownership and privacy decision.
3. Confirm email and payment controls
Ask who manages filtering, mailbox alerts and domain authentication. Have them explain how suspicious messages are reported and investigated, including messages that reached an inbox despite filtering.
Keep a separate approval process for supplier bank-detail changes and unusual payments. Email filtering won’t tell you whether a payment request is real. The supplier-payment guide sets out how to check a request independently and who signs it off.
4. Review failed updates and exceptions
Ask for failed updates, unsupported systems and overdue work, with the date the report was generated. Confirm whether the agreement includes third-party applications, network equipment and firmware as well as the operating system.
For a system that can’t be updated immediately, record the operational constraint, temporary safeguards, decision owner and next review. An exception should stay visible until it’s resolved or formally accepted.
The Cyber Centre’s baseline controls provide a Canadian reference for discussing patching, device configuration and access controls. Use them to build a program, then check that your agreement covers each item.
5. Establish who acts on alerts
For each important alert, identify who receives it, when someone reviews it and who can decide to isolate an account or device. Ask specifically about evenings, weekends, supplier handoffs and a primary contact being unavailable.
Monitoring hours, support hours and committed response times should be stated in the agreement. Don’t infer them from a product label. Include backup failures and the results of restore tests in the review.
Finish with a short action register: gap, evidence, owner, next step and due date. Review outstanding actions through the monthly IT review. If you need help comparing coverage with business requirements, contact us to discuss an IT assessment.


