Key takeaways
- Phishing and spoofing was the most reported crime type to the FBI's complaint center in 2024, far ahead of any other category.
- Front office staff see the lures first: fake insurer portals, invoice scams, payroll changes, fake IT calls and urgent requests that appear to come from a doctor.
- Teach one routine: do not click, report it, verify by phone using a number you already have.
- The Security Rule requires security awareness training for the whole workforce, including management, and turnover means onboarding matters most.
Why your front office is the target
Phishing is the most common way attackers get into a small practice, and the numbers show how routine it has become. In the FBI's Internet Crime Complaint Center report for 2024, phishing and spoofing was the most reported crime type, with 193,407 complaints, more than twice the next category[1].
The front office is exposed because of what it does all day. Staff open attachments from patients, insurers, labs and referring offices. They reset portal passwords, update payment details and answer calls from people who claim to be vendors. Attackers write messages that look exactly like that work, and they time them for the moments when staff are busiest: Monday mornings, month end and the last hour before closing.
Messages your staff will actually see
Generic training about Nigerian princes does not help. Show staff the lures that are built for medical offices. Each of these is a fictional example, with the red flags to point out.
- Example: Action required, claim denied. Log in to the payer portal to view the remittance. Red flags: a link that does not match the insurer's real web address, urgency, and a login page that asks for your email password.
- Example: New referral attached for a patient, please review today. Red flags: an unknown sender, an attachment that asks you to enable macros or editing, or a link to a document-sharing site you do not use.
- Example: Your mailbox is full, verify your account to keep receiving messages. Red flags: comes from outside, uses your practice name in an odd way, asks for your password.
- Example: Updated bank details for our next invoice, from a supplier you really use. Red flags: a change of payment instructions by email alone, a lookalike domain, pressure to pay before the usual date.
- Example: Hi, it is Dr. Patel, I am in a meeting, can you buy gift cards for a staff thank-you and send me the codes. Red flags: a personal email address, a request that bypasses normal purchasing, secrecy.
- Example: Payroll update, please confirm your direct deposit details by Friday. Red flags: payroll changes requested by email, a login page that is not your payroll system.
- Example: Your fax could not be delivered, open the attached PDF. Red flags: you did not send a fax, the attachment is an HTML file or a link.
Phishing by phone and text
Not every lure arrives by email. Callers pretending to be from the EHR vendor, the phone company or Microsoft ask staff to install remote access software or read out a code. Tech support scams alone generated 36,002 complaints to the FBI's complaint center in 2024[1]. Text messages that look like they come from a bank, a delivery company or the practice owner follow the same pattern.
Script for an unexpected support call: Thanks for calling. Our policy is that we do not allow remote access or share login codes on inbound calls. I will contact our IT provider on the number we have on file, and they will get back to you if this is genuine.
Make one rule absolute: nobody reads out a multi-factor code, a password or a one-time link to anyone, ever, whoever they say they are. Legitimate IT staff and vendors do not need them.
One routine to teach: stop, report, verify
Stop
If a message is unexpected, urgent or asks for a login, payment or personal details, do not click, open or reply.
Report
Use the report button in your email system if you have one, or forward the message to the address your IT provider gives you. Then delete it.
Verify by phone
If it might be real, call the sender on a number you already have, such as the insurer's number on your contract or the doctor's mobile, never the number in the message.
Speak up fast if you clicked
Tell the practice manager and IT straight away. Change your password if you entered it. A quick report limits the damage; a hidden click multiplies it.
Get feedback
IT or the manager confirms whether it was phishing and thanks the reporter, so people keep reporting.
The fourth step is the one that decides how bad an incident becomes. Staff who fear blame wait and hope. Staff who know that a fast report is praised call within minutes, which is often the difference between one reset password and a network-wide ransomware event.
What HIPAA expects from training
The Security Rule requires a security awareness and training program for all members of the workforce, including management[2]. It lists four implementation specifications as addressable: periodic security reminders, procedures for guarding against malicious software, log-in monitoring and password management[2]. Addressable means you assess them and either implement them or document a reasonable alternative; for phishing, a practice would struggle to justify skipping reminders and malware procedures.
Turnover makes onboarding the most important part of the program. In a May 2026 MGMA poll, 29% of medical group leaders said staff turnover was higher than the year before[3], and front desk and entry-level administrative roles remain among the most common churn points[4]. A new receptionist who starts on a Monday will see their first fake payer email that week.
- Day one: a 15-minute walk-through of the stop, report, verify routine and the no-codes rule, with the examples above.
- Monthly: a two-minute reminder at the staff huddle with one real phishing message the practice received, with names removed.
- Quarterly: a short simulated phishing email, followed by friendly feedback.
- Yearly: a refresher session for everyone, including physicians and owners.
- Every session: a sign-in sheet or system record. Keep training records for at least six years[5].
Running simulations fairly
Simulated phishing emails are a useful way to see whether training works, but they backfire if they feel like traps. Keep them realistic and relevant, avoid lures that mimic real emergencies or pay and benefits news that would upset staff, and never post names of people who clicked. Report results as a team trend, and offer a short refresher to anyone who clicks twice.
Measure two numbers each quarter: the share of staff who clicked, and the share who reported. The second number matters more. A practice where most people report a suspicious message within minutes is well defended, even if a few still click.
Technical backstops
Training lowers the odds of a click. Technical controls limit the damage when one happens anyway. Multi-factor sign-in on email and the EHR is the most valuable control, and the strongest form resists phishing outright. CISA states that the only widely available phishing-resistant authentication is FIDO/WebAuthn authentication, and suggests number matching where phishing-resistant methods are not yet possible[6].
- Turn on multi-factor sign-in for email, the EHR, payroll, banking and remote access.
- Tag external emails with a visible banner.
- Block macros in documents from outside the practice.
- Require a phone call to a known number before any change to payment or payroll details.
- Keep software and browsers updated automatically.
Example: a well-handled click
Example (fictional): A new receptionist at an orthopedic practice clicks a payer remittance link on her third day and enters her email password before the page looks wrong. She remembers the day-one walk-through and tells the office manager within five minutes. IT resets the password, signs her out of all sessions and confirms that multi-factor sign-in blocked the attacker's login attempt.
The manager thanks her in front of the team, without naming the mistake, and uses the email in the next huddle as the month's example. The incident goes in the security incident log with the outcome. The practice treats it as proof that the routine works.
Frequently asked questions
Is phishing training required by HIPAA?
The Security Rule requires a security awareness and training program for the whole workforce. It does not name phishing specifically, but guarding against malicious software and periodic security reminders are part of it, and phishing is the most common route in.
How often should we train?
Train every new hire in the first week, give short monthly reminders and run a fuller refresher at least once a year. Simulations every quarter help measure progress.
Should we discipline staff who click a simulated phishing email?
Usually not for a first click. Use it as a coaching moment. Save formal sanctions for ignoring policy, such as repeatedly sharing codes or concealing a real incident.
What should staff do if they entered a password?
Tell the practice manager and IT immediately, change the password and let IT check for other activity. Speed matters more than anything else.
References
Federal Bureau of Investigation, Internet Crime Complaint Center (IC3) (2024). Internet Crime Report 2024 (opens in a new tab) ↑
Legal Information Institute, Cornell Law School (current). 45 CFR § 164.308 - Administrative safeguards (opens in a new tab) ↑
Medical Group Management Association (MGMA) (2026). Stabilized but not solved: Staff turnover in medical practices looking no better, no worse in 2026 (opens in a new tab) ↑
Medical Group Management Association (MGMA) (2026). Stabilized but not solved: Staff turnover in medical practices looking no better, no worse in 2026 (opens in a new tab) ↑
Legal Information Institute, Cornell Law School (current). 45 CFR § 164.530 - Administrative requirements (opens in a new tab) ↑
Cybersecurity and Infrastructure Security Agency (CISA) (current). More than a Password (multifactor authentication) (opens in a new tab) ↑