Checking your security monitoring
Verify which systems produce security signals, how missing coverage is detected and who handles alerts under the agreed service arrangement.

Security monitoring is useful when the business knows what’s being observed and what happens next. A green dashboard won’t tell you whether every device is reporting, or whether a person will act on each alert.
Ask IT or the provider to explain the coverage, gaps and response arrangement. Keep scheduled control checks separate from event collection and staffed incident response; they can have different timings and responsibilities.
Record what’s covered
List the accounts, devices, cloud services and network equipment included. State which signals each provides and which systems can’t be observed through the current tools.
Compare the monitored list with the asset inventory. Include remote devices and supplier-managed systems. Record exclusions with an owner and a review date.
NIST’s continuous monitoring guidance describes a strategy for ongoing visibility into assets, threats, vulnerabilities and control effectiveness. Its US federal context doesn’t create a blanket legal requirement for a Canadian small business.
Test that signals arrive
Use a harmless test event, or the vendor’s own test method, to check the path from a representative system to its monitoring destination. Record whether the expected event arrived with usable information.
Check how the team notices a reporting agent, connector or log feed has stopped. A silent source shouldn’t look the same as a healthy source with no detected event.
Our security logging guide covers collection details. This review asks whether the agreed coverage is operating and owned.
Confirm who handles alerts
Separate collecting a signal, assessing it and taking action. Name the person or provider responsible for each step and check their service hours.
Ask what happens outside those hours and when the usual business contact is unavailable. Don’t infer around-the-clock human response from software that runs continuously.
Confirm the authority needed to suspend an account, isolate a device or disrupt a business service. The technical responder and business decision-maker need a working escalation route.
Review priority and exceptions
Ask how alerts are prioritized and how uncertain results are investigated. Keep a record of accepted exceptions, including why a rule was adjusted or a device excluded.
Monitoring can miss activity and generate false alarms. Review each tuning change for the risk it adds as well as the alerts it removes.
An exposure finding also needs a separate remediation owner. Spotting a problem doesn’t patch it, so check separately that the vulnerable service has been fixed.
Keep monitoring proportionate
Document the purpose of collected records, access and retention. Which privacy law covers employee information depends on your province and whether you’re federally regulated.
Use the Privacy Commissioner of Canada’s workplace privacy guidance as a reference. Don’t collect full message content or broad staff activity just because the tool offers it.
Verify the handoff and review changes
Run a controlled alert exercise with the responsible people. Check receipt, escalation, evidence handling and the permitted response without creating a live incident.
Record findings and close gaps through the service review. Repeat the checks after new devices, changed licences, connector changes or a supplier handover. Report coverage and limitations accurately.


