How Healthcare Organizations Can Respond to Spear Phishing Targeting Physicians
How can staff verify a suspicious message before responding?
Spear phishing is a targeted attempt to trick someone into revealing credentials, opening a malicious attachment, or taking another action that gives an attacker access. A message may appear to come from a colleague, hospital leader, vendor, or patient—even when the sender’s name and context seem familiar.
Be especially cautious of unexpected electronic health record file-sharing requests, links to sign in, requests for patient information, and messages that pressure you to act quickly. Check the complete sender address and destination of a link without opening it, but don’t treat a familiar display name or a polished message as proof that it is legitimate.
Verify unusual requests using a separate, trusted channel. For example, call the colleague using a number in the organization’s directory, or contact the vendor using a number already on file—not one supplied in the suspicious message. CISA advises staff to report suspicious emails to IT, avoid questionable links, and verify requests before acting in its phishing security guidance.
Use your organization’s approved reporting button or security contact. Don’t reply, download attachments, forward the message to personal email, or enter credentials. Preserve the message for investigation; follow your organization’s instructions about whether to leave it in your inbox or quarantine it.
What should healthcare organizations do after detecting spear phishing?
Activate the organization’s incident-response procedures and report the suspected message promptly to the designated security team. The response should include IT or security staff and, as appropriate, privacy, compliance, legal, clinical, and communications leaders. A suspected phishing message is worth investigating, but it does not automatically mean that a reportable breach occurred.
Preserve the original email and relevant technical details, such as its headers, attachments, links, and time received. Ask the security team to determine who received or interacted with it, whether credentials were submitted, whether a file was opened, and whether similar messages reached other staff. Avoid deleting evidence or launching an independent cleanup that could interfere with the investigation.
Contain any ongoing threat, assess the likely scope, and document the response and its outcome. HHS explains that the HIPAA Security Rule requires covered entities and business associates to identify and respond to suspected or known security incidents, mitigate harmful effects where practicable, and document incidents and outcomes in its October 2026 cybersecurity newsletter.
In parallel, the privacy or compliance team should assess whether protected health information (PHI) was accessed, used, or disclosed improperly. If unsecured PHI may have been involved, follow the organization’s breach assessment and notification process. HIPAA notification obligations depend on the facts; HHS describes the applicable requirements in its Breach Notification Rule guidance. Reporting a cyber incident to CISA does not replace any applicable HIPAA breach notification.
How can incident responders contain compromised physician accounts?
When there is evidence or a reasonable concern that a physician’s credentials were exposed, responders should promptly limit the account’s ability to cause further harm. Depending on the environment and clinical needs, that may mean temporarily disabling or restricting the account, revoking active sessions and tokens, and resetting credentials through a trusted device and approved process.
As part of the credential compromise assessment, review whether an attacker added an unfamiliar multifactor authentication (MFA) method, changed recovery details, created mailbox forwarding rules, or granted access to another user. Remove unauthorized changes, verify the physician’s identity through a trusted channel, and check for suspicious sign-ins or activity in connected systems. CISA recommends re-provisioning suspected or confirmed compromised accounts and auditing access after a phishing incident in its joint phishing guidance.
If the physician clicked a link or opened a file on a workstation, have security staff assess the device and isolate it if needed. Avoid reconnecting it to the network or using it to change passwords until responders advise that it is safe. Coordinate account restrictions with clinical leadership so the organization can maintain patient care through an approved alternate account or emergency access process when necessary.
Ready to simplify HIPAA compliance?
Join thousands of organizations that trust Accountable to manage their compliance needs.
Get Started Free TodayHow can organizations determine which clinical systems and data were affected?
Investigators should build a timeline from the message’s delivery through any sign-ins, account changes, file access, or system alerts. Review available email, identity-provider, endpoint, EHR, and file-sharing audit records. HHS notes that audit logs and regular review of system activity can help regulated entities identify when and how an attacker entered a system and what activities followed in its guidance on security incident procedures.
Determine which systems the physician’s account could access, whether the account was used to view or alter records, and whether data may have been downloaded, shared, or sent outside the organization. Check for unusual mailbox rules, delegated access, new application permissions, changes to patient records, and access to other accounts or services. Preserve logs and evidence according to the incident-response plan.
Document what is known and what remains uncertain, including the affected users, systems, time period, and types of data involved. The privacy team should use those findings to assess whether PHI was involved and whether notification duties apply. Avoid assuming that an attacker accessed every system the physician could reach; base conclusions on available evidence and record the limits of that evidence.
What account safeguards reduce the risk of repeat attacks?
Use multifactor authentication for email, remote access, EHR platforms, and other sensitive services where supported. Prioritize phishing-resistant MFA where practical, especially for privileged accounts. MFA reduces reliance on passwords alone, but it does not prevent every account takeover; staff should report unexpected authentication prompts rather than approve them.
Use unique passwords, role-based access, and only the permissions needed for each job. Review access when staff roles change, remove accounts that are no longer needed, and monitor for unusual sign-ins and account activity. HIPAA’s Security Rule calls for access controls, authentication, and audit controls, while allowing implementation to reflect the organization’s circumstances and risk assessment. See HHS’s Summary of the HIPAA Security Rule.
Strengthen email protections with spam and phishing filters, clear reporting tools, and controls for suspicious attachments and links. Establish a verification step for unusual requests involving credentials, payments, or access to clinical records. Provide practical, recurring education so physicians and staff know how to spot targeted messages and where to report them; make clear that reporting a suspected mistake quickly is more useful than trying to conceal it.
How can healthcare teams maintain clinical operations during recovery?
Use the organization’s downtime response plans if an affected account, EHR, or connected service must be restricted. Identify which services can continue safely, who can authorize emergency access, and how staff should document care while systems are unavailable. Provide a trusted method to confirm patient identity and communicate essential clinical information.
Maintain secure, retrievable backups and test restoration procedures. HHS describes data backup, disaster recovery, emergency operations, and contingency-plan testing as components of HIPAA Security Rule contingency planning in its ransomware and HIPAA guidance. Offline or otherwise isolated clinical data backups can help protect recovery copies from some attacks, but they should be handled under the organization’s security and recovery procedures.
When systems return, validate the restored environment and account access before resuming normal use. Reconcile paper or other approved downtime records into the EHR, check for missing or altered information, and tell staff which systems are safe to use. Keep patient safety, privacy, and continuity of care central throughout the response.
Effective response combines prompt reporting, careful account containment, evidence-based assessment, and tested downtime and recovery processes. These steps help healthcare organizations limit the impact of spear phishing while protecting clinical systems, PHI, and continuity of care.
FAQs
What should a physician do after clicking a suspicious link?
Report it immediately through your organization’s approved security channel, even if you did not enter information or notice a problem. If you entered credentials, approved an unexpected MFA prompt, or opened a file, tell the security team what happened and when. Don’t delete the message or attempt to clean the device yourself; follow instructions about account protection and device isolation.
How should a healthcare organization report suspected spear phishing?
Staff should report the message to the organization’s security or IT team using its approved reporting tool or incident-response contact. The organization should preserve the message, assess who interacted with it, document the investigation, and involve privacy or compliance staff if PHI may be affected. A report to CISA may be considered, but it does not replace any applicable HIPAA breach notification.
How can incident responders protect electronic health record access after an account is compromised?
Responders should restrict the affected account as appropriate, revoke active sessions, reset credentials through a trusted process, and verify MFA and recovery settings. They should review EHR and identity logs for suspicious access, remove unauthorized account changes, and coordinate any temporary access restrictions with clinical leaders to support patient care.
How can healthcare teams maintain access to patient data during system recovery?
Follow downtime response plans that identify approved emergency access, alternative communication, and documentation workflows. Use only authorized sources of clinical information and secure, retrievable backups; avoid personal email or unapproved file-sharing tools. After restoration, validate system integrity and reconcile downtime records into the EHR.
Table of Contents
- How can staff verify a suspicious message before responding?
- What should healthcare organizations do after detecting spear phishing?
- How can incident responders contain compromised physician accounts?
- How can organizations determine which clinical systems and data were affected?
- What account safeguards reduce the risk of repeat attacks?
- How can healthcare teams maintain clinical operations during recovery?
-
FAQs
- What should a physician do after clicking a suspicious link?
- How should a healthcare organization report suspected spear phishing?
- How can incident responders protect electronic health record access after an account is compromised?
- How can healthcare teams maintain access to patient data during system recovery?
Ready to simplify HIPAA compliance?
Join thousands of organizations that trust Accountable to manage their compliance needs.
Get Started Free Today