Fake IT Calls Are Hitting Canadian Law Firms. MFA Won’t Save Them.
November’s Industry Insights, and a question about accountability in cybersecurity.
In late October, several Canadian law firms disclosed that someone had gained unauthorized access to their systems. Around the same time, the Canadian Centre for Cyber Security warned of callers impersonating internal IT staff. They claimed an urgent password change or authentication update was required and directed employees to fake sign-in pages that captured credentials and relayed authentication responses.
Some callers would hang up when an employee tried to verify the request.
I keep thinking about the person taking that call. This attack can defeat conventional MFA, putting considerable weight on the employee’s decision to pause and check. In a workplace where deadlines matter and requests from senior people carry weight, responding promptly is part of being good at your job. Someone claiming authority and invoking urgency has something familiar to work with.
The disclosures do not establish how each firm was compromised. The campaign establishes something narrower: it works only if an employee does not pause. We teach employees to pause and check, then send them back into workplaces where keeping someone waiting can require an explanation.
I’ve written elsewhere about our obligation to protect vulnerable people from hackers. The workplace can create those circumstances. A capable person can find themselves caught between the advice on a cybersecurity awareness poster and everything they have learned about getting through the day.
My team and I spend a fair amount of time thinking about things like this.
Every month, we publish Industry Insights, a short collection of briefs on what is happening in the sectors our members work in. We follow developments and work out what they mean for the people we advise. Members and colleagues bring us questions, too. Have you heard about this? Have you thought about what happens next? We talk it through: who will feel the effects, what might change, what could someone reasonably do about it. We write some of it down and share it.
It’s a great gig if you can get it, especially if you enjoy having something to think about. My colleagues work in different sectors and know much more than I do about their areas of specialization. I know what I know, but I don’t know what they know, you know?
Reading across this month’s Industry Insights, I kept finding people held to account for controls that someone else sets.
In our piece for the mining sector, for instance, a CIO has to answer for the security of operational systems spread across remote sites, with supplier connections arranged over many years. Establishing who can connect, who authorized the access, and who can change it can itself be considerable work. Production depends on some of those relationships. Changing them takes decisions from people outside IT.
The CIO’s job is to make the exposure visible, say what it means for production, and put the decision in front of someone who can make it. Leadership decides what it will pay for, change, or live with.
Back to our law firms. The employee on the phone also depends on a decision made elsewhere: whether leadership will back them when verification delays a legitimate request. They answer for a pause that only works if leadership will accept the delay when the call turns out to be legitimate.
Before I hold anyone accountable, I want to know what they could see, what they could decide, and what support they had when they raised a concern. I expect people to take responsibility for their work. That includes the people who set priorities, approve budgets, choose suppliers, and decide how much delay is acceptable. Those three questions belong whenever we assess someone’s performance, and leaders answer them too.
If I expect someone to question an urgent request made in my name, I owe them a reasonable response when the request really is mine. And I have to be willing to wait.