Tools for protecting internal e-mail traffic

Company's internal e-mail traffic protection utilizes S/MIME encryption. The message is sent to the receiver with D-Envelope and therefore there is no need for complicated key/password exchange even though the messaging remains confidential throughout the whole message chain.

Secure Email can generate its own virtual certificates or keys (intended to be used between user and Sec@GW) or the organisations own certificates or keys can be used. The administrator can send users' certificates or keys to internal users or users can order them from Sec@GW. User can order the receiver's certificate or public key from Secure Email and then save the receiver address with certificate or key as contact to the e-mail client's address book or simply reply to the message sent by the system and select the message to be encrypted and signed.

• Using internal S/MIME encryption: Message will be sent S/MIME encrypted to the Secure Email server, which sends the messages to the receiver either in plain text or as encrypted message according to the rules configured to the server. Reply messages will be routed to Secure Email where they are S/MIME encrypted and delivered to the user's inbox.

• Internal S/MIME registration (default: off): The internal user can protect the internal e-mail traffic with S/MIME encryption.