Home / Blog Posts

What Canadian Businesses Can Learn from the KPMG Canada Breach and Recent Cybersecurity Warnings

by | Nov 20, 2026 | Cyber Security

On November 18, 2026, KPMG Canada confirmed that an unauthorized third party had gained access to tax documents belonging to some of its clients. The accounting and consulting firm said it acted immediately to contain the cybersecurity incident, secure its systems, and begin contacting affected clients.

In a statement, KPMG Canada spokesperson Sonja Cloutier-Bosworth expressed confidence that the affected information was not available online or being misused, based on the firm’s ongoing monitoring.

The full extent of the incident remains unclear. KPMG has not publicly disclosed how the unauthorized access occurred, how many clients were affected, or how many documents were accessed. The initial method of entry has also not been confirmed.

Cybersecurity Incidents Impacting Canadian Organizations

The disclosure follows a series of reported cybersecurity incidents affecting Canadian organizations, including major firms in the legal and financial sectors.

For professional services organizations, protecting client information is central to their operations. Accounting firms, law firms, and financial advisers routinely handle confidential financial records, tax information, and sensitive business documents.

Their clients depend on these organizations to manage that information responsibly and maintain its confidentiality.

The KPMG incident brings renewed attention to the cybersecurity risks facing organizations entrusted with sensitive client information, and the importance of protecting that information across Canada’s professional services sector.

Recent Cybersecurity Warnings Highlight a Broader Threat to Canadian Organizations

On October 28, 2026, the Canadian Centre for Cyber Security (CCCS) issued alert AL26-028, warning of an ongoing voice phishing, or “vishing,” campaign targeting Canadian organizations, including those in the legal and financial sectors.

According to the alert, attackers have impersonated internal IT support through telephone and Microsoft Teams calls, directing employees to fraudulent sign-in pages designed to gain access to their accounts.

The warning comes amid reported breaches at four major Canadian law firms: Bennett Jones LLP, McCarthy Tétrault LLP, Davies Ward Phillips & Vineberg LLP, and Borden Ladner Gervais LLP. The Globe and Mail reported that IT impersonation was involved in at least some of these incidents.

The warning also reinforces the need for phishing-resistant MFA, stronger verification during account resets, and clear procedures that allow employees to independently confirm unexpected IT support requests before taking action.

Reminder: KPMG Canada has not disclosed how its systems were accessed, and no connection between its incident and the methods described in the CCCS alert has been confirmed.

When Attackers Exploit Trust Rather Than Technology

The Canadian Centre for Cyber Security’s May and October 2026 alerts describe attacks that rely on impersonation rather than exploiting a software vulnerability.

Attackers pose as IT support staff, contact employees by phone or through familiar platforms such as Microsoft Teams, and direct them to fraudulent sign-in pages. Some also manipulate multifactor authentication (MFA) resets or device enrolment processes to gain continued access.

These methods exploit the trust employees place in familiar workplace tools and established IT support procedures. Once attackers obtain valid credentials or authenticated sessions, they can access cloud services using a legitimate user’s identity.

That makes limiting access to sensitive information just as important as protecting the account itself. Professional services firms often manage confidential client information across documents, attachments, and shared folders.

Access permissions should reflect the specific client engagements an employee supports, with regular reviews to ensure unnecessary access is removed.

Organizations can further strengthen these controls by requiring access to sensitive applications and client information from managed devices that meet established security requirements. This adds another layer of verification beyond a valid username and password.

As Calvin Engen, Chief Technology Officer for F12.net, explains, “One compromised account should have a limited reach.”

Endpoint security remains an important defense, but monitoring devices alone may not reveal the misuse of authenticated cloud sessions.

The Cyber Centre recommends monitoring suspicious MFA registrations, unusual account changes, and high-volume access to Microsoft 365 files.

Effective identity security therefore extends beyond the initial login. Organizations also need appropriate verification, monitoring, and access controls when employees reset MFA, recover accounts, or register new devices.

What Canadian Organizations Can Do to Strengthen Their Defenses

The Canadian Centre for Cyber Security’s October 2026 alert outlines practical measures organizations can take to reduce their exposure to identity-based social engineering.

For Canadian businesses, five areas deserve particular attention.

1. Strengthen Identity Verification Procedures

Review how employees and IT support teams verify requests for password changes, MFA resets, and new device registrations. Require employees to confirm unexpected requests through established support channels rather than relying on caller ID, email addresses, or the identity displayed in a messaging application.

2. Review External Collaboration Permissions

Audit external access settings in Microsoft Teams, Slack, Webex, and other collaboration platforms. Restrict messaging, calls, and meeting invitations to trusted or operationally necessary external users.

Regularly review guest permissions while maintaining the access employees need to work with legitimate clients and partners.

3. Adopt Phishing-Resistant Authentication

Implement phishing-resistant MFA, including FIDO2 security keys or device-bound passkeys, particularly for administrators and employees accessing sensitive information.

Apply strong identity verification to account recovery and MFA re-enrolment procedures so that security remains consistent throughout the authentication process.

4. Limit Access to Sensitive Information and Monitor Suspicious Activity

Protecting an account is only part of the equation.

Organizations should also limit what that account can access. For professional services firms, this means tying permissions to the client engagements employees actually support, reviewing access regularly, and removing permissions when they are no longer needed.

Where appropriate, use conditional access policies to require managed, compliant devices for access to sensitive client information and privileged applications. This helps organizations control not only who can access information, but also which devices can be used to access it.

Configure monitoring for unusual sign-ins, unexpected MFA registrations, changes to account permissions, and unfamiliar application authorizations.

Review Microsoft 365 audit logs for unusual document access, including high-volume downloads from SharePoint and OneDrive. Establish procedures for investigating and responding to suspicious activity.

Those procedures should include clear steps for containing a compromised account. When compromise is suspected, authorized responders should be able to revoke active sign-in sessions, block further access where necessary, and review potentially unauthorized authentication methods.

Just as importantly, organizations need to establish who is responsible for taking these actions. A documented incident response plan should identify who has the authority to initiate containment, which team is responsible for executing it, and how incidents are escalated outside regular business hours.

5. Reinforce Employee Awareness Through Practical Testing

Train employees to recognize unexpected IT support requests, particularly those involving urgent password changes or authentication updates. Conduct regular awareness exercises and reinforce procedures for independently verifying requests. Ensure employees know how to report suspicious calls, messages, or websites.

“Training needs to give people permission to pause and question an urgent request, even when it appears to come from someone they trust.”
Calvin Engen, Chief Technology Officer, F12.net

Together, these measures support a more consistent approach to protecting identities, managing access, and detecting unauthorized activity.

They also help organizations limit the amount of sensitive client information exposed if an account is compromised and improve their ability to detect and contain suspicious activity.

Cybersecurity Spending Is Easy to Measure. Effectiveness Takes Evidence.

An organization can show how much it has invested in security tools, but that alone doesn’t tell leadership whether suspicious activity will be detected or unauthorized access prevented.

It also doesn’t show how much sensitive information could be exposed if an account is compromised, or how quickly that access could be contained.

The NIST Cybersecurity Framework 2.0 offers a useful starting point by emphasizing cybersecurity outcomes rather than specific technologies.

For identity security, that means understanding how many employees use phishing-resistant MFA, whether sensitive account recovery requests are independently verified, and how quickly unusual account activity is detected.

It also means measuring whether employees have access only to the client information they need and whether security teams can identify which documents were accessed, downloaded, or shared following a suspicious login.

Organizations should also be able to demonstrate whether sensitive systems require managed-device access, how quickly compromised sessions can be revoked, and whether the teams responsible for containment can act without unnecessary delays.

These measures help leadership assess not only whether threats can be detected, but how effectively access can be restricted when an incident occurs.

“If one employee account is compromised today, how much client information can it reach, and how quickly can we detect and contain the activity?”
Calvin Engen, Chief Technology Officer, F12.net

These metrics help executives understand where their organization is protected, where gaps remain, and whether cybersecurity investments are reducing business risk.

Every Organization Has an Opportunity to Strengthen Its Defenses

The KPMG Canada incident deserves a measured response, not speculation about what happened or what could have been done differently.

What it does provide is an opportunity for Canadian organizations to examine how they protect the sensitive information entrusted to them.

The question for business leaders is whether their existing safeguards can reliably verify identities, limit access to confidential client information, detect unusual document activity, and contain unauthorized access before it extends further.

Building resilience starts with understanding those capabilities and addressing gaps before they become problems.

That includes regularly reviewing who can access sensitive information, validating that permissions remain appropriate, and ensuring security teams have the visibility and resources to investigate suspicious activity.

It also means verifying that access restrictions are enforced, compromised sessions can be revoked promptly, and responsibility for containment is clearly assigned before an incident occurs.

A review of identity security and data access controls is a practical place to begin. This helps organizations establish priorities, strengthen existing controls, and measure their progress over time.

Do You Know Where Your Organization Stands in Identity Security?

Knowing who can access sensitive information, how suspicious activity is detected, and how quickly unauthorized access can be contained is essential to building cyber resilience.

F12 helps Canadian organizations evaluate their cybersecurity posture, identify gaps, and prioritize improvements based on business risk.


Talk to an F12 Cybersecurity Expert
→

Stay Updated

Subscribe to receive information and updates from F12

Recent POSTS