Page Comparison

...

Companies choose to use Cloud Maven’s “Secure Email” powered by Paubox's Email Encryption solution for two main reasons -

1. They want to reduce their risk of bad actors intercepting their data in transit (e.g, man in the middle attacks) and eliminate the possibility of sensitive data to be transmitted in plain text. Paubox ensures this by encrypting everything by default with blanket encryption. 

2. They use email as a main form of communication and need to ensure that the intended recipients can easily read their encrypted emails.

...

1. Email encryption solutions require

...

1. you to trade your communication for a false sense of added security. Paubox, on the other hand, delivers a HITRUST CSF Certified level of protection (Paubox is one of the only solutions on the market that has this) without the hassle of dealing with cumbersome additional steps (e.g., portals, plugins, usernames, etc.)

Paubox Encrypted Email is designed for ease of use for both senders and their recipients. Eliminating extra steps, like plugins, keyphrases, and portals. Paubox is also the only email encryption solution to meet HITRUST CSF certification, which means it meets essential regulatory and industry-defined requirements.

...

• Automation using process builders, flows, and apex triggers.

• Support any standard or custom object.

• Inbound and Outbound (2-way communication and automatic linking)

• Automatic Linking with the follow-up email.

• License-based permissions are available.

Paubox offers 4 secure message authentication options:

...

1. Seamless: When sending to recipients who support TLS 1.2+, emails are delivered as seamlessly as regular emails. Requiring zero steps to read the encrypted email. This will reflect 97% - 99% of your email volume, depending on.

2. Secure Link: When sending to recipients who DO NOT support TLS 1.2+ emails will require just 1 click to read. Redirecting to the Secure Message Center.

3. Secure Login: When sending to recipients who DO NOT support TLS 1.2+ emails will require 1 click to read. Redirecting to the Secure Message Center. This "View Message" link is only suitable for one-time use. After it is clicked on a second time, another email with a new "View Message" link is sent to the ordinal recipient. 

4. MFA: When sending to recipients who DO NOT support TLS 1.2+ a phone number must be entered the first time they receive a message from this sender. They will then be sent a 6-digit code via SMS to access the message within the Secure Message Center. 

*The authentication options #2 , #3 and  #4 can all be forced for any email of your choice using the Email API. Regardless if the recipient supports a high enough level of encryption or not. 

Data Sheet

...