Consequently, Microsoft Exchange® will only journal the message notifications that do not contain confidential data. When sending a secure (encrypted) message, the actual message content is sent encrypted through the Secure Messaging platform. Microsoft Exchange® Journaling intercepts outgoing or incoming notification messages, and journals them to a specific archiving address. Users using the Google Chrome® browser can install the extension and render secure messages directly in Outlook Web Access® (OWA), Gmail®, Yahoo Mail® or any other webmail service within the same familiar interface. For email programs that do not include a Secure Messaging platform plug-in, a convenient link is provided within the notification message in the recipient’s existing inbox to access the Secure Webmail that also supports mobile, tablet and visually impaired user access. This data is then instantly transferred along with the secure message, using the same encrypted HTTPS route, and the message is rendered inside the existing inbox. Recipients of the secure message benefit from the same great features: the Outlook plug-in recognizes the notification message and instantly sends a command to the Secure Messaging platform to authenticate the recipient and decrypts the message and file attachments. Recipients equipped with the same Outlook plug-in never see this notification instead, the secure message is automatically rendered in Outlook and stored in the mail server. If equipped with Outlook, the notification message is sent through the sender’s outbound SMTP with all x-headers intact. This notification contains no confidential data, no file attachment. The Secure Messaging platform servers are used as a different ‘route’ (instead of using unsecure SMTP) and do not create a separate mail store – all company data is still available behind the firewall (optional).Ī basic email notification is sent through SMTP to notify the recipients of their new secure message. NET Framework AES algorithm (AesCryptoServiceProvider class), a FIPS 140-2 compliant library. All data in transit is secured with a minimum of 128bit SSL and 256bit AES at rest encryption using Microsoft’s. The Secure Messaging platform Cloud servers are hosted in Worldclass tier-1 datacenters. At this stage, the user is authenticated and once the data is transferred securely to Secure Messaging platform, the message content and file attachments are encrypted ‘at rest’ using AES 256bit. On ‘SEND’, Outlook intercepts the command and re-routes the message and file attachments securely via HTTPS, instead of sending the encrypted message via SMTP. All data can be stored decrypted in the mail server at the administrator’s preference.Īll communications with the browser or Microsoft Outlook® are secured with HTTPS – confidential data is never exposed to unsecure SMTP route. Microsoft Hosted Exchange® & Office365® and Google Apps® are all supported. No changes are required to the user’s the email address, email program or email server. The user workflow remains practically unchanged. It’s ideal for indexing, searching, archiving and e-discovery. By default, it stores the secure messages decrypted in the mail server. The optional plug-in for Microsoft Outlook® extends the functionality of the system and the patented Delivery Slip without requiring any mail server modifications for both sender and recipient. Support for Hosted or On-premise Email (Microsoft Exchange, Microsoft Office365, Google Apps, Zimbra, etc.)
0 Comments
Leave a Reply. |