Blog Cybersecurity
What to Do When a Phishing Email Hits Your Business
Someone in your business just clicked a phishing email. Maybe they entered their password into a fake Microsoft login page. Maybe they opened an attachment and now their machine is doing something strange. Maybe they texted the office manager at 7:14 a.m. with "I think I did something bad." Whatever the specifics, the next hour is the one that matters.
This article is a plain-English response guide for small-business owners and office managers in Central Oregon when a phishing email hits. It covers what to do in the first hour, the first day, and the first week, and what to do before the next one, because there will be a next one.

How to tell if what just happened was actually phishing
Common phishing scenarios we see in Central Oregon small businesses:
- Fake Microsoft or Google login page. "Your password is expiring, click here to renew." The link goes to a page that looks like Microsoft login but is not.
- Fake invoice attachment. "Please review the attached invoice." Opening the attachment installs malware or redirects to a credential harvester.
- CEO fraud. An email that looks like it is from the owner, asking the bookkeeper to wire money immediately. Classic business email compromise.
- Fake DocuSign or signature request. Looks real, asks you to log in, captures your credentials.
- Fake Microsoft Teams or SharePoint link. "A document has been shared with you."
- SMS phishing (smishing). Text claiming to be from your bank, Amazon, UPS or the owner.
- Vishing. Phone call pretending to be IT or the bank asking you to confirm your password.
If you have done any of the following, you may be compromised:
- Entered a password into a page reached from an email link.
- Approved a multi-factor authentication prompt you did not initiate.
- Opened an attachment and seen something strange happen.
- Granted an "app" permission to your Microsoft 365 or Google account from a link.
- Replied to an email requesting bank details, wire instructions or passwords.
- Wired money based on an email request.
The First Hour: What to Do Right Now
Speed matters. Attackers often work automatically: within minutes of getting your password they may be in your mailbox setting up forwarding rules and preparing to send phishing from your own account to your clients.
Step 1: Disconnect from the internet (if a device is involved)
If you clicked something that may have installed malware, disconnect it from the network (unplug the cable, turn off Wi-Fi); don't power it off. This isolates the problem and keeps evidence your IT provider may need.
Step 2: Change the Password Immediately
From a different, trusted device. Change your Microsoft 365 or Google Workspace password. If you reused that password elsewhere (hopefully not), change those too.
Step 3: Review and Revoke Sessions
In Microsoft 365 or Google Workspace admin, sign the account out of all sessions globally. This kicks the attacker out even if they still have the password.
Step 4: Check for New Mail Rules
Attackers commonly add forwarding or auto-delete rules to hide their activity. Check Outlook rules and Microsoft 365 admin for suspicious rules created recently.
Step 5: Check for New "Connected Apps"
In Microsoft 365 or Google Workspace, review the apps and services connected to the account. Revoke anything unfamiliar.
Step 6: Check for New Multi-Factor Devices
Attackers often add their own phone as a second-factor device. Review the account's registered authentication methods and remove unknown devices.
Step 7: Call Your IT Provider
They have access to logs, admin tools and forensic insight you do not. For most incidents this is also the moment to engage them formally, even if you were considering doing it later.
Step 8: Call your bank, if money was involved
If a wire transfer was sent based on a phishing email, call the bank immediately. There is a short window where the wire can sometimes be recalled.

The First 24 Hours: Contain and Assess
In the first day after the incident, the goals shift from immediate response to understanding what happened:
Determine the Attacker's Access
What accounts were compromised? What data was accessible? What systems were connected? Your IT provider pulls admin logs to answer these questions.
Check for Data Exfiltration
Did the attacker download emails, OneDrive files, SharePoint documents? Logs usually show this.
Review Sent Mail
Did the attacker send phishing emails from the compromised account to your clients? If yes, you need to warn clients.
Check Backups
If the incident involves malware or ransomware, make sure your backups are safe and not also compromised.
Document the Incident
Write down what happened, when, who did what, what systems were affected. You will need this for insurance, for your attorney, possibly for regulators.
Notify Your Cyber Insurer
Most policies require you to notify the insurer as soon as practicable. Even if you are not sure the incident is significant, call. Insurers can refuse coverage for late notification, and many policies require you to use their panel vendors, so call before hiring an incident response firm.
Decide on Client Notification
If client data was accessed, you may have a legal and ethical obligation to notify. State breach notification laws (in Oregon, the Oregon Consumer Information Protection Act, ORS 646A.600 et seq.), HIPAA for healthcare, PCI for payment data all have specific triggers.
The First Week: Cleanup and Prevention
Once the immediate incident is contained, the week-long cleanup starts:
- Reset passwords for all users if there is any chance the attack was broader than one account.
- Enable multi-factor authentication everywhere it is not already on. This is the single biggest step you can take to prevent recurrence.
- Review and tighten mail rules, forwarding and permissions across all users.
- Run phishing training for all staff.
- Review Microsoft 365 or Google Workspace security settings and enable features that are off.
- Rebuild any compromised devices from clean images rather than trying to clean them.
- Document the incident response for insurance, legal, and your own files.
- Review your incident response plan based on what you learned.
The Real Cost of a Phishing Incident
What a phishing incident actually costs a Central Oregon small business, in rough buckets:
- Direct financial loss if money was wired or payroll was redirected. Can be anywhere from $0 to catastrophic.
- Response costs: IT provider time, forensic consultant, lawyer, maybe a specialized incident response firm. $5,000 to $50,000 for most small-business incidents.
- Downtime: compromised accounts locked, systems rebuilt, work interrupted. $2,000 to $20,000 for a 15-person business.
- Client notification and PR: if clients were affected. Hard to put a number on.
- Regulatory and legal: if the incident triggered HIPAA, PCI or state privacy law reporting. Can be substantial.
- Insurance deductible: most cyber policies have a $5,000 to $25,000 deductible.
- Insurance premium increase at renewal.
- Reputation and client trust.
For a 15-person Central Oregon business, a serious phishing incident can easily run into the tens of thousands of dollars in total costs. For a business with regulated data (healthcare, legal, financial), it is often considerably more.

How to Prevent the Next One
You cannot prevent all phishing. You can make it dramatically less likely to succeed. The high-return preventive measures:
Multi-Factor Authentication
On Microsoft 365, Google Workspace, QuickBooks, your line-of-business software, your VPN, and anything else that supports it. Mandatory, not optional. Phishing-resistant MFA (FIDO2 security keys, passkeys or Windows Hello for Business) is dramatically better than SMS codes, and better than push or code apps, which a fake login page can still trick users into approving.
Email Filtering
Microsoft Defender for Office 365 or Google's advanced threat protection. Catches a lot of phishing before it reaches your users.
Phishing Training
KnowBe4, Hoxhunt, or similar. $3 to $5 per user per month. Among the most cost-effective security investments for a small business, after MFA. Simulated phishing campaigns teach staff to spot real ones.
Written Procedures for Wire Transfers and Sensitive Requests
Any request for money, bank changes, payroll changes or vendor payment changes must be verified by phone call to a known number, not by replying to the email. Even if it looks like it is from the owner.
Conditional Access Policies
If you are on Microsoft 365 Business Premium, enable conditional access policies that block logins from unusual countries, require MFA for admin accounts, and alert on anomalous activity.
Endpoint Protection
Modern endpoint detection and response, SentinelOne, CrowdStrike, Microsoft Defender for Business, can block malware that gets through filters.
Regular Security Review
Quarterly review of accounts, access, rules, policies and incidents. Boring. Essential.
What NOT to Do
Some common instincts that make things worse:
- Do not try to "clean" a malware-infected device yourself. Reimage from scratch.
- Do not pay a ransom without legal and insurance consultation. Payment often does not recover data and may trigger sanctions regulations.
- Do not delete evidence. Those suspicious emails, logs, mail rules: your IT and your insurer need them.
- Do not forward the suspicious email to a bunch of colleagues to see if they got it too. You just helped it spread.
- Do not hide the incident from your IT provider, insurer or clients to avoid embarrassment. Hiding it will cost you far more later.
- Do not blame the staff member who clicked. People fall for phishing. The response is to improve systems and training, not punish individuals.

Short Version
If someone in your business just clicked a phishing email: disconnect the device, change the password from a different device, revoke the account's sessions, check for suspicious mail rules and connected apps, call your IT provider, and if money was involved call the bank. In the first week, roll out multi-factor authentication, phishing training, written procedures for wire transfers, and modern endpoint protection: these are the measures that prevent the next incident.
If you are dealing with a phishing incident right now, text (541) 239-3338 or call (541) 239-3338. Text us; we'll tell you what to do next. If you want to put the preventive measures in place before an incident, book a free 30-minute security consultation.
