PGP's Universal Server Provides Unobtrusive Encryption

Over the last couple of weeks we've looked at the theory behind public key encryption and public key infrastructure. But how is all of this pulled together into a product that enables you to send or receive encrypted e-mail messages?
If you need encryption in an enterprise environment then the ideal solution is as transparent to those using it as possible. That's because any specific steps that users have to take to encrypt their messages are likely to be forgotten, ignored or carried our incorrectly.
For that reason, many organizations choose to install an encryption gateway appliance which encrypts messages after they have been sent by users from standard e-mail clients like Microsoft Outlook, and which decrypts incoming messages before passing them on to their destinations.
One of the earliest public key encryption applications was called Pretty Good Privacy (PGP), written in 1991 by Phil Zimmermann. PGP, Inc. was bought by Network Associates in 1997, but following a management buyout in 2002 PGP morphed into PGP Corporation, which today is one of the best known vendors of corporate encryption solutions. The company's offerings are based around a set of encryption applications--for e-mail and other targets such as mobile devices or storage disks - that use a common encryption platform, plus a management server called PGP Universal Server that oversees them all.
PGP's Universal Gateway Email
PGP's Universal Gateway Email is the company's gateway encryption (and decryption) application. To build a transparent secure e-mail system an organization runs a virtual appliance made up of PGP Universal Server and Universal Gateway Email. This can run on a hardened version of Linux on one of several specific server hardware configurations from vendors including Dell, HP and IBM, or it can take the form of a virtual machine running on VMware ESX.
The appliance is connected between the corporate mail server and the corporate firewall, and when it receives outgoing e-mail messages from the mail server it kicks in to action. The first things the encryption application has to do is decide which messages to encrypt and find the public keys belonging to the recipients of those messages that need to be encrypted. This information is provided by the PGP Universal Server. Its role is to manage and apply rules and policies for encryption, based on factors including the destination, the sender, or even the contents of the message. Account creation, group management and policy enforcement can be automated by integrating Active Directory, Lotus Notes/Domino directories or other LDAP directories with the Universal Server.
Let's imaging that you want to send an e-mail to someone at another organizations, and the Universal Server determines, by looking at the rules and policies that it has to apply, that your message should be encrypted--perhaps because you are working in a confidential new product group. To encrypt the message the encryption software first needs the intended recipient's public key. So how does it get that?












Useful Links