Later in the presentation, we’ll talk about AI use policies for employees.
Moral Implications of Cybercrime
We’ve already touched on the moral issues. We do not want to fund criminals. If that criminal organization is connected to countries like North Korea or Iran, which face heavy sanctions and financial constraints, cybercrime revenue may be helping fund missile programs and other activities. We don’t want to be victims. If you pay a ransom, you’re encouraging them to attack someone else.
The bad guys will often promise to delete your data. A couple of years ago, the FBI seized the servers of what was then the world’s largest ransomware group, LockBit. What did they find? They found all the victim data that had supposedly been deleted. It was still there. We cannot trust criminals.
When your organization is compromised, you’re exposing data that largely isn’t yours. It’s your employees’ data. It’s your clients’ data. You have an obligation to protect it. And when you’re compromised, you expose the people in your business and personal circles as well.
We’ve all received that random email from someone we know telling us to click a strange link. You probably became suspicious immediately. That person was likely compromised. Maybe they didn’t take security seriously enough, and now they’ve put everyone around them at risk. Identity theft and cybercrime have such a serious impact on some people that they contemplate suicide. This is a serious issue, and I wish it received more media attention than it does.
Ransomware Evolution
Let’s talk about ransomware.
When ransomware first appeared, attackers would simply encrypt your computer or network. You’d receive a ransom note and decide whether or not to pay. A lot of people chose not to pay, so the criminals adapted.
Now, if your organization gets encrypted and refuses to pay, the attackers may respond by saying, “Fine. We’ll publish all the sensitive data we downloaded from your employees and clients unless you pay.”
If you still refuse, they may launch a massive bot attack to cripple your network and disrupt your operations.
If you continue refusing, they may contact your clients directly and tell them that your organization doesn’t take security seriously. They may even demand ransom payments from your clients.
They will do almost anything they can to get paid.
Real-World Ransomware Examples
Here are a couple of examples.
About a year ago, PowerSchool, one of the largest K–12 education platforms in North America, experienced a ransomware incident. Attackers downloaded faculty, staff, and student data from approximately 18,000 schools. PowerSchool paid the ransom. Did the criminals delete the data? No. They kept it.
The attacker then sent ransom demands directly to the schools, threatening to publish confidential information unless additional payments were made.
Another recent example involved Canvas and its parent company. They experienced a similar attack. Criminals stole the data and began threatening schools. In this case, the company paid the ransom. Personally, I don’t trust that the data was actually deleted.
In the PowerSchool case, authorities eventually identified and arrested the perpetrator. It turned out to be a single individual in their late teens who likely learned many of these techniques through resources shared in criminal communities online.
A lesson learned: If you ever receive a ransom note, don’t engage with the attacker. Pretend you don’t exist. Forward the communication to the appropriate people in your organization and let trained professionals handle it.
Case Study: CFO Ransomware Experience
I want to share a brief story.
Doug is the CFO of a Midwest service company. About two years ago, they experienced a ransomware event. We took over management of their network about six months afterward. He was kind enough to record a short video about the experience.
Doug explained that before the incident, they believed they were too small to be targeted. They assumed cyber criminals only pursued large organizations and thought their IT team had everything covered. They were wrong.
The ransomware event and recovery process were far worse than they imagined. Business interruption caused significant financial losses. He spent months on conference calls and recovery efforts. Even after employees returned to work, he was still trying to catch up. Organizational morale suffered as well.
His advice was simple: Don’t skimp on cybersecurity. Partner with a mature, security-focused managed services provider. Make sure you have secure backups. Invest in cyber insurance to help mitigate risk.
That was a powerful message.
Business Impact and Aftermath
In both versions of this webinar, I share Doug’s story because it started with a simple end-user mistake. We’re all human, and the attackers are smart. But from a leadership perspective, the lesson is even more important: Nobody is too small to be targeted.
The aftermath of an incident is often much worse than people imagine. Even years later, organizations may still be dealing with attorneys, insurance claims, compliance issues, and reputational damage.
Organizations often ask questions afterward such as:
- Why did we wait to prioritize security spending?
- Will our reputation be damaged?
- Will we be sued?
- Will regulators investigate us?
- Will I personally be held accountable?
- Will this force us to raise prices?
In fact, I recently saw a statistic showing that roughly 30% of small businesses have had to raise prices after a major cyber incident simply to recover costs and maintain profitability.
Leadership Responsibility
Which brings us to the central theme of this presentation:
Who is ultimately responsible for preventing an existential event within your organization?
Is it IT? No.
IT owns some of the blocking and tackling, but they do not own the outcome. The responsibility belongs to executives, CEOs, boards of directors, and executive leadership teams.
Those leaders are ultimately accountable for cybersecurity outcomes.
Leadership Accountability (Continued)
Part of the challenge is that many leaders don’t know how to engage with cybersecurity the same way they engage with finance. CEOs understand they own financial outcomes, even though they aren’t doing the accounting themselves. They know how to ask questions and hold people accountable.
Finance has centuries of established standards and best practices. Cybersecurity is relatively new, evolves rapidly, and is often less familiar to leadership teams.
Most executives understand that poor financial controls are dangerous, but they often underestimate cyber risk until it becomes personal. Like Doug said, it wasn’t until after the incident that they realized how serious the threat really was.
Cybersecurity is not an IT task. It is a business risk.
A useful analogy is that cybersecurity is to IT and data what financial controls are to accounting. IT operates the security program, but leadership owns the risk, just as leadership owns financial risk.
Financial Comparison Framework
Some questions a CEO should regularly ask the CFO include:
- How is our financial position changing, and why?
- What risks could materially impact our financial stability?
- What controls ensure our numbers are accurate?
- What keeps you up at night financially?
These questions assume the CFO has a process, can explain it, and can provide evidence to support it.
Similarly, before signing financial statements, a CEO might ask:
- What could materially be wrong with this information?
- What controls prevent fraud or material errors?
- What has changed since last quarter that increases risk?
- If we were audited tomorrow, where would you be most concerned?
Applying Leadership Questions to Cybersecurity
Those same principles apply to cybersecurity, and they lead naturally into the next section: the questions CEOs should be asking their IT and security leadership.
What event could materially harm our business? Again, think of this like those pre-signoff questions. Where are we most exposed today? Show me. Give me some evidence. Help me understand this because I don’t understand it as well as finance. I don’t need it to be too technical.
How do we prevent or detect that? If we had a serious incident tomorrow, what would I wish I had asked you today?
Again, I love that question. It moves ownership up to the top of the food chain. IT does the blocking and tackling, but leadership owns the outcome. Cybersecurity deserves the same critical questions as finance—before an incident, not after.
How Modern Hacking Works
Let’s talk a little bit about how modern hacking works. Today, attackers rely heavily on open-source intelligence. They gather information from company websites, social media posts, public records, and data that may already be available on the dark web. They also use generative AI tools like ChatGPT, Gemini, and Copilot to help identify the most effective ways to attack organizations.
Breaking through a properly configured firewall is difficult, which is why most attacks now begin with spear phishing. We should assume that at some point someone will make a mistake and an attacker will gain access. The incidents you hear about in the news—and the thousands you don’t—typically involve attackers getting past antivirus software, firewalls, and multifactor authentication. Once inside, they can spread laterally across a network in as little as 18 minutes, gain administrator privileges, download sensitive data, and, if ransomware is their goal, encrypt systems. It happens very quickly, which is why organizations need the ability to detect and neutralize threats early.
Password Security Issues
Some of this content also comes from presentations I give directly to end users. One topic I always cover is password hygiene because it’s still a major problem. Back in 2021, PC Magazine conducted a survey that remains relevant today. About a quarter of respondents said they use the same password for everything. Another quarter said they reuse passwords for most things. That’s a significant issue because if one account is compromised, attackers will immediately try those same credentials against email, banking, payroll, and other critical systems.
Another common problem is using the same password for both personal and business accounts. If a personal password appears in a data breach and an employee falls for a phishing attack at work, that single password can become the starting point for a much larger compromise.
Business Email Compromise and Financial Fraud
Business email compromise is now far more common than ransomware. When attackers gain access to a mailbox, they can impersonate trusted individuals and persuade others to move money, change banking information, or reveal sensitive information. According to the FBI, billions of dollars are lost to these schemes every year, and cyber insurance carriers report that mailbox compromises account for the majority of claims they handle.
One example involved a former client in Eden Prairie. Their CEO received a phishing email asking her to reset her Microsoft password. She entered her credentials into a fake website, and the attackers captured them. They then bypassed multifactor authentication by stealing a browser session token—the small file that allows a trusted browser to remain authenticated for a period of time. With that token, the attackers gained access to her mailbox, monitored communications with the company’s bank, and eventually convinced the bank to transfer nearly half a million dollars. The company did not have cyber insurance, and even if they had, that type of loss is often difficult to recover through a policy.
We see variations of this every day. Another common scenario involves a vendor becoming compromised. Employees receive legitimate-looking emails from a trusted vendor and eventually receive a request saying the vendor has changed banks and future payments should be sent to a new account. Organizations lose billions of dollars each year to these schemes.
Last year, both the City of Baltimore and the City of Portland experienced incidents involving compromised vendors. In Baltimore’s case, approximately $1.5 million was transferred before anyone realized the money was going to criminals. Portland lost approximately $6 million. In both cases, employees approved banking changes without independently verifying the request.
The lesson is simple: never rely solely on email when banking information changes. Verify through a trusted phone number or another established communication channel. Do not use the contact information provided in the email itself.
This issue affects businesses of all sizes. We’ve seen multiple clients lose more than $100,000 because attackers inserted themselves into existing conversations using domains that differed from legitimate vendors by only a single character. The organizations weren’t responsible for the vendor being compromised, but they were responsible for lacking the financial controls needed to verify the request before sending money.
I’ve seen policies where this area was $25,000 or $50,000. Again, considering the average claim for finance fraud is about $150,000, those numbers need to be much higher. This is a good policy. Depending upon your industry and clientele, you should consider requiring your clients to carry cyber insurance. In other words, if something happens and they go through an incident, they could drag you into a lawsuit or bring you in as a co-defendant. You want to make sure they have cyber insurance so their policy can help cover the situation and make them less inclined to pursue claims against you.
AI Usage Policies and Risks
You also need to develop an AI policy. I don’t have a sample policy here, but I’ll send one later. Many of you already know that generative AI tools like ChatGPT, Gemini, and others often use conversations to train their large language models. About 90% of users rely on free AI tools, and that’s one of the tradeoffs. You’re helping train the model. Let everybody else do that. Let’s protect our own data.
If you’re a Microsoft 365 organization, use the business version of Copilot that comes with your Microsoft 365 subscription. It protects your conversations, doesn’t use them to train the public model, and keeps everything within your Microsoft 365 tenant. It’s private and secure. If you’re using free versions of tools like Copilot or Claude, many of them offer an opt-out setting that prevents your conversations from being used for training.
The people who built these systems don’t fully know what the future holds for all of this data. It ends up somewhere in hyperspace. Because of that, never input sensitive information, passwords, banking information, confidential information, or anything you wouldn’t want exposed. Substitute sensitive details with placeholders when you’re having conversations with AI.
AI Poisoning and Scams
There’s also something called AI poisoning. Let me give you an example of how bad actors are using it against us. They know people search for things like Microsoft’s support phone number, Adobe’s support number, and similar information. They’ll launch millions of bots and flood the internet with fake phone numbers that actually connect to scammers.
You ask an AI tool for Microsoft’s support number, and it may return the scammer’s number because that’s what it found online. That’s why you must verify contact information by going directly to the company’s website. If you call that fraudulent number, the scammer may ask for your credit card information or request that you read a code sent to your phone. That code is often your multifactor authentication code. Never provide it.
Password and Authentication Best Practices
Do not use generative AI to create passwords. These systems generate content based on patterns they’ve seen elsewhere. They are not true random password generators. Instead, use the password generation feature built into a password manager.
Use business-provided AI systems whenever possible, such as Microsoft Copilot or the business version of Gemini available through Google Workspace. Those environments are designed to be more secure. I would also recommend sticking with U.S.-based AI providers. Personally, I would not use DeepSeek because it’s based in China, and I have no idea what will ultimately happen with that data.
I also do not recommend deploying OpenClaw. It’s a very powerful open-source AI platform, but there are limited controls and boundaries around it. If an employee deploys it and connects it to internal systems, it becomes very difficult to manage and secure, particularly if you’re in a regulated industry.
Passkeys and Modern Authentication
I strongly encourage you to deploy passkeys. I’m giving you a little homework here.
What exactly are passkeys? Passkeys are passwordless authentication. Passwords remain one of the biggest reasons small security incidents become major breaches. Passkeys are largely phishing-resistant.
Let’s say I set up a passkey for my Amazon account using my fingerprint on this computer. That passkey is tied to this device. I can’t log in from another device unless I’ve specifically synchronized that passkey. If a scammer tricks me and says, “Hit your fingerprint so I can help you,” it still won’t help them because they don’t have my computer. Passkeys are incredibly effective.
There are some challenges. They require a little technical knowledge, and people need to get comfortable using them. Start practicing. When websites offer passkeys, try them. Use a biometric method like a fingerprint or facial recognition and synchronize your passkeys through a trusted password manager if available.
Real-World Security Incident Examples
I also wrote an article in my quarterly newsletter about passkey best practices. I encourage you to read it. If everyone used passkeys everywhere, it would save billions of dollars and make life significantly harder for cybercriminals.
Let me share a couple of real-world incidents.
Several years ago, we were onboarding a new client. One frontline employee clicked a phishing link. The attackers deployed a keylogger across the network, which is software that captures every keystroke entered on computers and servers. The malware remained active for four to six months before we discovered it.
We only found it because users were complaining about unusual pop-ups. There was actually a glitch in the malware. This particular client was a manufacturer, and every keystroke was being transmitted to China for months before we shut it down.
Why didn’t they deploy ransomware? Because ransomware wasn’t the goal. The goal was intellectual property theft.
Positive Case Study: Threat Containment
Now for a more positive example.
A client in Woodbury experienced a similar user mistake. Someone clicked a malicious link, and bad things started happening. Fortunately, they had an advanced detection and response solution installed. The affected computer was immediately isolated from the rest of the network before the threat could spread.
Ten days later, the FBI contacted the client and said they had observed one of the company’s computers communicating with infrastructure they were monitoring. The FBI noted that by that point, most organizations would already have been encrypted by ransomware. Instead, the threat had been contained within minutes.
That’s the type of protection every organization needs.
Security Tools and Best Practices
I encourage you to upgrade your detection and response capabilities. There are several products that do this, including Huntress, CrowdStrike, Sophos, and others. The important thing is not just detecting threats but automatically neutralizing them because attacks happen 24 hours a day. Most occur at two o’clock in the morning when nobody is watching.
For organizations that primarily manage security internally, the average time from detection to neutralization is approximately 16 hours. That’s far too slow.
Modern systems can respond in minutes. If someone logs in from Russia using your account, the system can immediately lock the account. If malware begins executing on a workstation, the system can isolate the computer before the threat spreads.
Every organization needs this capability. Cyber insurance carriers increasingly require it.
Email Security and Training
I also encourage you to improve your email security. Most organizations rely solely on Microsoft’s or Google’s built-in filtering. We’ve seen more malicious emails getting through recently. A second layer of email security can dramatically reduce risk.
Security awareness training remains important as well. There’s been debate within the cybersecurity community about whether monthly training is effective, but a large study last year found that organizations conducting ongoing awareness training experienced significantly better outcomes than those that didn’t.
Cyber Insurance Guidance
Now let’s talk about some questions leadership should be asking IT.
Don’t assume your IT team has everything covered. Trust, but verify.
Ask questions like:
- Where are we most at risk?
- Show me the results of our most recent security risk assessment.
- How are our backups protected from deletion or modification?
- How do we neutralize critical alerts 24/7?
- How do we protect user identities?
- What’s our strategy for defending against AI-related threats?
- What are the gaps in our cyber insurance coverage?
- How quickly can we recover from a serious attack and return to normal operations?
Homework and Action Items
For finance professionals, remember that these scams can affect personal finances just as easily as business finances. Someone can pretend to be your internet provider, your utility company, or your municipality and send fraudulent payment requests. Always verify payment changes through another channel.
I’m going to send everyone additional materials, including a checklist. Review it carefully. Print it out if necessary. Discuss these topics with younger family members and elderly loved ones, because they are often the groups losing the most money to scams.
Closing Remarks
Finally, I’m offering free cybersecurity assessments. These are typically 45-minute meetings where we review your cybersecurity posture, cyber insurance, and AI policies. I do these regularly because it’s my way of helping protect the small business community, their employees, and their clients.
As we wrap up, remember this: at some point, all of us learned how to manage money. In 2026, cyber awareness and privacy protection have become equally important life skills.
Please review the materials, share the checklist with your loved ones, especially those who may be vulnerable, and complete the homework.
Thank you very much.