Key Management

Secure Messaging requires only one set of keys - one public and one private, per company. The company's public key can be automatically attached to every outgoing message via a public key macro that is inserted into the user's signature file. This is set up via the Secure Messaging Manager at the server level and requires no end user interaction. All incoming public keys are recognized by the Secure Messaging Server and automatically added to the company's public key ring. The message recipient at the company is also notified that the sender's key has been added.

Relay Architecture

Secure Messaging is able to minimize the administration of key management because of its relay architecture. Many fewer public and private keys are needed between organizations who use Secure Messaging. Relay architecture allows all of the security functions to be controlled and applied by the administrator, saving users the time and frustration of managing these functions on their own PCs. Also, relay architecture helps the company avoid the long delays that can occur with real-time encryption when messaging volume is at a peak.

Example

Company A has 10 locations and a total of 1000 users. They do not use Secure Messaging's relay architecture. Key management in Company A involves 1,001,000 keys. (1000 users x 1000 public keys + 1000 private keys)

Company B also has 10 locations and a total of 1000 users. They are a Secure Messaging user with relay architecture. Key management in Company B involves a total of 110 keys. (10 locations x 10 public keys + 10 private keys)

In Company A, key pairs are managed at the user level resulting in each employee having to manage 1000 public keys ( 1 for each employee including themselves, plus their own private key. In Company B, fewer keys ( 11 )are managed at each location because they are administered at the server level.

The benefit here is the many fewer keys that need to be managed and that end users do not have to worry about setting any levels of trust. The Server manages the keys and the administrator applies the level of trust to all incoming public keys.