ePrism Encrypted Email Service FAQ

Q. How is the Encrypted Email Service licensed?

A: Licensing for EdgeWave's Encrypted Email service is based on the number of users, not on the number of messages sent.


Q. Are there restrictions on message volumes?

A: There are no restrictions on the number of messages you can send through EdgeWave's Encryption Service.


Q. In order to buy this feature, do I also have to buy any of the other services offered in the
     ePrism Messaging Security Suite?

A: ePrism Encryption Service is part of the ePrism Email Security Suite. While you can evaluate the Encrypted Email Service without dislocating your existing email filtering solution, there are significant advantages to using ePrism Encryption over other encrypted email providers because it is integrated with the complete ePrism suite. All ePrism services are accessible via a single management console, making it easy to manage all your email security and encrypted email services from a single user interface. Also, our secure encrypted email is integrated with ePrism Data Loss Protection (DLP) Service, so that detection of a DLP violation can automatically trigger the encrypted email service - another added benefit.


Q. Do I have to license all SMTP users for this feature?

A: No. you need only license users that need the encrypted email services. If required, this can be a subset of your total users. User numbers and volumes will be audited and verified against customer licensed values.


Q. Is there a minimum number of licenses I have to buy?

A: Customers must buy at least 25 user licenses.


Q. How long are messages stored on the portal for secure message delivery?

A: Messages are stored on the encrypted email portal for 30 days


Q. How does Park and Pull encrypted email service differ from other encrypted email
     providers technologies?

A: The main advantages of deploying a park and pull encryption solution are
  1. The ability to send secure encrypted email to anyone regardless of their computer software
  2. There are no software clients or keys required at the endpoints in order to send or receive an encrypted message.
  3. Recipients of secure messages can access all of their secure messages from one mailbox on the portal. Recipients will be required to create a login once, after which they can use the portal as needed.


Q. Why do I need to encrypted email services?

A: Non encrypted email can be intercepted and read by unauthorized users relatively easily and it is dangerous to allow confidential or sensitive data to be exposed. Data is vulnerable to both intentional and inadvertent loss; for instance misdirecting an email to the wrong recipient. Other reasons for using encrypted email services include:
  • Data Security � Encrypted email services ensure that your sensitive data (credit card information, customer data, patient records, Social Security numbers of customers, etc) are received only by the intended recipient. Any loss of such sensitive data could be devastating to your company.
  • Data Compliance - Fines for non-compliance with government regulations such as HIPAA, SOX, or PCI can be huge. In addition, exposing private data can subject you to costly litigation.


Q. Is there a restriction on the size of message that can be sent via secure encrypted email?

A: Yes. In order to provide an acceptable level of performance for the recipient, the maximum encrypted email size is currently 100Mb.


Q. Where are EdgeWave's data centers located?

A: EdgeWave has two SAS70 certified datacenters in the US: East Coast and West Coast.


Q. What encryption methods are used to get messages to and from the pickup center?

A: The initial secure encrypted email is sent using transport layer security (TLS) encryption. Then a notification message containing a link to a secure HTTPS web site is generated and sent to the recipient, who simply clicks the link and is taken to the portal, where they can read and respond through their browser.


Q. Is the secure encrypted email portal fault-tolerant?

A: Yes, multiple servers are deployed for each configuration. If any one of those servers happens to fail, the other servers in the cluster will continue to handle the workload while the failed server is replaced.