SIM Swap Response for Physicians: Secure Compromised Accounts and Protect Patient Data

Kevin Henry

Incident Response

Published Updated

9 minutes read
Share this article
SIM Swap Response for Physicians: Secure Compromised Accounts and Protect Patient Data

How can a SIM swap compromise a physician’s accounts?

A SIM swap occurs when someone fraudulently transfers your phone number to a SIM or device they control. If successful, they may receive calls and text messages intended for you—including one-time passcodes used to sign in to accounts or reset passwords. A related port-out attack moves your number to another wireless provider. The Federal Communications Commission’s SIM-swap rule notice describes how these attacks can give a bad actor control of a victim’s mobile account.

That access can become a stepping stone to your personal or work email, identity provider, cloud storage, electronic health record (EHR), e-prescribing platform, patient portal, or remote-access tools. If an attacker gets into a system containing patient information, they may be able to view or disclose protected health information (PHI), or change account settings that enable further access.

Text-message authentication is particularly vulnerable when the attacker controls your number. The takeover alone does not establish that any clinical system or patient data was accessed, but it should prompt a timely response and investigation.

What should physicians do immediately after discovering a SIM swap?

  1. Contact your wireless carrier using a trusted phone or other channel. Report suspected SIM fraud, request restoration of your number and service, and ask the carrier to secure the account against further unauthorized changes. Record the report or case number, the time you contacted the carrier, and any account changes the carrier identifies.
  2. Ask about a wireless account lock or freeze. Request protection against SIM changes and number ports, and set or update the carrier account PIN and password. A lock can help block those specific changes, but it does not secure your email, work accounts, or other recovery methods. As of November 20, 2026, FCC compliance dates for adopted carrier requirements to offer account locks are December 17, 2026, for SIM changes and December 18, 2026, for number-porting rules; ask your carrier what protections are available now. See the FCC’s SIM-change compliance notice and number-porting compliance notice.
  3. Notify your organization promptly. Use a known, trusted contact method to reach your IT or security team, privacy officer, or incident-response contact. Follow your organization’s incident response procedures; do not rely on the compromised number to receive verification codes or incident updates.
  4. Secure accounts from a trusted device. Start with your primary email and identity-provider accounts. Change compromised or reused passwords, revoke active sessions and unfamiliar connected applications, and update recovery information. Use a phishing-resistant sign-in method, such as a passkey or security key, where available; otherwise, use an authenticator method not tied to the compromised number if your organization permits it.
  5. Preserve details while acting quickly. Keep carrier alerts, emails, screenshots, timestamps, and descriptions of unusual prompts or account activity. Do not delete suspicious messages or reset a potentially affected device before consulting your organization’s incident responders, unless they direct you to do so.

These steps support SIM fraud reporting and limit the chance that an attacker will use the number to regain access after service is restored.

How should healthcare organizations contain and investigate unauthorized access?

Organizations should treat a physician’s confirmed or suspected SIM swap as a potential security incident and promptly assess whether work accounts could have been reached. The HIPAA Security Rule requires regulated entities to identify and respond to suspected or known security incidents, mitigate harmful effects to the extent practicable, and document incidents and outcomes. HHS explains these duties in its Security Incident Procedures guidance.

Contain access in a coordinated way: disable or secure affected accounts, revoke sessions and tokens, reset credentials, review authentication and recovery settings, and remove unauthorized forwarding rules, delegated access, or connected applications. Coordinate with the carrier and relevant technology vendors when needed. Preserve evidence as practical while containment proceeds, and avoid actions that could disrupt clinical operations without a safe continuity plan.

Assign the investigation to appropriate security, IT, privacy, legal, and clinical-operations personnel. HHS recommends that incident response procedures define responsibilities, methods for determining scope, instructions for managing an incident, and processes for collecting and maintaining evidence. Its cybersecurity incident-response guidance also recommends assessing damage, mitigating vulnerabilities, and preserving relevant artifacts.

Ready to simplify HIPAA compliance?

Join thousands of organizations that trust Accountable to manage their compliance needs.

Get Started Free Today

Which systems and incident data should be reviewed and preserved?

Review systems that use the physician’s phone number for sign-in, account recovery, alerts, or communications. Depending on the organization’s setup, this may include the identity provider and single sign-on platform, email and cloud services, EHR, e-prescribing, patient portals, VPN and remote-access tools, secure messaging, voicemail, and mobile-device management.

Look for sign-ins from unfamiliar devices or locations; password resets; changes to recovery numbers, email addresses, or multi-factor authentication; new sessions or connected applications; altered forwarding rules; unusual record searches or exports; and changes to e-prescriptions or user permissions. Compare activity with the carrier’s SIM-change timeline and the physician’s confirmed actions.

Preserve relevant system and authentication logs, audit reports, carrier notices and case records, incident tickets, screenshots, and forensic artifacts. Record when each item was collected and who handled it, and follow organizational retention and evidence-handling procedures. The HHS guidance on responding to security incidents specifically discusses reviewing audit logs and collecting and preserving data relevant to an investigation.

Document the discovery time, accounts and devices involved, containment steps, systems reviewed, findings, and any remaining uncertainties. A careful unauthorized access investigation helps the organization determine what happened and supports its later privacy and notification decisions.

How should organizations assess potential exposure of protected health information?

A SIM swap does not automatically mean patient data was exposed. The organization should determine whether an unauthorized person accessed an account or system containing PHI, what information was available, and whether it was actually viewed, acquired, used, or disclosed. Include PHI in email, messages, alerts, or files—not only records in the EHR—in the assessment.

Under the HIPAA Breach Notification Rule, an impermissible use or disclosure of PHI is generally presumed to be a breach unless the covered entity or business associate documents a low probability that the PHI was compromised through a risk assessment. HHS identifies four factors: the nature and extent of the PHI, including identifiers; who received or used it; whether it was actually acquired or viewed; and how effectively the risk was mitigated. Review the HHS Breach Notification Rule guidance and document the facts supporting the conclusion.

Assess whether affected information was unsecured protected health information. HHS defines unsecured PHI as information not rendered unusable, unreadable, or indecipherable to unauthorized people using a method specified in its guidance. Encryption may be relevant only if it meets that guidance and the decryption key or process was not compromised; simply describing data as “encrypted” does not resolve the assessment. See HHS guidance on securing PHI.

Consider applicable exceptions, the amount and type of information involved, the scope of access, and mitigation. Consult the organization’s privacy officer and counsel when facts are uncertain. A covered entity or business associate must be able to document why notification was or was not required; HHS describes this documentation responsibility in its Breach Notification Rule guidance.

When do HIPAA breach notification requirements apply?

The HIPAA Breach Notification Rule applies to a breach of unsecured PHI involving a covered entity or business associate. A suspected SIM swap, without evidence of an impermissible use or disclosure of PHI, does not by itself establish that a HIPAA breach occurred. Make and document the breach determination based on the investigation, including any applicable exceptions or a risk assessment demonstrating a low probability that the PHI was compromised.

If notification is required, affected individuals must generally be notified without unreasonable delay and no later than 60 calendar days after discovery. For a breach affecting 500 or more individuals, the covered entity must notify the HHS Secretary without unreasonable delay and within 60 days; for fewer than 500, it may report to HHS annually, no later than 60 days after the end of the calendar year in which the breach was discovered. A breach affecting more than 500 residents of a state or jurisdiction also requires notice to prominent media outlets serving that area. Consult the HHS notification requirements for details.

A business associate must notify the covered entity of a breach at or by the business associate without unreasonable delay and no later than 60 days after discovery; the business associate agreement may require faster reporting. State law, contracts, and organizational policies may also impose obligations beyond HIPAA, so involve privacy and legal leadership early.

In short, restore control of the phone number, secure accounts, involve your organization, preserve evidence, and assess PHI exposure before deciding whether notifications are required.

FAQs.

What should a physician do first after a suspected SIM swap?

Contact the wireless carrier through a trusted channel to report the suspected fraud and regain control of the number. At the same time, promptly notify your organization’s security or IT contact using a known, un-compromised method. Do not use the affected number for verification codes while it may be controlled by someone else.

How can a wireless account lock help prevent another SIM swap?

A carrier’s SIM-change lock or freeze can block or impede unauthorized SIM changes; a number-port lock can help prevent the number from being transferred to another carrier. Ask your carrier to enable available protections and secure the account with a strong PIN. These controls do not protect other accounts or replace strong authentication. FCC compliance dates for adopted requirements to offer these options are December 17, 2026, for SIM changes and December 18, 2026, for number-porting rules, as stated in the FCC’s SIM-change notice and number-porting notice.

Does a suspected SIM swap automatically mean patient data was exposed?

No. It shows that your phone number may have been taken over, but it does not prove that anyone accessed a clinical or other work system containing PHI. The organization should review relevant accounts, activity logs, and records, then document its assessment of whether PHI was accessed or disclosed.

When must patients and federal authorities be notified of a breach?

If a covered entity determines that a breach of unsecured PHI occurred and no exception or documented low-probability determination applies, affected individuals generally must be notified without unreasonable delay and within 60 days of discovery. HHS must be notified within 60 days for breaches affecting 500 or more individuals; for fewer than 500, reporting is generally due within 60 days after the end of the calendar year. Media notice is also required when a breach affects more than 500 residents of a state or jurisdiction. Refer to the HHS HIPAA Breach Notification Rule guidance and consult privacy or legal leadership about the specific incident.

Share this article

Ready to simplify HIPAA compliance?

Join thousands of organizations that trust Accountable to manage their compliance needs.

Get Started Free Today

Related Articles