Experience w/ local encryption on servers & CPU load?

In an environment with pretty tough security requirements an idea has come up to use local encryption on servers for many if not all databases.

If this requirement turns out to be real, what kind of CPU impact can we expect on the server. Let’s assume an even mix of simple, medium and strong encryption is used over all databases.

For 4.000 users we were thinking about a Windows based 2-box-cluster, 2-4 Xeons, 4 GB RAM. These would be for databases/applications only, mail would be served by two clusters based on similar hardware. This is Notes clients only, no browser access. Fast is good, they have a special deal enterprise license, processors are cheap, so probably make that 4 Xeons per box.

I know that Windows sounds funny for a system with actual security requirements, but that should be ok when the server is reachable on nothing but port 1352 and an angry pit bull is guarding the safe containing the smartcard-reader in the server rack.

I also know that the proposed hardware would easily handle the load without local encryption, and would remain usable even if one server in a cluster died.

What I don’t know is what locally encrypting everything on a server will do to the CPUs.

Has anybody done this before? What is your experience regarding CPU requirements?

Subject: Experience w/ local encryption on servers & CPU load?

I am prepared to be corrected but I think this would be a bad idea. Not becuase or performance but rather access.

Local Encryption is designed to secure databases stored away from the main Domino environment and accessed by a single user. So when you encrypt the database locally for a user, you find no one else (user or server) can access it. This includes server tasks like compact, replication, fixup, updall, FTI, etc.

I have seen cases where users have locally encrypted their mail files on Domino servers and as a consequence it no longer works correctly (including administration tasks, delegation and calendar freetime lookup in mail files for example).

Instead you should use a mixture of Enforce Consistent ACL and good physical and network security on the server.

Regards

Paul Benwell