Cybersecurity services
Assessments, endpoint protection, email security, training, incident readiness, and 24/7 monitoring for managed-service clients.
You cannot fix everything at once, and should not have to guess what matters most. We review how you are actually set up, rank risks by likelihood and impact, and give you an actionable plan.
A structured review against the attacks that most often cause harm (stolen passwords, phishing, ransomware, unpatched systems, misconfigured cloud), ending in ranked risks and a practical plan, not scanner output. We measure against recognized baselines: the Canadian Centre for Cyber Security's baseline controls for small and medium organizations, the CIS Critical Security Controls and the NIST Cybersecurity Framework. Findings are mapped to any specific requirement, such as OSFI Guideline B-13 for federally regulated financial institutions or a client's questionnaire.
| Area | What we check |
|---|---|
| Identities and access | Accounts, admin rights, missing MFA, password policies, joiners and leavers |
| Devices | Patching, disk encryption, endpoint protection, who can install software |
| Email and collaboration | Filtering, SPF, DKIM, DMARC, external sharing, abused mailbox rules, Microsoft 365 or Google Workspace settings |
| Network and remote access | Firewall rules, VPN, Wi-Fi, services exposed to the internet |
| Backups and recovery | Coverage, whether attackers could reach them, last tested restore |
| Cloud services and vendors | Key platform configuration, third-party access |
| People and process | Training, incident response, verifying payment or banking changes |
| AI tools, if in scope | AI services staff use, data reaching them, prompt injection and leakage defences (AI governance) |
Three rows from an invented risk register, showing the format we use:
| Finding | Likelihood | Impact | Recommended fix | Effort |
|---|---|---|---|---|
| Two administrator accounts have no MFA | High | High | Enforce MFA and move admins to separate accounts | Low |
| Backups stored on a share reachable by all staff | Medium | High | Isolate backups and test a restore | Medium |
| No DMARC record on the main email domain | High | Medium | Publish DMARC in monitoring mode, then enforce | Low |
We use read-only access through named accounts removed at the end, share findings only with people you name and delete assessment data as agreed. You decide who sees what: the summary suits insurers or clients, the technical report your IT team.
Your business and data guarded from intruders, biggest risks first.
A clear roadmap instead of recurring security fire drills.
The roadmap shows the order and estimated effort of the work.
For insurers, clients and boards, rather than assurances.
Fix findings with your team, another provider or us, as a project or within managed IT services with ongoing security (the assessment doubles as its baseline). Common next steps: EDR deployment, email security, awareness training.
Systems, sites and questions in scope, plus the rules and time windows for any scanning.
Output: Signed scope, scanning authorization.
Configuration review, approved scans and short interviews with the people who run your systems.
Output: Evidence and raw findings.
Findings compared with a recognized baseline and ranked by likelihood and impact on you.
Output: Risk register.
Leadership and IT walked through the findings, quick wins and longer-term roadmap.
Output: Summary, technical report, roadmap.
After an agreed period, we check the fixes made and update the register.
Output: Retest note, updated register.
No package prices: estimates in Canadian dollars from an agreed scope, taxes shown separately.
A scan finds known weaknesses on reachable systems; an assessment also checks how accounts, email, backups and processes are set up, and which risks matter. A bare scan may need only a tool. For deep penetration testing of a custom application, we scope it and coordinate a specialist.
Very little. Most of the work is configuration review and short interviews. Any scanning is authorized in writing and scheduled in agreed windows.
No. It shows how well your controls reduce risk and where the gaps are. Compliance with PIPEDA, provincial privacy laws or sector rules is a legal question for your counsel, and certification comes from an independent body. See compliance readiness.
Typically once a year, and after major changes such as a merger, a move to the cloud or a significant incident. Managed-service clients receive ongoing reviews under their agreement.
Assessments, endpoint protection, email security, training, incident readiness, and 24/7 monitoring for managed-service clients.
Privacy and security practices ready for regulators, clients, auditors and insurers, gaps fixed before anyone asks.
Four lessons from large data breaches, what they mean for you, and a readiness checklist.
Tell us about your organization and what prompted the question. We will arrange a scoping conversation.