Do attorneys need to encrypt email? Not every message. Under ABA Formal Opinion 477R, routine unencrypted email is generally still acceptable for talking to clients. When the information is sensitive, the opinion says to encrypt it. This page covers encrypted email for attorneys from that point on: how each kind works, what each one actually protects, and how to choose.
- When it’s required. Sensitive information, a client who asks for it, or a law that demands it.
- The four kinds. TLS, S/MIME, PGP and portal-based encryption. They protect different stretches of a message’s trip.
- What none of them do. Encryption guards the path to a mailbox. It can’t help once the wrong person is reading that mailbox.
- How to pick. Start from what your client has to do to open the message. Most firms already own a workable option.
When attorneys need encrypted email
The duty comes from ABA Model Rule 1.6(c) (checked October 4, 2026):
A lawyer shall make reasonable efforts to prevent the inadvertent or unauthorized disclosure of, or unauthorized access to, information relating to the representation of a client.
It asks for reasonable efforts and names no technology.
ABA Formal Opinion 477R (May 11, 2017, revised May 22, 2017) applies that to email:
Thus, the use of unencrypted routine email generally remains an acceptable method of lawyer-client communication. However, cyber-threats and the proliferation of electronic communications devices have changed the landscape and it is not always reasonable to rely on the use of unencrypted email.
The same opinion names three triggers for special precautions. A client agreement can require them. A law can require them. Or “the nature of the information requires a higher degree of security.” For that last case it’s direct: “if client information is of sufficient sensitivity, a lawyer should encrypt the transmission and determine how to do so to sufficiently protect it.”
These are the ABA’s Model Rules and opinions. Your state’s version of Rule 1.6 is what binds you, so check your own bar’s page. The full walk through the comments, the factors and the cases where encryption is called for is in what the ethics rules ask of a firm’s email.
How each kind of encryption works
Four arrangements get called encrypted email. They differ in two ways: which part of the trip they protect, and who can open the message at the end.
TLS: the connection between servers
TLS encrypts the link between two mail servers while a message crosses it. You already have it. Google’s help page says it in one line: “All Gmail messages use TLS automatically.” (Google, checked October 4, 2026.)
The catch is the other end. Google’s admin documentation says what happens when the receiving server doesn’t support TLS: “Gmail still sends messages but the connection isn’t secure.” (Google Workspace, checked October 4, 2026.) An admin can require TLS for named domains instead. Then a message that can’t go securely bounces, and you get a non-delivery report.
Once the message lands, TLS is done. It sits readable in your sent folder, on the client’s provider and on the client’s phone.
S/MIME: certificates on both ends
S/MIME encrypts the message itself, so it stays sealed in transit and in storage. Microsoft’s Exchange Online documentation (checked October 4, 2026) lists two services:
- Encryption, which “Protects the content of email messages.”
- Digital signatures, which “Verifies the identity of the sender of an email message.”
Both matter to a law firm. The signature proves the message came from you and wasn’t altered. Microsoft is clear that encryption alone doesn’t do that: “An unsigned, encrypted message is as susceptible to sender impersonation as a message that isn’t encrypted.”
The cost is setup. Each person needs a certificate, and you need the recipient’s public certificate before you can encrypt to them. That suits a regular counterpart with an IT department, such as a corporate client’s legal team. It rarely suits an individual client.
PGP: keys you manage yourselves
PGP works on the same idea as S/MIME: each person has a public key to share and a private key to keep. The current standard is OpenPGP, RFC 9580, published July 2024. It “provides encryption with public key or symmetric cryptographic algorithms, digital signatures, compression, and key management.”
The difference is who vouches for the keys. S/MIME leans on certificate authorities. PGP leaves it to the people exchanging keys. That gives you full control, and it asks the same of your client. Some encrypted mail providers use OpenPGP underneath and handle the keys for you.
Portal-based: the message waits somewhere else
This is what most firms mean by encrypted email. Microsoft Purview Message Encryption, Gmail’s options and most add-ons work this way for outside recipients. The message is held by a service, and the client gets a notice that it’s waiting.
Microsoft describes the client’s side of it (Microsoft Learn, checked October 4, 2026):
Recipients of encrypted messages who receive encrypted or rights-protected mail sent to their Gmail and Yahoo accounts receive a wrapper mail that directs them to the encrypted message portal where they can easily authenticate using a Microsoft account, Gmail, or Yahoo credentials.
Clients without those accounts can usually use a one-time passcode instead. Nobody installs anything or swaps certificates. The service holds the means to open the message, so this protects against interception and casual forwarding more than against the provider itself. An admin can set rules that encrypt automatically, for example every message to a named client.
A fifth option is plain and common: a password-protected PDF attached to an ordinary email, with the password given by phone. It needs no subscription at all.
What encryption covers, and what it leaves open
Encryption protects a message on its way to a mailbox. It does nothing about who’s sitting at that mailbox. That’s the one misreading on this page that costs firms something, because several of the risks that matter most in practice live at the client’s end.
Here’s how each kind holds up against the things that actually go wrong.
| Risk | TLS | S/MIME or PGP | Portal-based |
|---|---|---|---|
| Someone reading traffic between mail servers | Covered when both servers use it | Covered | Covered |
| A breach at the client’s email provider | Not covered | Covered | Covered while the content stays in the portal |
| A breach at the service holding the message | Not covered | Covered | Not covered |
| A typo or autocomplete sending it to the wrong person | Not covered | Usually blocked, since you need that person’s key | Not covered; the portal opens for whoever holds that address |
| A spouse or employer who can open the client’s mailbox | Not covered | Not covered if they also use the client’s device | Not covered |
| The client forwarding your advice | Not covered | Not covered once decrypted | Partly; “do not forward” can restrict it |
| Proof the message came from your firm | No | Yes, when signed | No |
| Subject line, sender, recipients and timestamps | Visible at both ends | Visible | Usually visible |
Three rows deserve a sentence each.
The wrong recipient. Portal encryption sends the passcode to whatever address you typed. So a misdirected message is still a misdirected message. A short pause before sending to anyone outside the firm does more here than any setting.
The client’s own mailbox. Encryption can’t tell the client from someone using the client’s laptop. A divorce client on a shared family computer, or an employee writing from a work account, is a privilege question as much as a security one. The client-side habits are in is emailing a lawyer confidential?
The subject line. Even the stronger options leave the envelope readable. Google says so for its own client-side encryption: “The header of the email, including subject, timestamps, and recipients, will not have additional encryption.” (Google, checked October 4, 2026.) “Documents for your review” tells the client everything they need and tells nobody else anything.
Choosing an option for your firm
Most small firms don’t need a new system. They need to decide which matters get which treatment. Work through it in this order.
- Look at what you already pay for. On Microsoft 365, check whether your plan includes Purview Message Encryption. On Google Workspace, check which edition you’re on. The product-by-product comparison, with plans and BAAs, is in choosing a secure email client for a law firm.
- Sort your matters into two tiers. Routine correspondence goes by ordinary email. Anything sensitive goes encrypted or through a portal. Medical records, financial account numbers, settlement terms and trade secrets are the usual second tier.
- Match the method to the client. An individual client gets portal-based encryption or a locked PDF. A corporate legal department that runs S/MIME gets S/MIME, signed. A technical client who asks for PGP gets PGP.
- Ask each client at intake. Opinion 477R expects that conversation early. Ask how they read email, on what device, and who else can reach it.
- Put documents somewhere better than an attachment. Large or sensitive files usually belong in a client portal or secure file share, with an ordinary email saying they’re there.
- Write the rule down. One paragraph that staff can follow without asking you.
What is the most secure encrypted email?
On paper, the strongest arrangement is end-to-end encryption where only you and the client hold the keys: S/MIME, PGP, or a provider built on them. Nobody in between, including the provider, can read the content.
In practice, the most secure option is the one your client will actually use. A method that makes a client give up and reply in plain text from a work account protects nothing. For most individual clients that points to portal-based encryption with a one-time passcode.
If you have clients in the EU
This section only applies if your firm handles personal data of people in the European Union. US rules don’t import any of it.
The EU’s General Data Protection Regulation can reach a US firm directly. Article 3(2) applies it to a controller “not established in the Union” where the processing relates to “the offering of goods or services” to people in the Union. Representing a client who lives in Germany can put you there.
Article 32(1) sets the security duty. It asks for security “appropriate to the risk,” and its first example is:
the pseudonymisation and encryption of personal data;
Like Rule 1.6, that’s a risk-based test rather than a mandate to encrypt every message.
Encryption also pays off after a breach. Article 34 normally requires telling affected people about a high-risk breach. Article 34(3)(a) lifts that duty where the data was protected by measures “that render the personal data unintelligible to any person who is not authorised to access it, such as encryption.” For EU client files, that’s a strong reason to send them encrypted by default.
What an assistant sees when mail is encrypted
Point is an AI email client that sits on your existing Microsoft 365 or Gmail account. Your encryption settings stay where they are. What Point reads depends on what each message’s encryption leaves in your mailbox.
- TLS mail arrives readable, so Point reads, sorts and summarizes it like any other message.
- A portal message arrives as a notice with a link. Point sees the notice and can remind you it’s waiting. The content stays in the portal.
- A message you lock end to end in Point is sealed on your device before it leaves. Point’s servers carry it without being able to open it. Point doesn’t summarize it, take a task from it or draft a reply to it.
How far Point acts on the mail it can read is set per kind of action. Review is the default, so drafts wait for you. At the top of the dial Point acts without asking, and a sent email can’t be pulled back off someone else’s server. For client mail, review is the setting to keep. The rest of what Point does is on the benefits page. The longer account of which encryption an assistant can and can’t read is in encrypted email, and what an AI assistant cannot read.
Common questions
Do attorneys need to encrypt email?
Not for every message. ABA Formal Opinion 477R says unencrypted routine email “generally remains an acceptable method of lawyer-client communication.” It also says a lawyer should encrypt when client information is sensitive enough, when a client agreement requires it, or when a law does. Your state’s version of Rule 1.6 is what governs you.
What is the most secure encrypted email?
End-to-end encryption, where only the sender and recipient hold the keys, is the strongest. S/MIME and PGP both work that way. For most individual clients, though, portal-based encryption with a one-time passcode is the secure option they’ll actually use. Pick the strongest method your client can open without falling back to plain email.
Are encrypted emails HIPAA compliant?
Not by themselves. Encryption is one safeguard, and HIPAA asks for more. A firm doing legal work for a hospital, practice or health plan that touches patient records can count as a business associate. That brings a written agreement with your email provider and a recorded choice about encryption. The details are in are encrypted emails HIPAA compliant?
Is emailing a lawyer confidential?
Yes, on the lawyer’s side: the duty of confidentiality covers what you send. Privilege is a separate protection, and a client can lose it. Writing from a work account, sharing an account with someone else, or forwarding your lawyer’s advice to a third party can all put it at risk. Encryption doesn’t fix any of those, because each one happens at the client’s end.
What email do most law firms use?
Microsoft 365 with Outlook leads by a wide margin. Google Workspace with Gmail is the other platform you’ll meet. Both have built-in encryption. Microsoft offers Purview Message Encryption, and Google offers confidential mode and, on its top editions, client-side encryption.
Is TLS enough for attorney email?
For routine correspondence it generally is, under Opinion 477R. TLS protects the message only between servers, and only when both servers support it. For sensitive matters, use a method that keeps the message sealed after it arrives.