Blog
   |   
All Industries

Is S/MIME Enough for HIPAA, CMMC, and CUI Email?

By
Qanapi
November 18, 2026
•
5 min read
Share this post
Is S/MIME Enough for HIPAA, CMMC, and CUI Email?

S/MIME is enough to meet the email encryption requirement in HIPAA and the CUI transmission requirement in CMMC Level 2, but only when three conditions hold: the cryptographic module is FIPS-validated, the private keys sit where your obligations say they should, and your recipients can actually use it. S/MIME protects the message itself. It does not protect the subject line, it does not decide who holds a copy of the key, and it does not reach a recipient without a certificate. Those three gaps, not the protocol, are where audits stall.

What does S/MIME actually protect?

S/MIME is the IETF standard for signing and encrypting email with X.509 certificates (RFC 8551). The sender encrypts the message body and attachments with the recipient's public key. The content stays encrypted on every server it crosses and in the recipient's mailbox, and only the matching private key opens it. The signature proves who sent the message and that nothing changed on the way.

That is a different control from TLS, which Gmail shows as a gray lock. TLS encrypts the connection between mail servers, and Google manages those keys, so it protects mail from outsiders on the network, not from the providers that handle it (Google). A server-side encryption gateway applies protection at the gateway, which means the gateway operator handles the plaintext before it is encrypted. Both protect the pipe. S/MIME protects the message.

S/MIME leaves four things open:

  • The subject line and headers. S/MIME encrypts the MIME body. Subject, sender, recipients, and timestamps travel in the clear unless header protection is used, which RFC 8551 treats as optional. Google's client-side encryption also leaves the subject unencrypted (Gmail Help). A subject that names a patient or a controlled part number is exposed.
  • The key copy. With Google's hosted S/MIME, Google manages a copy of each user's private key (Google). That is a decision about who you trust, not a defect in S/MIME.
  • Recipients without certificates. Both parties need certificates, and they must exchange signed mail once before encrypted mail can flow (Qanapi).
  • The module. S/MIME names algorithms. It does not certify the software that runs them. For CUI, that difference decides the assessment.

Is S/MIME enough for HIPAA?

For the message body, yes. The HIPAA Security Rule requires protection of ePHI in transmission and lists encryption as an addressable implementation specification (45 CFR 164.312(e)). Addressable means you implement it or document an equivalent alternative; it does not mean optional. HHS proposed in January 2025 to make encryption required (Federal Register), and as of November 2026 that rule is not final. The rule names no protocol, so S/MIME with current algorithms satisfies the encryption specification.

The gaps in healthcare are practical, not legal:

  • Patients rarely hold certificates. S/MIME fits practice to lab, practice to payer, and practice to referring clinician, because those are organizations that can hold certificates. For patients, a portal or Gmail's end-to-end encryption guest account is the realistic route (Qanapi).
  • Subject lines carry PHI. Train staff to keep names, dates of birth, and conditions out of the subject, because S/MIME will not hide them.
  • Every vendor in the path is a business associate. A gateway, portal, or key service that handles PHI for you needs a business associate agreement.

Is S/MIME enough for CMMC Level 2 and CUI?

It can be, and the deciding factor is the module, not the protocol. CMMC Level 2 assesses the 110 requirements in NIST SP 800-171 Rev. 2 (NIST). Three apply directly to email:

Requirement 3.13.8
Cryptographic mechanisms that prevent unauthorized disclosure of CUI in transmission
Where S/MIME stands
Meets the intent
The message is encrypted end to end, not just the connection.
Requirement 3.13.11
FIPS-validated cryptography when cryptography protects CUI confidentiality
Where S/MIME stands
Passes or fails on the module
Ask your provider for the CMVP certificate number.
Requirement 3.13.10
Establish and manage cryptographic keys
Where S/MIME stands
Depends on who controls the keys
Document who issues, renews, revokes, and holds copies of each key.

On 3.13.11, an algorithm name such as AES-256 is not evidence. The module that runs it must be validated, and must appear on NIST's Cryptographic Module Validation Program list (DIB SCC CyberAssist). FIPS 140-2 certificates moved to the historical list on September 21, 2026, so new evidence should point to FIPS 140-3.

On 3.13.10, NIST SP 800-171 does not say the contractor must hold the only copy of a key. It does require you to document key management, and the key copy determines who can read CUI. Expect assessors to ask for it in the System Security Plan and the shared-responsibility matrix.

The timeline shifted, the obligation did not. The Department of War suspended CMMC Phase 2, the November 10, 2026 start of mandatory third-party certification, on July 13, 2026 and said it would keep enforcing the underlying requirements through self-assessments and selected government-led assessments (Inside Government Contracts). DFARS 252.204-7012 still requires NIST SP 800-171 for covered CUI.

Three questions that decide whether S/MIME is enough

  1. Who must never read this message? If the answer includes your email provider, hosted S/MIME is not enough. You need keys held outside the provider: client-side encryption or CSE-wrapped S/MIME.
  2. Can you produce the module's FIPS certificate? For CUI, no certificate means no credit on 3.13.11, whatever the protocol.
  3. Who are your recipients? Organizations that can hold certificates suit S/MIME. Individuals who cannot need a guest account or portal, with the trade-offs that come with it.

How the options compare

TLS only
Gray lock
Encrypts the connection between mail servers.
Who else reads it
Every mail provider in the path
Recipient needs
Nothing
Best fit
Baseline only; not a CUI control
Server-side gateway
Encrypts at the gateway
Applies encryption on a server after the message leaves the sender.
Who else reads it
The gateway operator
Recipient needs
Varies by product
Best fit
Transit protection for routine mail
Portal or secure reader
Read in a browser
Stores the message on the vendor's platform and sends the recipient a link.
Who else reads it
The portal vendor
Recipient needs
A browser login
Best fit
One-off recipients and patients
Hosted S/MIME
Green lock
Signs and encrypts the message itself, with a certificate for each user.
Who else reads it
Google, which manages a key copy
Recipient needs
An S/MIME client and one signed-mail exchange
Best fit
PHI between organizations; CUI when the module is FIPS-validated
CSE-wrapped S/MIME
Blue shield
Encrypts the message in the browser, with keys held by an external key service outside Google.
Who else reads it
Only holders of your externally managed keys
Recipient needs
An S/MIME client
Best fit
CUI and CMMC Level 2 work where the provider must not hold keys

Where Qanapi Flow fits

Qanapi Flow runs S/MIME inside native Gmail and takes the certificate work off the admin. The admin selects users or a Google Group and clicks Enable; Qanapi orders, verifies, uploads, and renews each certificate (Qanapi). Recipients use any S/MIME-capable mail client.

Flow Secure Email
$10per user per month
Green lock
Hosted S/MIME across the domain
Best for PHI and sensitive mail between organizations
Flow Zero Trust
$15per user per month
Blue shield
CSE-wrapped managed S/MIME, with Qanapi as the external key service, so keys stay outside Google's reach (Qanapi)
Best for CUI and CMMC Level 2 work in Google Workspace
Flow Federal
$25per user per month
Blue shield
CSE-wrapped managed S/MIME in a FedRAMP High authorized environment, stackArmor's Armory on Google Cloud
Best for federal deployments, scoped with the Qanapi team

Flow's FIPS 140-3 coverage comes from a validated third-party cryptographic module. Flow does not make an organization compliant. On Qanapi's CMMC mapping, hosted S/MIME bears on 2 of the 59 practices Flow touches (Qanapi); the rest of your program still has to stand on its own. Google requires a supported Workspace edition for S/MIME and client-side encryption, such as Enterprise Plus.

Request a quote for Flow Secure Email, then book a demo to see it in action. In the demo, we enable S/MIME for a Google Group from the admin console and show certificate ordering, verification, upload, and renewal running without manual steps, plus removal when a user is disabled, compared with what a self-managed certificate rollout requires for every user.

Frequently asked questions

Is S/MIME HIPAA compliant?

S/MIME satisfies HIPAA's encryption specification for the message body when it uses current algorithms. HIPAA compliance also depends on your risk analysis, business associate agreements, and keeping PHI out of subject lines, which S/MIME does not encrypt.

Does CMMC require S/MIME?

No. CMMC Level 2 requires cryptographic protection of CUI in transmission (NIST SP 800-171 requirement 3.13.8) using FIPS-validated cryptography (3.13.11). S/MIME is one way to meet both when its module is FIPS-validated.

Does S/MIME encrypt the subject line?

Not by default. S/MIME encrypts the body and attachments. The subject, sender, recipients, and timestamps stay readable unless header protection is used.

Is S/MIME FIPS-validated?

S/MIME is a protocol, so it cannot be validated. The cryptographic module that performs the encryption can be. Ask your provider for the CMVP certificate number and confirm it covers FIPS 140-3.

What is CSE-wrapped S/MIME?

CSE-wrapped S/MIME combines S/MIME with Google Workspace client-side encryption. Messages are encrypted in the browser with keys from an external key service, so Google never holds a usable copy of the private key.

Can I send S/MIME email to patients?

Only if the patient has an S/MIME certificate and mail client, which is rare. For patients, use a portal or Gmail's end-to-end encryption with a guest account, and keep S/MIME for organization-to-organization mail.