Most conversations about HIPAA compliant email eventually land on the same acronym: TLS. It’s the most common encryption method in use, and for good reason — it’s widely supported and relatively simple to enforce. But TLS isn’t the only encryption standard healthcare organizations should understand, and it isn’t always the right tool for securing your email address and message content.

S/MIME is the other name that comes up frequently, especially in healthcare, and usually in the same breath as PGP, along with some confusion about what it actually does differently. This guide breaks down what S/MIME is, how MIME works underneath it, how to configure it, and — just as importantly — when it’s genuinely worth the effort versus when it isn’t, based on both the technical standard and real feedback from the people who’ve actually had to manage it.

If you haven’t yet worked through the basics of what makes email HIPAA compliant in the first place, our HIPAA Compliant Email guide is a useful starting point before diving into a specific encryption standard like this one.

What Is S/MIME?

S/MIME stands for Secure Multipurpose Internet Mail Extensions (also written Secure/Multipurpose Internet Mail Extensions). It’s a security extension of MIME, the original standard introduced in 1992 that first allowed email to carry more than plain text — attachments, formatting, and different character sets. Understanding how MIME works helps explain what S/MIME adds on top: where MIME made richer content possible, S/MIME made that content secure by encrypting it and digitally signing it.

S/MIME’s roots as a security standard go back to the early 2000s, largely through work done by RSA Security, one of the earliest companies focused on computer and network security. Because it’s been around for so long, S/MIME is supported natively by most major email clients, including Outlook and Apple Mail, without requiring third-party software or plugins.

At its core, S/MIME provides three distinct protections for email security:

• Encryption — ensures that only the intended recipient, using their private key, can read the email messages sent to them
• Sender authentication — verifies the identity of the sender, so the recipient can trust the email actually came from who it claims to be from
• Digital signing — confirms the message wasn’t altered in transit, effectively letting you digitally sign each message you send

This combination is what distinguishes S/MIME from encryption methods that only protect the connection a message travels over. S/MIME protects the message itself — a meaningful distinction for any organization handling sensitive data security requirements.

How Does S/MIME Work?

S/MIME is built on Public Key Infrastructure (PKI) and asymmetric encryption — a system that uses two mathematically linked digital certificates instead of one shared password.

• Public key — shared openly, used by others to encrypt messages sent to you and to verify your digital signature
• Private key — kept secret and secure, used by you to decrypt received messages and sign outgoing ones

When someone sends you an S/MIME-encrypted email, they encrypt it using your public key. Only your corresponding private key can decrypt it, meaning that even if the message is intercepted somewhere along its path, it remains unreadable without that specific private key. This is what people mean when they describe S/MIME as end-to-end encryption: the protection travels with the message itself, not just the connection carrying it.

To configure S/MIME, both the sender and recipient need:

• A digital certificate, issued by a trusted certificate authority (CA), tied to their specific email address
• That certificate properly installed and configured in their email client
• Each other’s public key, exchanged in advance, so encryption and decryption can actually happen

If any one of these pieces is missing on either side, S/MIME simply doesn’t work for that exchange — a limitation that comes up constantly in practitioner discussions, and one worth understanding before you invest time configuring it.

What IT Practitioners Actually Say About This

One useful, if slightly humbling, reality check comes up repeatedly in IT forums when people ask whether they should bother configuring S/MIME: as one systems administrator put it plainly, most people you correspond with have no idea how to verify a digital signature and won’t even notice if one is missing. Emails from your bank or a government tax agency, they pointed out, typically aren’t S/MIME signed at all — a sign of just how limited real-world verification behavior actually is outside of specific technical or regulatory contexts.

Another common thread: several IT professionals candidly noted that email clients like Outlook can create friction by automatically trying to reply with an S/MIME signed message, which can be genuinely annoying for a recipient who has no certificate configured and no way to make sense of the added complexity. Their advice, consistently, boiled down to one clarifying question: it isn’t a question of whether you should configure S/MIME, but whether you actually need it — if none of the people you communicate with require signed email, the added configuration probably isn’t buying you anything meaningful.

That distinction — need versus want — is exactly the lens healthcare organizations should apply too, and it’s the framing this guide uses throughout.

S/MIME vs. TLS vs. PGP: How They’re Different

It’s easy to lump every encryption acronym together, but each one solves a slightly different problem.

TLS encryption – most people interact without realizing it — it’s what protects the connection when your email travels from your server to the recipient’s server. The tradeoff is that TLS only protects the message in transit; once it lands on a mail server, TLS’s job is done.

S/MIME and PGP both aim to close that gap by encrypting email messages themselves, so they remain protected even after delivery. The key difference, as one privacy-focused forum discussion put it well, comes down to how identity is managed: S/MIME farms identity verification out to a trusted certification authority, while PGP requires you to manage that trust relationship yourself. For most healthcare organizations, S/MIME’s centralized CA model is the more practical fit, since it aligns better with how enterprise IT departments already manage digital certificates and existing vendor relationships.

Key Benefits of S/MIME

• Genuine end-to-end protection. Because the message itself is encrypted, S/MIME protects data security even if it passes through servers that don’t support encryption.
• Built-in sender authentication and message integrity. Digital signatures verify both the identity of the sender and that the message hasn’t been tampered with — a layer TLS alone doesn’t provide.
• Broad native support across email clients. Most major email clients support S/MIME out of the box, without requiring a separate plugin.
• Flexibility to sign without encrypting. As one practitioner pointed out, you can digitally sign an outgoing message without encrypting it — useful for something like a mailing list, where you want recipients to trust the message came from you, but full encryption isn’t necessary or practical for a broad distribution list.

The Real Tradeoffs of S/MIME

Certificate management is ongoing, not one-time. Every sender and recipient needs a certificate tied to their email address, renewed and reissued as staff change roles or leave. Manageable for a small group; significant admin overhead for a whole organization.

Both parties must be configured correctly. If a recipient lacks a certificate or the sender’s public key, the message bounces or fails to send encrypted — some systems fall back to TLS, but only if configured to do so.

Most recipients can’t verify it anyway. IT practitioners consistently note that outside specific business or regulatory contexts, recipients have no practical way to check a digital signature — and default behaviors like auto-signed replies can just create friction.

It doesn’t scale to high-volume email. S/MIME suits direct correspondence between known parties, not appointment reminders, billing notices, or large mailing lists.

It can conflict with malware scanning. End-to-end encryption blocks gateway-level inspection, so scanning has to happen at the endpoint instead.

How to Configure S/MIME?

For Individuals

1. Obtain an S/MIME certificate from a trusted certificate authority. Certificates come in different validation levels — Basic (validates only the email address), Individual Validation (confirms personal identity), Organization Validation (confirms the business’s legitimacy), or Sponsor validation (combining both).
2. Install the certificate in your email client — most major email clients, including Outlook and Apple Mail, support this natively.
3. Configure the client to use the certificate for both encrypting outgoing messages and verifying signatures on incoming ones.
4. Exchange public keys with anyone you intend to correspond with securely — typically by sending them a signed (but not necessarily encrypted) email first, which shares your public key automatically.

For Organizations

1. Determine the validation level your organization actually needs. Higher validation levels provide stronger identity assurance but involve more verification steps and cost.
2. Use centralized tools to manage the certificate lifecycle. Protocols like LDAP or endpoint management platforms (such as Microsoft Intune) can significantly reduce the manual burden of distributing and renewing digital certificates at scale.
3. Distribute certificates and provide clear installation guidance to every employee who needs S/MIME — this is often where organizations underestimate the support burden, particularly for less technical staff.
4. Set clear policies on when S/MIME is required versus when other encryption methods, like enforced TLS, are sufficient. Treating S/MIME as a blanket requirement across an entire organization typically creates more friction than protection, echoing exactly what practitioners report when they configure it without a clear need.

When Does S/MIME Actually Make Sense?

Given its administrative overhead — and the recurring, practical feedback from people who’ve actually configured it — S/MIME is best reserved for specific, high-sensitivity use cases rather than applied indiscriminately:

• Clinician-to-clinician communication involving particularly sensitive diagnoses or treatment details, where both parties are known and willing to maintain certificates
• Cross-organization referrals where a small, defined group of specialists regularly exchanges detailed patient information and can reasonably manage the certificate relationship
• Legal, compliance, or executive correspondence where verifying the sender’s identity and confirming message integrity outweighs the setup cost

For everything else — appointment reminders, billing communications, marketing outreach, or high-volume patient correspondence — enforced TLS or a managed encryption platform that automatically selects the right method per recipient is almost always the more practical choice. This mirrors exactly what experienced IT practitioners consistently conclude on their own: it’s not about whether S/MIME can work, it’s about whether your specific communication actually needs it.

A Simpler Path: Automated, Per-Recipient Encryption

The tradeoff most organizations run into with S/MIME isn’t whether it works — it’s whether staff can reliably manage digital certificates for every relevant contact without errors slipping through, and without creating the kind of recipient friction practitioners describe so consistently.

Rather than requiring every sender and recipient to individually configure S/MIME, some HIPAA compliant email platforms automatically select the appropriate encryption method per recipient — TLS when it’s sufficient, a secure portal when the recipient’s system doesn’t support TLS, and PGP or S/MIME when the situation calls for genuine end-to-end protection and sender verification. This removes the burden of manually deciding — and manually maintaining certificates — from individual staff members, while still making S/MIME available for the specific cases where it’s the right tool.

What Should I Do Now? (revised with target-keyword anchor text)

S/MIME is a legitimate, well-established way to secure your email and verify the sender — but understanding when to use it, and when a simpler method is more appropriate, matters just as much as knowing how to configure it. Most healthcare organizations don’t need S/MIME everywhere; they need the right encryption method applied automatically, based on the situation.

Here’s where to go next:

1. Learn more about HIPAA compliant email encryption to see how encryption standards like S/MIME fit into a broader compliance strategy.
2. Explore Secure High Volume Email to see how automatic, per-recipient encryption — including S/MIME and PGP where appropriate — removes the manual certificate management burden from your staff.
3. Talk to a LuxSci expert if you’re evaluating which encryption approach fits your organization’s specific mix of high-sensitivity and high-volume email.

FAQs

1. Is S/MIME better than TLS for email security?

Neither is universally better — they solve different problems. TLS protects the connection a message travels over and suits high-volume, everyday email. S/MIME protects the message content itself, end-to-end, and suits specific, high-sensitivity communications between known parties who can manage digital certificates.

2. What happens if I send an S/MIME encrypted email to someone who doesn’t support it?

The message typically won’t deliver as encrypted, and depending on how the sending system is configured, it may bounce back to the sender or automatically fall back to TLS.

3. Do I need a separate digital certificate for every email address, or just one for my organization?

Each individual email address needs its own certificate issued by a certificate authority. A single organizational certificate doesn’t cover every employee — certificates are tied to specific addresses, not the organization as a whole.

4. Can I digitally sign an email without encrypting it?

Yes. Signing confirms the identity of the sender and that the message wasn’t altered, without requiring the recipient to have a certificate of their own. This is useful for situations like mailing lists, where full encryption isn’t practical but sender verification still adds value.

5. Is S/MIME a good fit for HIPAA compliant marketing emails?

Generally, no. S/MIME’s certificate and key exchange requirements don’t scale well to high-volume or one-to-many communication like marketing campaigns. Enforced TLS or a platform that manages encryption automatically per recipient is typically the better fit for that use case.

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

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.

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:

1. Explore LuxSci’s SecureLine encryption technology to see how automated encryption, enforced TLS, and a signed BAA work together — no complex configuration required.
2. Read our HIPAA Compliance Checklist to understand the full scope of what your organization needs to have in place beyond email.
3. 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.