HIPAA Compliance For Email

HIPAA Compliant Email
Pete Wermter
September 6, 2024

Ensuring HIPAA compliance for email is crucial for healthcare organizations and their business associates when handling Protected Health Information (PHI). HIPAA regulations require strict safeguards, including access controls, audit logs, integrity protections, and transmission security, to prevent unauthorized access and breaches. Encryption plays a key role in securing PHI during email exchanges, and organizations must establish comprehensive email policies aligned with the HIPAA Privacy Rule. Additionally, some state laws may impose stricter requirements, such as obtaining explicit patient consent before using email for PHI. Understanding these regulations is essential for maintaining compliance, protecting patient data, and avoiding costly penalties.

The Health Insurance Portability and Accountability Act (HIPAA) is a complicated law that sets the standards for collecting, transmitting, and storing protected health information (PHI). When information is stored or exchanged electronically, the HIPAA Security and Privacy Rules require covered entities to safeguard its integrity and confidentiality. One of the most common ways that PHI is shared electronically is via email. Understanding how HIPAA email rules apply is essential to meet HIPAA requirements and protect sensitive data.

The HIPAA Email Security Rule

It’s important to note that HIPAA does not require the use of any specific technology or vendor to meet its requirements. Generally speaking, the Security Rule requirements for email fall into four categories:

Organizational requirements state the specific functions a covered entity must perform, including implementing policies and procedures and obligations concerning business associate contracts.
Administrative requirements relate to employee training, professional development, and management of PHI.
Physical safeguards encompass the security of computer systems, servers, and networks, access to the facility and workstations, data backup and storage, and the destruction of obsolete data.
Technical safeguards ensure the security of email data transmitted over an open electronic network and the storage of that data.

Below, we discuss some of the main requirements that apply to email and the steps you need to take to secure email accounts that transmit and store PHI.

HIPAA Compliance Email Rules

While email encryption gets most of the spotlight during discussions on HIPAA compliant email security, HIPAA regulations for email cover a range of behaviors, controls, and services that work together to address eight key areas.

1. Access: Access controls help safeguard access to your email accounts and messages. Implementing access controls is essential to keep out unauthorized users and secure your data. Some key steps to take include:

Using strong passwords that cannot be easily guessed or memorized.
Creating different passwords for different sites and applications.
Using two-factor authentication.
Securing connections to your email service provider using TLS and a VPN.
Blocking unencrypted connections.
Being prepared with software that remotely wipes sensitive email off your mobile device when it is stolen or misplaced.
Logging off from your system when it is not in use and when employees are away from workstations.
Emphasizing opt-out email encryption to minimize breaches resulting from human error.

2. Encryption: Email is inherently insecure and at risk of being read, stolen, eavesdropped on, modified, and forged (repudiated). Covered entities should go beyond the technical safeguards of the HIPAA Security Rule and take steps beyond what is required to futureproof their communications. Some email encryption features to adopt include the following:

The ability to send secure messages to anyone with any email address.
The ability to receive secure messages from anyone.
Implementing measures to prevent the insecure transmission of sensitive data via email.
Exploring message retraction features to retrieve email messages sent to the wrong address.
Avoiding opt-in encryption to satisfy HIPAA Omnibus Rule.

3. Backups and Archival: HIPAA email retention rules require copies of messages containing PHI to be retained for at least six years. To address these requirements, organizations must consider the following:

How are email folders backed up?
Are there at least two different backups at two different geographical locations? The processes updating these backups should be independent of each other as a measure against backup system failures.
Have you maintained separate, permanent, and searchable archives? While the emails should be tamper-proof, with no way to delete or edit them, they should be easily retrievable to facilitate discovery, comply with audit requests, and support business-critical scenarios.

4. Defense: Cyber threats against healthcare organizations are continually increasing. Some may be surprised to learn that HIPAA secure email requirements mandate that organizations take steps to defend against possible attackers. To defend against malicious messages, consider implementing the following technologies:

Server-side inbound email malware and anti-virus scanning to detect phishing and malicious links
Showing the sender’s email address by default on received messages
Email filtering software to detect fraudulent messages and ensure it uses SPF, DKIM, and DMARC information to classify messages
Scanning outbound email
Scanning workstations for malware and virus
Using plain text previews of your messages

5. Authorization: A crucial aspect of HIPAA secure email requirements is ensuring that bad actors cannot impersonate your company or employees. Configuring your domains with SPF and DKIM is essential to verify your identity as an authorized sender of mail from your domains. Also, ensure that users cannot send messages through your email servers without authentication and encryption.

6. Reporting: Setting accountability standards for email security is essential to establishing and improving your HIPAA compliance posture. Some important steps to take include:

Creating login audit trails.
Receiving login failure and success alerts.
Auto-blocking known attackers.
Maintaining a log of all sent messages.

7. Reviews and Policies: Humans are the greatest vulnerability to any security and compliance plan. Create policies and procedures that focus on plugging vulnerabilities and preventing human errors. Some ways to reduce risk include:

Inviting independent third parties to review your email policies and user settings. Fresh, unbiased eyes can weed out issues quickly.
Disallowing the use of public Wi-Fi for devices that connect to your sensitive email.
Creating email policies prohibiting users from clicking on links or opening attachments that are not expected or requested.

8. Vendor Management: Most people do not manage their email in-house. Properly vetting and researching whoever will be responsible for your email services is essential. Perform a yearly review of your email security and stay on top of emerging cybersecurity threats to take proactive action when necessary for sustained HIPAA compliance.

LuxSci’s secure email solutions were designed to help organizations tackle complicated HIPAA email rules. Contact us today to learn more how we can help you secure sensitive data.

Documenting HIPAA Compliance For Email

HIPAA compliant email requires documented proof that privacy and security protocols are being followed. HIPAA email systems must include audit trails, policy records, and incident response documentation that demonstrate appropriate safeguards are in place. Healthcare organizations benefit from clear documentation practices that satisfy regulatory inspectors while supporting daily operations and staff training activities.

Email Policy Documentation and Implementation Records

Healthcare organizations must develop written policies that govern HIPAA email usage according to Privacy Rule and Security Rule standards. Email policies should specify encryption requirements, staff responsibilities for handling patient information, and procedures for responding to security incidents. Policy documents must include implementation dates, responsible staff members, and update procedures when regulations change or organizational needs evolve.

Training records provide evidence that employees understand their HIPAA email obligations and can properly implement security procedures. Documentation should capture completion dates, training topics, assessment scores, and remedial training when staff members fail initial evaluations. Organizations that cannot produce training records struggle to prove employees received instruction appropriate to their job functions and access to patient information.

Business Associate Agreement files cover relationships with email service providers and other vendors handling protected health information. Contract documentation should include security specifications, incident reporting procedures, and audit rights that allow healthcare organizations to verify vendor performance. Without proper agreements, healthcare organizations expose themselves to liability when vendors mishandle patient information.

Risk assessment documentation identifies vulnerabilities in HIPAA email systems and describes corrective measures implemented to address identified problems. Assessment records should include evaluation methods, discovered issues, remediation plans, and verification that fixes have been properly implemented. Many organizations conduct risk assessments but fail to document their findings, making it difficult to track improvements over time.

Audit Trail Management and Log Analysis

HIPAA compliance for email depends on audit logs that track user activities, system access, and message handling throughout email platforms. Audit systems should capture login events, message transmission records, administrative changes, and security alerts that might indicate potential violations. Log protection prevents tampering while ensuring data remains accessible for regulatory review periods.

Monitoring systems can identify unusual email usage patterns that suggest security incidents or policy violations. Alert capabilities should flag failed login attempts, large file transfers, abnormal message volumes, and access from unauthorized locations. Real-time monitoring helps healthcare organizations respond quickly to potential security events before they escalate into breaches.

Log review schedules ensure audit data receives regular examination for potential security incidents or policy violations. Review procedures should specify analysis frequency, responsible personnel, and escalation steps when suspicious activities are discovered. Some entities collect extensive audit data but never review it, missing opportunities to identify security problems early.

Log retention policies balance storage costs with regulatory requirements and potential legal discovery obligations. Retention schedules should consider HIPAA requirements alongside other applicable regulations that might demand longer storage periods.Log data must be destroyed properly when retention periods expire to prevent unauthorized access to historical communications.

Incident Response Documentation and Breach Investigation

HIPAA email incident response procedures must address security events and human errors that might compromise patient information. Response plans should include assessment procedures, containment steps, investigation protocols, and notification requirements for different incident types. Quick response often determines whether a minor security event becomes a reportable breach.

Breach investigation procedures help healthcare organizations determine whether email incidents constitute breaches of unsecured protected health information under HIPAA definitions. Investigation protocols should include evidence collection methods, impact assessments, timeline development, and documentation standards that support internal decisions and potential regulatory reporting. Complex incidents may require external legal and technical expertise.

Notification procedures vary based on incident severity and the type of information potentially compromised. Internal notification processes ensure appropriate personnel are informed about incidents and can participate in response activities. Patient notification requirements create legal obligations that organizations must fulfill within timeframes established by federal regulations.

Corrective action documentation describes measures implemented to prevent similar incidents and demonstrates organizational commitment to improving email security. Action plans should include root cause analysis, remediation steps, implementation timelines, and verification procedures that confirm corrective measures work as intended. Organizations that implement fixes without documenting them may repeat the same mistakes when staff turnover occurs.

Staff Training Documentation and Competency Records

HIPAA email training programs must address technical email operations and regulatory requirements for handling protected health information. Training materials should cover encryption procedures, access controls, incident reporting, and acceptable use policies for email communications. Role-based training ensures different staff groups receive instruction appropriate to their job functions and patient information access levels.

Competency verification procedures help healthcare organizations confirm staff members understand and can properly implement HIPAA email security measures. Verification methods may include written tests, practical demonstrations, and performance monitoring that evaluate staff compliance with email policies. Training programs without competency verification cannot prove that employees actually learned the required information.

Refresher training schedules ensure staff members stay current with evolving threats, policy updates, and new email system features. Training frequency should consider technology change rates, emerging security threats, and organizational policy modifications. Staff members who received training years ago may not remember procedures or may have developed bad habits that compromise security.

Training effectiveness measurement helps healthcare organizations evaluate whether HIPAA email training programs meet learning objectives. Measurement approaches may include before and after assessments, incident rate analysis, and feedback collection that provide insights into training quality. Organizations should adjust training content based on effectiveness data to ensure educational efforts support compliance goals.

System Configuration and Change Control Records

Email system configuration documentation provides detailed records of security settings, access controls, and integration setups that support HIPAA compliance for email. Configuration records should include baseline security settings, approved modifications, and verification procedures that confirm systems maintain appropriate security levels. System administrators need current configuration records to troubleshoot problems and maintain security standards.

Change management procedures ensure modifications to HIPAA email systems receive proper evaluation, testing, and documentation before implementation. Change processes should include security impact assessments, testing protocols, approval workflows, and rollback procedures that minimize risks to email security. Changes made without proper documentation and approval create security vulnerabilities that may not be discovered until a breach occurs.

Version control procedures help healthcare organizations track changes to email system configurations and maintain the ability to restore previous settings when problems occur. Version documentation should include change descriptions, implementation dates, responsible personnel, and verification that modifications function properly. Organizations need version control to understand how their systems evolved and to reverse changes that cause problems.

Patch management procedures ensure email systems receive security updates promptly while maintaining system stability and compliance. Patch processes should include vulnerability assessment, testing protocols, deployment schedules, and verification that updates install correctly. Delayed patching leaves systems vulnerable to known exploits that criminals actively target.

HIPAA Compliant Email Vendor Management and Contract Documentation

Email service provider relationships must include Business Associate Agreements that specify security requirements, compliance obligations, and incident reporting procedures. Contract documentation should cover data handling standards, audit rights, and termination procedures that protect healthcare organizations when vendor relationships end. Regular vendor performance reviews ensure service providers continue meeting contractual obligations.

Vendor compliance verification ensures email service providers maintain their obligations under Business Associate Agreements and healthcare security standards. Verification activities may include security certification reviews, audit report analysis, and compliance documentation that demonstrates ongoing adherence to healthcare privacy requirements. Healthcare organizations that trust vendors without verification may discover compliance failures only after incidents occur.

Service level agreement documentation defines performance expectations, availability targets, and response times for email services and security incidents. Agreement records should include uptime guarantees, incident response procedures, and remediation steps when service levels are not met. Performance tracking helps healthcare organizations evaluate vendor reliability and compliance with contractual commitments.

Vendor communication records document interactions about security updates, policy changes, and compliance requirements that affect email services. Communication logs should include update notifications, compliance discussions, and resolution of security concerns that arise during vendor relationships. Good communication records help resolve disputes and ensure both parties understand their obligations when changes occur.

Pete Wermter

As a marketing leader with more than 20 years of experience in enterprise software marketing, Pete's career includes a mix of corporate and field marketing roles, stretching from Silicon Valley to the EMEA and APAC regions, with a focus on data protection and optimizing engagement for regulated industries, such as healthcare and financial services. Pete Wermter — LinkedIn

Get in touch

Find The Best Solution For Your Organization

Talk To An Expert & Get A Quote

First Name

Last Name

Work Email

Phone

Company

Type of Inquiry

Company Size

Message (optional)

Acceptance

I consent to be contacted by LuxSci for this inquiry and other relevant content, products, and services. You may unsubscribe from these communications at any time. We're committed to your privacy. For more information, check out our Privacy Policy.

A member of our staff will reach out to you

Search

Get Your Free E-Book!

LuxSci High Email Deliverability Best Practices Paper

What you’ll learn:

What Is Secure Email? The Complete Guide for Healthcare Organizations

July 29, 2026
Pete Wermter

Key Takeaways

Secure email is not the same as “email with encryption turned on.” True secure email requires enforced automated encryption, a signed BAA, access controls, audit logs, and documented processes — not just a feature toggle.
Standard email platforms like Gmail and Microsoft 365 rely on opportunistic TLS by default, which can silently fall back to unencrypted delivery if the recipient’s server doesn’t support encryption.
HIPAA’s encryption safe harbor means a misdirected but properly encrypted email is a non-event. The same email sent unencrypted is a presumed breach unless a risk assessment shows otherwise.
A signed Business Associate Agreement (BAA) with your email provider is non-negotiable — without one, you cannot legally send or store PHI through that provider.
The proposed 2025 HIPAA Security Rule update, planned for finalization in 2027, would make encryption of ePHI in transit and at rest a mandatory requirement rather than “addressable,” raising the stakes for organizations still relying on opportunistic TLS.

Best for: Healthcare IT Directors, Compliance Officers, Privacy Officers, and Marketing Managers at provider, payer, and supplier organizations that handle protected health information (PHI).

In healthcare IT, the term “secure email” gets thrown around loosely. Vendors slap the label on anything with a padlock icon, and internal teams often assume that because their provider offers TLS, they’re covered. They’re not, and the gap between what’s assumed and what’s actually required is where data breaches occur and HIPAA violations happen.

This guide breaks down exactly what secure email means from a technical and regulatory standpoint, why the email platform your staff uses every day probably isn’t compliant out of the box, and what to look for when evaluating a provider that needs to protect PHI at scale. If you want the full picture of what compliance requires beyond email specifically, our HIPAA Compliance Checklist is a useful companion read.

What Is Secure Email?

Secure email refers to an email system that protects the confidentiality, integrity, and availability of message content — specifically PHI — through a combination of technical safeguards and contractual protections. It’s not a single feature. It’s a stack of controls working together.

At minimum, secure email in a healthcare context includes:

Enforced encryption in transit, so messages can’t fall back to plaintext delivery
Encryption at rest, so stored messages remain protected on the server
Authentication protocols (SPF, DKIM, DMARC) that prevent spoofing and impersonation
Access controls and audit logs that track who accessed what, and when
A signed Business Associate Agreement (BAA) with the email provider

The distinction that trips up most organizations is this: encryption is a component of secure email, not the whole picture. A provider can offer encryption and still fail to meet HIPAA requirements if that encryption isn’t enforced, if there’s no BAA in place, or if audit logging doesn’t exist. Secure email is the combination of all these pieces functioning as a system, which is why it needs to be evaluated holistically rather than checked off feature by feature.

For healthcare provider, payer, and supplier organizations, this matters because email remains one of the highest-volume channels for PHI exposure, from clinical referrals to patient billing statements to routine staff communication. Getting the definition right is the first step toward closing the compliance gap.

Why Standard Email Is Not HIPAA-Compliant

Many healthcare organizations run on Gmail (Google Workspace) or Microsoft 365, and most assume they’re protected because encryption exists somewhere in the stack. That assumption is the single most common — and most dangerous — misconception in healthcare email security.

Here’s the problem: standard email services use opportunistic TLS by default. TLS is attempted between mail servers, but if the receiving server doesn’t support it, the message is delivered anyway — unencrypted, in plaintext. Neither the sender nor the recipient typically sees a warning. The email just goes through.

This isn’t a hypothetical edge case. IT professionals managing healthcare email infrastructure have flagged this exact issue directly: opportunistic TLS is often enabled by default and creates a false sense of security, since it offers no guarantee that a given message, including one containing PHI, won’t be transmitted in plaintext if the recipient’s mail server doesn’t support encryption. Organizations assume they’re protected simply because TLS is technically “on,” without realizing it isn’t enforced.

That gap has real consequences under HIPAA. The Security Rule currently treats transmission encryption as an “addressable” safeguard, meaning covered entities can, in theory, implement an equivalent alternative measure instead. In practice, regulators and auditors from the Office for Civil Rights (OCR) expect enforced encryption as the standard of care. “Addressable” has never meant optional — it means an organization needs a documented, defensible reason if it isn’t doing enforced encryption, and few reasons hold up under scrutiny. Finally, under OCR’s proposed changes to the HIPAA Security Rule for ePHI, scheduled for final publication in July 2027, email encryption moves from addressable to mandatory.

Beyond the encryption gap, standard consumer and even most business email plans typically lack:

A BAA that’s actually offered and signed (available on some enterprise tiers, but not automatic)
Enforced access controls beyond basic password authentication
Audit logging sufficient to meet HIPAA Security Rule requirements
Built-in encryption at rest guarantees for stored messages

None of this means Gmail or Microsoft 365 are inherently insecure products. It means their default configuration is built for general business use, not for an environment where every misrouted or intercepted message carries breach notification liability. Making either platform HIPAA-appropriate requires layering on additional tools, policies, and critically, a provider relationship that includes a signed BAA covering the exact services in use.

The Technical Components of Secure Email

Secure email is built upon five technical layers. Understanding each one, and where it fails in standard email, clarifies exactly what a compliant solution needs to deliver.

Encryption in Transit (TLS)

Transport Layer Security (TLS) encrypts the connection between mail servers as a message travels from sender to recipient. There are two flavors, and the difference between them is the crux of most healthcare email compliance failures:

Opportunistic TLS attempts an encrypted connection but falls back to unencrypted delivery if the receiving server doesn’t support it. This is the default across most consumer and business email platforms.
Enforced TLS requires an encrypted connection for delivery to succeed. If encryption can’t be established, the message fails to send rather than going out in plaintext, or a link to secure portal can be sent to securely access the information.

HIPAA’s Security Rule lists encryption as addressable, but enforced TLS has become the de facto standard that auditors and OCR expect from covered entities and business associates handling PHI over email. As one healthcare IT professional put it while debating this exact tradeoff internally: the goal is to require TLS for all outbound email and then document the remaining controls around it, treating enforced TLS as the technical baseline, with policy and process built on top.

Encryption at Rest

Transit encryption only protects a message while it’s moving. Once it lands on a mail server — sender’s outbox, recipient’s inbox, backups, archives — it needs to remain encrypted in storage. This is encryption at rest, and it’s where many organizations underestimate their exposure.

Encryption in transit alone offers zero control over a message after it’s been delivered. If the destination server isn’t itself encrypting stored data, or if a backup snapshot is taken without encryption, PHI sitting in an inbox is exposed regardless of how securely it arrived. HIPAA’s Security Rule requires safeguards for ePHI both in transit and at rest, a compliant secure email provider needs to guarantee both, not just one.

End-to-End Encryption (S/MIME, PGP)

End-to-end encryption (E2EE) encrypts message content itself, not just the connection it travels over — meaning even the email provider can’t read the content. Two standards dominate here:

S/MIME uses certificate-based encryption and is common in enterprise environments, such as healthcare, particularly where organizations already manage a public key infrastructure.
PGP (Pretty Good Privacy) uses a public/private key model and is more common in technical or security-conscious communities, though it’s less frequently deployed at scale in healthcare due to key management complexity.

E2EE isn’t a baseline requirement for every PHI-containing email, enforced TLS plus encryption at rest satisfies most use cases. But it becomes necessary for especially sensitive communications, cross-organization data sharing where you don’t control the recipient’s infrastructure, or when a business associate agreement specifically requires it.

Authentication (SPF, DKIM, DMARC)

These three protocols work together to prevent domain spoofing and email impersonation, a growing attack vector against healthcare organizations specifically, given how often phishing campaigns impersonate providers, payers, or patients.

SPF (Sender Policy Framework) specifies which mail servers are authorized to send email on behalf of a domain.
DKIM (DomainKeys Identified Mail) adds a cryptographic signature verifying a message wasn’t altered in transit.
DMARC (Domain-based Message Authentication, Reporting & Conformance) tells receiving servers what to do when SPF or DKIM checks fail, and provides reporting visibility.

Without these configured correctly, an organization’s domain can be spoofed to send convincing phishing emails to patients or staff, creating a security failure that compounds the compliance risk of email interception.

Digital Signatures

Digital signatures verify sender identity and confirm a message hasn’t been tampered with between sending and receipt. Paired with encryption, they close the loop on message integrity, confirming not just that content was protected, but that it came from who it claims to have come from and arrived unaltered.

Standard Email vs. Secure Email: Feature Comparison

Feature	Standard Email	Secure Email (HIPAA-Compliant)
Encryption in Transit	Opportunistic TLS — attempted but not enforced	Enforced TLS — connection fails if encryption unavailable, can include delivery via secure portal option
Encryption at Rest	Not guaranteed; provider-dependent	Required — server-side encryption of stored messages
End-to-End Encryption	Not available	Supported via S/MIME and/or PGP
Digital Signatures	Not available	Included — verifies sender identity and message integrity
Authentication (SPF / DKIM / DMARC)	Optional, rarely enforced	Required — spoofing and impersonation protection
Business Associate Agreement (BAA)	Not provided on standard plans	Required — must be signed before sending PHI
Audit Logs	Basic or none	Full audit trail — required under HIPAA Security Rule
Access Controls	Basic password only	Role-based access, MFA, admin controls
Misdirected Email	Reportable HIPAA breach	Non-reportable if properly encrypted (safe harbor)
HIPAA Compliant by Default	No	Yes

What Makes Email HIPAA-Compliant Specifically

Technical safeguards alone don’t make email HIPAA-compliant. Compliance is a combination of technology, contracts, and documented processes — all four need to be in place simultaneously. This includes:

A signed BAA with your email provider – Any vendor that transmits, processes, or stores PHI on your behalf is a business associate under HIPAA, and business associates are legally required to sign a BAA before handling that data. Email providers have persistent access to ePHI — even end-to-end encrypted messages pass through their infrastructure at some point — which makes this requirement absolute, not situational. If a provider won’t sign a BAA, using them to send or store PHI isn’t a compliance risk you can mitigate; it’s a violation from the start.

Encryption as an addressable safeguard – Under 45 CFR §164.312(e)(2)(ii), the HIPAA Security Rule lists encryption of ePHI in transit as “addressable” rather than strictly “required.” In practice, this doesn’t mean optional, it means an organization must implement it, or document and justify an equivalent alternative safeguard. Enforced encryption has become the expected standard, and with the newly proposed HIPAA Security Rule planned for July 2027 publication, NPRM would formalize that expectation by making encryption of ePHI in transit and at rest mandatory rather than addressable. Organizations still relying on opportunistic TLS as their “equivalent alternative” should treat this as a closing window.

Access controls and audit logs – HIPAA requires the ability to track who accessed PHI, when, and what they did with it. This means role-based access permissions, multi-factor authentication, and a complete, retained audit trail — not just for compliance reporting, but for identifying and responding to incidents quickly.

The encryption safe harbor – This is one of the most consequential, and most underused, provisions in HIPAA. If PHI is sent via properly encrypted email and ends up misdirected to the wrong recipient, it is not a reportable breach under the Breach Notification Rule, because the encrypted content is considered unreadable and therefore not “unsecured PHI.” The exact same misdirection with unencrypted email is a reportable breach, triggering notification obligations to the individual and to HHS/OCR. Encryption isn’t just a security best practice here, it’s the line between a non-event and a formal breach investigation.

HITRUST certification as a trust signal – When evaluating vendors, HITRUST CSF certification is a strong external indicator that a provider’s security controls have been independently assessed against a recognized healthcare-specific framework. It’s not a HIPAA requirement in itself, but it meaningfully reduces the diligence burden on your side when vetting a provider.

Types of Healthcare Email That Must Be Secure

Not all internal debate here is about “should we secure email” — it’s about scope. Which specific email flows actually carry PHI, and therefore need to run through a compliant channel? In practice, the answer is broader than most teams initially assume.

Screenshot 2026 07 29 at 9.47.13 AM What Is Secure Email? The Complete Guide for Healthcare Organizations

The common thread: if a message references anything that could identify a patient in connection with health information — a name next to a diagnosis, an account number tied to a service date, an annual test reminder — it needs to move through a secure channel, regardless of whether it’s clinical, financial, or administrative in nature.

How to Evaluate a Secure Email Provider for Healthcare

Vendor evaluation in this category tends to go one of two ways: teams either take a provider’s “HIPAA-compliant” label at face value, or they get buried in RFP questions without knowing which answers actually matter. Ask these key questiosn to focus the evaluation on what’s operationally and legally significant.

“Does the provider sign a BAA? This is the first filter, not the last. If a vendor won’t sign a BAA — or offers a heavily limited one — everything else is irrelevant. Some organizations go a step further and negotiate indemnity or make-whole clauses into the BAA itself, seeking financial protection beyond the baseline liability allocation.

What encryption methods are supported? Confirm specifically whether the provider offers TLS only, or also supports S/MIME and/or PGP for end-to-end encryption where needed. TLS-only coverage is sufficient for most standard PHI communication; organizations with cross-border data sharing or especially sensitive use cases may need E2EE options available.

Is encryption enforced or opportunistic? This is the single most important technical question to ask directly, in those terms. A vendor that describes its encryption vaguely, without distinguishing enforced from opportunistic delivery, hasn’t answered the question. Push for specifics.

How are large attachments handled? Lab results, imaging files, and clinical documents often exceed standard attachment size limits. Confirm the provider has a secure, compliant method for large file transfer that doesn’t force users onto an unencrypted workaround.

What audit logging and reporting capabilities exist? You need visibility into delivery, access, and any failed encryption attempts, not just a generic sent/received log. Ask whether logs are retained for a period consistent with your organization’s HIPAA documentation requirements.

Do they support high-volume transactional email? Appointment reminders, billing notices, and patient communications at scale require infrastructure built for volume without sacrificing per-message compliance. Confirm the provider’s platform is built for this your specific pattern, not just person-to-person messaging.

Is the platform US-based with US data residency? For many healthcare organizations, where data physically resides — and under which jurisdiction — is a material factor in vendor risk assessment, particularly for payers and larger provider organizations with strict data governance policies.”

One operational factor worth weighing alongside these questions: secure email portals — the kind that require recipients to click through to a separate web page to read a message — solve the encryption problem but often create a real adoption problem. IT teams have reported a direct conflict between phishing-awareness training and portal-based workflows: staff and patients trained not to click suspicious links in emails are, understandably, reluctant to click the “secure link” a portal email contains. This is a legitimate reason many organizations increasingly prefer platforms that enforce encryption transparently in the background — like LuxSci’s SecureLine encryption technology — rather than routing every message through a separate portal experience.

Secure Email Checklist for Healthcare Organizations

Every safeguard covered in this guide comes down to a handful of concrete, verifiable actions. Use the checklist below as a working reference for what needs to be in place across your legal agreements, technical controls, and internal processes. This is not a one-time setup task, but something worth revisiting as your email volume, vendors, and regulations evolve. Share it across your compliance and IT teams as a starting point for an internal audit.

Legal and Contractual – BAA signed with email provider and all third-party vendors handling PHI.
Encryption – Forced TLS, not opportunistic only for emails in transit and all stored data encrypted with AES-256 bit encryption.
Access and Audit – Unique user IDs, role-based access, and login monitoring with advanced MFA enabled for all email accounts; audit logs active and maintained.
People and Processes – Staff trained in PHI handling, established breach response plan, annual email security policy review.

What Should I Do Now?

Secure email isn’t a single setting you switch on — it’s a combination of enforced encryption, a signed BAA, access controls, and documented process working together. Get any one piece wrong, and the rest doesn’t hold up under an OCR audit or a breach investigation.

If your organization is still relying on opportunistic TLS, an unsigned or incomplete BAA, or a patchwork of workarounds to move PHI through email, now is the time to close that gap, especially with the proposed 2025 HIPAA Security Rule update poised to make encryption a mandatory requirement rather than an addressable one in 2027.

Below are three ways you can continue your journey to securing your healthcare email:

Explore LuxSci’s SecureLine encryption technology to see how automated encryption, enforced TLS, and a signed BAA work together — no complex configuration required.
Read our HIPAA Compliance Checklist to understand the full scope of what your organization needs to have in place beyond email.
Stay ahead of the new regulation with Email Encryption Under the New HIPAA Security Rule for a closer look at what the mandatory encryption shift means for your organization.

FAQs

1. Is email HIPAA compliant?

Email can be HIPAA compliant, but only when the right safeguards are in place — enforced encryption, a signed BAA with your email provider, access controls, audit logs, and staff training on PHI handling. Standard email without these safeguards is not compliant.

2. Do I need to sign a BAA with my email provider?

Yes. Email providers have persistent access to ePHI — even encrypted messages pass through their servers — making them Business Associates under HIPAA. A signed BAA is required. If your provider won’t sign one, you cannot legally use them to send or store PHI.

3. What is the difference between opportunistic TLS and enforced TLS — and which does HIPAA require?

Opportunistic TLS attempts encryption but falls back to plaintext if the recipient’s server doesn’t support it. Enforced TLS stops delivery rather than sending unencrypted. HIPAA’s Security Rule treats transmission encryption as an addressable specification, in practice, enforced TLS is the standard auditors and OCR expect. The proposed 2025 HIPAA Security Rule NPRM would make encryption of ePHI in transit a mandatory requirement in 2027.

4. What happens if I send PHI in an unencrypted email?

It is an impermissible disclosure under HIPAA’s Privacy Rule and triggers the Breach Notification Rule, requiring you to notify the individual and HHS/OCR within 60 days. Penalties range from $100 to $50,000 per violation. Had the email been properly encrypted, the same incident would qualify for HIPAA’s encryption safe harbor, meaning no notification required.

5. Is Gmail or Microsoft 365 HIPAA compliant for sending patient emails?

Neither is compliant in their default configuration. Both use opportunistic TLS, meaning PHI can be sent in plaintext if the recipient’s server doesn’t support encryption. A signed BAA is available on enterprise plans but doesn’t close the technical gap alone. A purpose-built HIPAA-compliant email platform is the reliable solution.

HIPAA Security Rule Update: Email Encryption Rule Delayed to 2027

July 22, 2026
Pete Wermter

If you’ve been waiting for the final word on the new HIPAA Security Rule before you touch your email encryption strategy, you now have an official reason to keep waiting.

Our advice: Don’t do it.

What is the new HIPAA Security Rule for ePHI?

The Department of Health and Human Services’ Office for Civil Rights had targeted May 2026 for a final rule implementing the most significant update to the HIPAA Security Rule in over two decades. The proposal eliminates the “addressable” standard and makes encryption of ePHI in transit and at rest mandatory for every covered entity and business associate. That deadline came and went quietly. Now we know why: an updated federal regulatory agenda shows OCR’s timeline has moved to July 2027, with the rule-making downgraded from “final rule stage” to “long-term action.” OCR is still working through more than 4,700 public comments on the January 2025 proposal.

For an industry that had been expecting a tighter deadline, a year-plus delay is the kind of news that invites a collective exhale — and a shelved project plan. At LuxSci, we think that would be a mistake, for three reasons:

The current rule already requires you to address encryption. “Addressable” was never “optional.” It has always meant you must implement the safeguard, implement an equivalent alternative, or document in writing why neither is reasonable for your organization. Most healthcare organizations have never done that documentation rigorously, and OCR’s existing enforcement authority applies today, not in 2027.
Breach costs haven’t waited for the rule. IBM’s 2025 Cost of a Data Breach Report puts the average healthcare breach at $7.42 million, still the highest of any industry. At the same time, email remains the number one attack vector into healthcare organizations. None of that risk is paused by a regulatory delay.
Delay is not withdrawal. OCR has not signaled it’s abandoning the encryption mandate, only that it’s taking longer to finalize it. Organizations that build now toward the standard already proposed will be ahead (and more secure) regardless of exactly when, or in what final form, the rule lands. Organizations that wait risk a compressed scramble once it does.

What should healthcare IT and compliance leaders actually do with this news?

Reevaluate your ePHI security posture, recalibrate its urgency, and use the extra runway to do the job right, instead of racing against a deadline. This includes:

Getting a real inventory of where ePHI moves by email today, inbound and outbound, and where encryption is inconsistent or absent.
Closing the documentation gap on “addressable” now, while you have time to do it well rather than defensively.
Pushing your email vendor for concrete answers on encryption standards, MFA enforcement, audit logging, and breach notification — the same technical controls the proposed rule would make mandatory.
Building (or updating) a written, enforcement-ready posture: policies, vendor agreements, certifications and verifications, test results, and training records that would hold up under an OCR investigation today, not just in a future compliance deadline.

Get LuxSci’s new Definitive Guide on the new HIPAA Security Rule

From Addressable to Mandatory: Email Encryption Under the New HIPAA Security Rule provides the latest update on the rule, what it means for healthcare email encryption, and what you can do now to properly prepare for what’s coming in 2027. The guide also includes an interactive scorecard that lets you evaluate your current email set up and vendor across seven security and compliance dimensions in under two minutes, no email address required.

You can read the guide here: From Addressable to Mandatory: Email Encryption Under the New HIPAA Security Rule

If you want a second set of eyes on where your organization stands, our team offers a free 30-minute compliance assessment of your current email environment against the proposed rule’s requirements.

Reach out today and schedule a call.

HIPAA Security Rule Email Encryption Requirements

July 8, 2026
Tom Deeb

Your Email Platform Is Becoming Critical Healthcare Infrastructure

July 1, 2026
Pete Wermter

Most healthcare organizations view email as a utility, a necessary tool for sending messages between staff, communicating with patients, sending out newsletters, connecting workflows, and so on. Historically, IT teams focused on keeping it running, security teams worried about phishing, and compliance teams made sure sensitive emails were encrypted.

Today, however, that view is rapidly becoming outdated.

Email has evolved into one of healthcare’s most critical digital infrastructure components, and also one of it’s biggest security threats. It’s a core channel for patient engagement, care coordination, revenue cycle operations, digital marketing, remote monitoring, and increasingly, AI-powered communications. The organizations that recognize this shift are building communications platforms designed for security, performance, automation, and growth. With the new HIPAA Security Rule requiring email encryption on the horizon, those companies that don’t may find themselves constrained by systems that were never intended to support modern healthcare.

Email Is No Longer Just a Messaging Tool

Healthcare organizations now depend on email to support dozens of mission-critical workflows every day.

Patients receive appointment reminders, registration instructions, imaging results, billing notifications, Explanation of Benefits (EOBs), prescription updates, preventive care reminders, patient education, and post-discharge follow-up. Marketing teams deliver personalized wellness campaigns and service line promotions. Clinical systems generate transactional notifications. Revenue cycle teams rely on secure digital communications to accelerate payments and reduce paper costs.

For many organizations, mission-critical patient communications flow through email every month.

When viewed collectively, email is more than a simple communications channel. It has become operational infrastructure with high levels of security needed and increasing compliance requirements.

The Stakes Continue to Rise

As healthcare becomes more digital, every communication carries greater business and clinical importance.

A delayed billing email may postpone payment. A failed appointment reminder can increase no-show rates. An undelivered care management message may impact patient outcomes. A misconfigured security policy can expose protected health information (PHI). Poor deliverability can undermine expensive patient engagement initiatives before they ever reach the inbox.

These are no longer isolated IT issues. Email can affect revenue, patient satisfaction, operational efficiency, compliance, and organizational reputation.

Today’s healthcare leaders require email infrastructure to provide the same reliability and visibility they demand from electronic health records, identity management systems, and other core infrastructure.

AI Is Raising the Bar Even Higher

There’s little doubt that artificial intelligence (AI) promises to transform patient communications.

Healthcare organizations everywhere are exploring AI-generated patient education, personalized outreach, intelligent scheduling, multilingual communications, and automated follow-up programs.

But AI also increases the importance of the underlying communications infrastructure.

Generating more personalized emails means little if organizations cannot:

Automatically protect PHI.
Apply consistent security policies.
Maintain complete audit trails.
Deliver messages reliably.
Integrate with EHRs, RCM and CRM platforms, and customer data platforms.
Demonstrate compliance during an audits.

In many ways, AI amplifies both the opportunities and the risks. Your email platform can help determine whether AI initiatives succeed or create new compliance and operational challenges.

Infrastructure Matters More Than Features

Healthcare buyers have traditionally evaluated email platforms based on individual features such as encryption, spam filtering, or secure portals.

Those capabilities remain important, but they no longer tell the whole story.

Today’s healthcare organizations should be evaluating communications platforms the same way they evaluate any mission-critical infrastructure.

Questions increasingly include:

Can it support both transactional and marketing communications?
Does it automatically enforce security policies without relying on user decisions?
Can it integrate with EHRs, CRM systems, CDPs, and business applications?
Will it scale during peak communication periods?
Does it provide detailed audit logging and reporting?
Can it adapt as regulatory expectations evolve?
Does it maintain high deliverability at enterprise scale?
Does it support single-tenant dedicated infrastructure for high performance and increased security?

These infrastructure characteristics often determine long-term success far more than any single feature comparison.

Email and the Future Of Secure Healthcare Communications

Healthcare is steadily moving toward a world where nearly every patient interaction is digital, personalized, and data-driven.

Healthcare leaders often ask whether they need a more secure email solution. That may be the wrong question.

The better question is whether their communications infrastructure is ready for where healthcare is headed over the next decade.

If you want talk about the future of your healthcare email infrastructure, reach out today and schedule a 30-minute assessment call with our experts.

Set Up a Call

How are B2B and B2C Strategies Used in Healthcare Marketing?

December 5, 2024
Erik Kangas

Healthcare marketing employs distinct B2B and B2C strategies to reach different audiences within the medical and healthcare product and services sectors. B2B marketing targets healthcare providers, medical suppliers, and insurance companies, while B2C marketing focuses on patient outreach and service promotion. Both approaches require specialized marketing tactics that comply with healthcare regulations, such as HIPAA, while meeting business objectives.

Marketing to Healthcare Businesses

Medical device manufacturers, pharmaceutical companies, and healthcare technology providers develop B2B marketing plans to reach hospitals, medical practices, and other healthcare organizations. These campaigns focus on technical specifications, return on investment, and operational benefits. Marketing teams create detailed product documentation, research papers, and case studies to support their sales efforts. Teams usually participate in healthcare trade shows, industry conferences, and professional networking events to build relationships with potential buyers, as well as deploying email campaigns and social media engagement programs. B2B healthcare marketing requires extensive knowledge of medical procurement processes, insurance reimbursements, compliance requirements, and industry standards.

Patient-Focused Marketing Strategies

B2C healthcare marketing connects medical providers, payers and suppliers with potential patients through direct outreach and service promotion. Marketing campaigns display treatment options, medical expertise, and patient benefits. Organizations develop educational content about health conditions, preventive care, and treatment outcomes, and typically carry out email campaigns and engagements programs to connect with targets. They use patient testimonials and success stories to build trust with prospective patients and customers. Marketing content and materials should be education and informative, addressing common health concerns and explaining medical procedures and advice in accessible language. Patient engagement and response rates are tracked by teams to measure campaign effectiveness.

Channel Selection and Message Development

Healthcare organizations select different marketing channels based on their B2B or B2C audience. B2B campaigns utilize secure email campaigns, industry websites and media outlets, and LinkedIn for content distribution. B2C marketing can also include advertising, social media awareness and engagement, and consumer health websites. Marketers should develop separate content strategies for each audience type. B2B content emphasizes technical details and business value, while B2C messages focus on patient experience and better health outcomes. Channel selection, such as email and/or patient portals, considers audience preferences, regulatory requirements, and cost-effectiveness.

Building Professional Networks

B2B healthcare marketing can contribute to building relationships through professional networking and industry partnerships. Organizations develop referral networks with other healthcare providers and supplest, and maintain connections with payers, such insurance companies and government health plans. Marketing teams may organize educational events for healthcare professionals, including digital marketing and CX teams, and participate as members in industry associations, where they create partnership programs that benefit both organizations and their patients. These relationships help healthcare providers expand their service reach and improve awareness. Marketing efforts focus on maintaining long-term business relationships that generate consistent referrals and business opportunities.

Managing Patient Relationships

B2C marketing in healthcare focuses on patient acquisition and retention through personalized communication over channels like email and text. Organizations develop patient engagement programs that include regular health updates, marketing promotions, plan renewals, new product offers, appointment reminders, and wellness information. Marketers can create patient education materials and health resource libraries, where they manage online review platforms and patient feedback systems to maintain strong relationships. Patient relationship management includes tracking satisfaction scores and addressing service concerns promptly. Marketing campaigns can encourage patient loyalty through quality care experiences and relevant, responsive communication.

Measuring Healthcare Marketing Performance

Healthcare organizations typically track different metrics for B2B and B2C marketing success. B2B measurements include conversions, contract values, partnership agreements, and referral volumes. B2C metrics focus on patient acquisition costs, service utilization, and satisfaction ratings. Data is analyzed from all channels to optimize their strategies and resource allocation. Team should compare campaign performance across different audience segments and marketing approaches. Regular performance reviews help organizations adjust their marketing mix to achieve better results. Teams will then use analytics tools to track marketing return on investment and guide future campaign planning.

What Are the Objectives of Healthcare Marketing?

January 6, 2025
Erik Kangas

Successful healthcare marketing campaigns set measurable targets to engage patients and customers, build brand recognition, strengthen market position, and generate business growth, while meeting healthcare regulations and compliance requirements. Marketing teams develop strategies to meet these targets through patient outreach and service promotion, including email marketing and outreach campaigns. These strategies balance business development with patient engagement and compliance requirements, focusing on both short-term acquisition goals and long-term relationship building.

Healthcare Marketing Strategy Development

Marketing in healthcare requires detailed approaches that respect patient privacy and medical ethics. Marketing teams create plans that address both revenue targets and patient and customers needs, while navigating regulations that govern healthcare communications, privacy and data security. Their work includes market research, campaign development and messaging, and results tracking across multiple channels. These plans typically incorporate email, digital, and community outreach methods to connect with patients and healthcare partners. Teams analyze current patient segments, demographic data, local healthcare needs, and market opportunities to develop targeted campaigns that resonate with specific patient populations and groups. Marketing departments also work closely with medical and business line staff to ensure all messaging and content accurately represent healthcare services and products, while maintaining professional standards and brand consistency.

Audience Segmentation Techniques

Marketing teams can improve conversion rates by targeting their audiences by numerous subgroups. The teams divide potential patients and customers into multiple subgroups based on specific healthcare needs and conditions, service utilization patterns, demographics, and behavioral characteristics. These segments include patients with chronic condition management needs, those seeking preventive care, and individuals requiring specialized treatments. With the right campaign management tools, teams can create custom messaging for each segment addressing their concerns and interests. For example. departments conducting email healthcare marketing campaigns can use patient data to identify recurring treatment needs and develop targeted follow-up programs. They track response rates across different segments to refine their targeting approaches and message development. This segmentation allows for more efficient resource allocation and higher conversion rates across marketing channels.

Patient Outreach and Relationship Building

Marketing teams develop methods, such as email outreach campaigns, to reach new patients and maintain connections with current ones. The teams analyze patient data to understand healthcare usage patterns and create targeted outreach programs that address community needs. These programs include detailed health education materials, preventive care information, new products, and service updates delivered through carefully selected communication channels, typically over secure email and via patient portals. Marketing departments track patient engagement through these touchpoints, from initial contact, to product and service delivery, to ongoing relationships and active engagement. They measure program effectiveness through patient response rates, conversions, such as appointment scheduling patterns or new plan enrollments, and satisfaction surveys. This data helps teams refine their communication approaches and develop more effective patient engagement strategies. Healthcare marketing initiatives also focus on building trust through transparent communication about treatment options, costs, and expected outcomes, all of which needs to be transmitted securely win a way that meets HIPAA compliance requirements.

Building Healthcare Product and Service Awareness

Healthcare organizations should develop marketing campaigns to promote their range of medical services, products and/or specialties. Marketing teams typically research regional healthcare needs and service gaps to identify growth opportunities within specific medical areas. They create targeted promotion strategies for each service or product line, considering factors like local competition, patient demographics, and insurance coverage. These campaigns often include physician referral programs, community health education events, and specialized outreach to patient groups who might benefit from specific services. Again, it’s critical to secure these communications, especially when PHI is being used, to protect patient privacy and meet HIPAA compliance requirements. Teams should continuosly monitor performance through patient volume metrics, engagement rates and conversions, revenue tracking, and market penetration rates. This information guides decisions about resource allocation and helps identify which services need additional marketing support.

Market Position and Competitive Analysis

Healthcare providers should also conduct regular market analyses to understand their competitive position and identify opportunities for growth. Marketing teams study regional healthcare trends, track competitor offerings, and assess patient satisfaction with current services. They use this information to develop campaign strategies that highlight their unique capabilities and treatment options. Market research includes patient preference surveys, analysis of healthcare utilization patterns, and assessment of emerging medical technologies. Teams use these insights to adjust their healthcare marketing messages and service offerings to meet changing patient needs. They should also monitor their market share across different service lines and geographic areas to ensure marketing efforts maintain or improve their competitive position.

Performance Measurement and Optimization

Finally, marketing departments must establish detailed metrics to evaluate their programs and demonstrate return on investment to internal teams and management. This includes tracking patient acquisition costs, engagement, satisfaction scores, and revenue generation across all marketing initiatives. Teams should use analytics tools to measure campaign performance across different channels and adjust strategies based on results. Regular reporting helps organizations understand which marketing efforts deliver the best outcomes and where to focus future investments. This data-driven approach ensures healthcare marketing resources target the most effective channels and messages. Teams should also monitor long-term trends in patient and customer retention, and referral patterns to assess the lasting impact of their healthcare marketing efforts.

How to Avoid AI-Based Email Security Threats

May 20, 2025
Pete Wermter

Artificial intelligence (AI) has been the hottest topic in technology for the past few years now, with a focus on how it’s transforming business and the way we work. While we’d seen glimpses of AI’s capabilities before, the release of ChatGPT (containing OpenAI’s groundbreaking GPT-3.5 AI model) put the technology’s limitless potential on full display. Soon, stakeholders in every industry looked to find ways to integrate AI into their organizations, so they could harness its huge productivity and efficiency benefits.

The problem? Hackers and bad actors are using AI too, and it’s only strengthening their ability to carry out data breaches, including AI-based email security threats.

While AI brings considerable advantages to all types of businesses, unfortunately, its vast capabilities can be used for malicious purposes too. With their unparalleled ability to process data and generate content, cybercriminals can use a variety of AI tools to make their attacks more potent, increasing their potential to get past even the most secure safeguards.

With all this in mind, this post discusses how AI is helping cyber criminals massively scale their efforts and carry out more sophisticated, widespread attacks. We’ll explore how malicious actors are harnessing AI tools to make AI-based email cyber attacks more personalized, potent, and harmful, and cover three of the most common threats to email security that are being made significantly more dangerous with AI. This includes phishing, business email compromise (BEC) attacks, and malware. We’ll also offer strategic insights on how healthcare organizations can best mitigate AI-enhanced email threats and continue to safeguard the electronic protected health information (ePHI) under their care.

How Does AI Increase Threats To Email Security?

AI’s effect on email security threats warrants particular concern because it enhances them in three ways: by making email-focused attacks more scalable, sophisticated, and difficult to detect.

Scalability

First and foremost, AI tools allow cybercriminals to scale effortlessly, enabling them to achieve exponentially more in less time, with few additional resources, if any at all.

The most obvious example of the scalable capabilities of generative AI involves systems that can create new content from simple instructions, or prompts. In particular, large language models (LLMs), such as those found in widely used AI applications like ChatGPT, allow malicious actors to rapidly generate phishing email templates and similar content that can be used in social engineering attacks, with a level of accuracy in writing and grammar not seen before. Now, work that previously would take email cybercriminals hours can be achieved in mere seconds, with the ability to make near-instant improvements and produce countless variations.

Similarly, should a social engineering campaign yield results, i.e., getting a potential victim to engage, malicious actors can automate the interaction through AI-powered chatbots, which are capable of extended conversations via email. This increases the risk of a cybercriminal successfully fooling an employee at a healthcare organization to grant access to sensitive patient data or reveal their login credentials so they can breach their company’s email system.

Additionally, AI allows cybercriminals to scale their efforts by automating aspects of their actions, and gathering information about a victim, i.e., a healthcare organization before launching an attack. AI tools also can scan email systems, metadata, and publicly available information on the internet to identify vulnerable targets, and their respective security flaws. They can then use this information to pinpoint and prioritize high-value victims for future cyber attacks.

Sophistication

In addition to facilitating larger and more frequent cyber attacks, AI systems allow malicious actors to make them more convincing. As mentioned above, generative AI allows cybercriminals to create content quickly, and craft higher-quality content than they’d be capable of through their own manual efforts.

Again, using phishing as an example, AI can refine phishing emails by eliminating grammatical errors and successfully mimicking distinct communication styles to make them increasingly indistinguishable from legitimate emails. Cybercriminals are also using AI to make their fraudulent communications more context-aware, referencing recent conversations or company events and incorporating data from a variety of sources, such as social media, to increase their perceived legitimacy.

In the case of another common email attack vector, malware, AI can be used to create constantly evolving malware that can be attached to emails. This creates distinct versions of malware that are more difficult for anti-malware tools to stop.

More Difficult to Detect

This brings us to the third way in which AI tools enhance email threats: by making them harder to detect and helping them evade traditional security measures.

AI-powered email threats can adapt to a healthcare organization’s cybersecurity measures, observing how its defenses, such as spam filters, flag and block malicious activity before automatically adjusting its behavior until it successfully bypasses them.

After breaching a healthcare organization’s network, AI offers cybercriminals several new and enhanced capabilities that help them expedite the achievement of their malicious objectives, while making detection more difficult.

These include:

Content Scanning: AI tools can scan emails, both incoming and outgoing, in real-time to identify patterns pertaining to sensitive data. This allows malicious actors to identify target data in less time, making them more efficient and capable of extracting greater amounts of PHI.
Context-Aware Data Extraction: similarly, AI can differentiate between regular text and sensitive data by recognizing specific formats (e.g., medical record numbers, insurance details, social security numbers, etc.)
Stealthy Data Exfiltration: analyzing and extracting PHI, login credentials, and other sensitive data from emails, while blending into normal network traffic.
Distributed Exfiltration: instead of transferring large amounts of data at once, which is likely to trigger cyber defenses, hackers can use AI systems that slowly exfiltrate PHI in smaller payloads over time, better blending into regular network activity.

AI and Phishing

Phishing attacks involve malicious actors impersonating legitimate companies, or employees of a company, to trick victims into revealing sensitive patient data. Typical phishing attack campaigns rely on volume and trial and error. The more messages sent out by cybercriminals, the greater the chance of snaring a victim. Unfortunately, AI applications allow malicious actors to raise the efficacy of their phishing attacks in several ways.

First, AI allows scammers to craft higher-quality messaging. One of the limitations of phishing emails for healthcare companies is that they’re often easy to identify, since they are replete with mis-spelled words, poor grammar, and bad formatting. AI allows malicious actors to overcome these inadequacies and create more convincing messages that are more likely to fool healthcare employees.

On a similar note, because healthcare is a critical industry, it’s consistently under threat from cybercriminals, which are also known as advanced persistent threats (APTs) or even cyber terrorists. By definition, such malicious actors often reside outside the US and English isn’t their first language.

While, in the past, this may have been obvious, AI now provides machine translation capabilities, allowing cybercriminals to write messages in their native language, translating them to English, and refining them accordingly. Consequently, scammers can craft emails with fewer tell-tale signs that healthcare organizations can train their employees to recognize.

Additionally, as alluded to earlier, AI models can produce countless variations of phishing messages, significantly streamlining the trial-and-error aspect of phishing campaigns and allowing scammers to discover which messaging works best in far less time.

Lastly, as well as enhancing the efficacy of conventional phishing attacks, AI helps improve spear phishing campaigns, a type of fraudulent email that targets a particular organization or employee who works there, as opposed to the indiscriminate, “scatter” approach of regular phishing.

While, traditionally, spear phishing requires a lot of research, AI can scrape data from a variety of sources, such as social media, forums, and other web pages, to automate a lot of this manual effort. This then allows cybercriminals to carry out the reconnaissance required for successful attacks faster and more effectively, increasing their frequency and, subsequently, their rate of success.

AI and Business Email Compromise (BEC) Attacks

A business email compromise (BEC) is a type of targeted email attack that involves cybercriminals gaining access to or spoofing (i.e., copying) a legitimate email account to manipulate those who trust its owner into sharing sensitive data or executing fraudulent transactions. BEC attacks can be highly effective and, therefore, damaging to healthcare companies, but they typically require extensive research on the target organization to be carried out successfully. However, as with spear phishing, AI tools can drastically reduce the time it takes to identify potential targets and pinpoint possible attack vectors.

For a start, cybercriminals can use AI to undertake reconnaissance tasks in a fraction of the time required previously. This includes identifying target companies and employees whose email addresses they’d like to compromise, generating lists of vendors that do business with said organization, and even researching specific individuals who are likely to interact with the target.

Once a target is acquired, malicious actors can use AI tools in a number of terrifying ways to create more convincing messaging. By analyzing existing emails, AI solutions can quickly mimic the writing style of the owner of the compromised account, giving them a better chance of fooling the people they interact with.

By the same token, they can use information gleaned from past emails to better contextualize fraudulent messages, i.e., adding particular information to make subsequent requests more plausible. For example, requesting data or login credentials in relation to a new project or recently launched initiative.

Taking this a step further, cybercriminals could supplement a BEC attack with audio or video deepfakes created by AI to further convince victims of their legitimacy. Scammers can use audio deepfakes to leave voicemails or, if being especially brazen, conduct entire phone conversations to make their identity theft especially compelling.

Meanwhile, scammers can create video deepfakes that relay special instructions, such as transferring money, and attach them to emails. Believing the request came from a legitimate source, there’s a chance employees will comply with the request, boosting the efficacy of the BEC attack in the process. Furthermore, the less familiar an employee is with attacks of this kind, the more likely they are to fall victim to them.

In short, AI models make it easier to carry out BEC attacks, which makes it all the more likely for cybercriminals to attempt them.

AI and Malware

Malware refers to any kind of malicious software (hence, “mal(icous) (soft)ware”), such as viruses, Trojan horses, spyware, and ransomware, all of which can be enhanced by AI in several ways.

Most notable is AI’s effect on polymorphic malware, which has the ability to constantly evolve to bypass email security measures, making malicious attachments harder to detect. Malware, as with any piece of software, carries a unique digital signature that can be used to identify it and confirm its legitimacy. Anti-malware solutions traditionally use these digital signatures to flag instances of malware, but the signature of polymorphic malware changes as it evolves, allowing it to slip past email security measures.

While polymorphic malware isn’t new, and previously relied on pre-programmed techniques such as encryption and code obfuscation, AI technology has made it far more sophisticated and difficult to detect. Now, AI-powered polymorphic malware can evolve in real-time, adapting in response to the defense measures it encounters.

AI can also be used to discover Zero Day exploits, i.e., previously unknown security flaws, within email and network systems in less time. Malicious actors can employ AI-driven scanning tools to uncover vulnerabilities unknown to the software vendor at the time of its release and exploit them before they have the opportunity to release a patch.

How To Mitigate AI-Based Email Security Threats

While AI can be used to increase the effectiveness of email attacks, fortunately, the fundamentals of mitigating email threats remains the same; organizations must be more vigilant and diligent in following email security best practices and staying on top of the latest threats and tools used by cybercriminals.

Let’s explore some of the key strategies for best mitigating AI-based email threats and better safeguarding the ePHI within your organization.

Educate Your Employees: ensure your employees are aware of how AI can enhance existing email threats. More importantly, demonstrate what this looks like in a real-world setting, showing examples of AI-generated phishing and BEC emails compared to traditional messages, what a convincing deepfake looks and sounds like, instances of polymorphic malware, and so on.

Additionally, conduct regular simulations, involving AI-enhanced phishing, BEC attacks, etc., as part of your employees’ cyber threat awareness training. This gives them first-hand experience in identifying AI-driven email threats, so they’re not caught off-guard when they encounter them in real life. You can schedule these simulations to occur every few months, so your organization remains up-to-date on the latest email threat intelligence.
Enforce Strong Email Authentication Protocols: ensure that all incoming emails are authenticated using the following:
- Sender Policy Framework (SPF): verifies that emails are sent from a domain’s authorized servers, helping to prevent email spoofing.
- DomainKeys Identified Mail (DKIM): preserves the integrity of the message’s contents by adding a cryptographic signature, mitigating compromise during transit, e.g., stealthy or distributed data exfiltration.
- Domain-based Message Authentication, Reporting & Conformance (DMARC): enforces email authentication policies, helping organizations detect and block unauthorized emails that fail SPF or DKIM checks.

By verifying sender legitimacy, preventing email spoofing, and blocking fraudulent messages, these authentication protocols are key defenses against AI-enhanced phishing and business email compromise (BEC) attacks.

Access Control: while AI increases the risk of PHI exposure and login credential compromise, the level of access that a compromised or negligent employee has to patient data is another problem entirely. Subsequently, data breaches can be mitigated by ensuring that employees only have access to the minimum amount of data required for their job roles, i.e. role-based access control (RBAC). This reduces the potential impact of a given data breach, as it lowers the chances that a malicious actor can extract large amounts of data from a sole employee.
Implement Multi-Factor Authentication (MFA): MFA provides an extra layer of protection by requiring users to verify their identity in multiple ways. So, even in the event that a cybercriminal gets ahold of an employee’s login credentials, they still won’t have sufficient means to prove they are who they claim to be.
Establish Incident Response and Recovery Plans: unfortunately, by making them more scalable, sophisticated, and harder to detect, AI increases the inevitability of security breaches. This makes it more crucial than ever to develop and maintain a comprehensive incident response plan that includes strategies for responding to AI-enhanced email security threats.

By establishing clear protocols regarding detection, reporting, containment, and recovery, your organization can effectively mitigate, or at least minimize, the impact of email-based cyber attacks enhanced by AI. Your incident response plan should be a key aspect of your employee cyber awareness training, so your workforce knows what to do in the event of a security incident.

Get Your Copy of LuxSci’s 2025 Email Cyber Threat Readiness Report

To learn more about healthcare’s ever-evolving email threat landscape and how to best ensure the security and privacy of your sensitive data, download your copy of LuxSci’s 2025 Email Cyber Threat Readiness Report.

You’ll discover:

The latest threats to email security in 2025, including AI-based attacks
The most effective strategies for strengthening your email security posture
The upcoming changes to the HIPAA Security Rule and how it will impact healthcare organizations.

Grab your copy of the report here and start increasing your company’s email cyber threat readiness today.