#Windows server 2008 security guide manual#
#Windows server 2008 security guide software#

Following a fully redundant deployment scenario where there are 6 machines (2 x web, 2 x console, 2 x DB) there would be 4 HSM devices.

This means if the intention is to use a local PCI device, an HSM would be installed wherever there is a management console/deferred processor/zone processor or a web site. The encryption process takes place before information is ever written to the data store (MS SQL/Oracle). Change the default password on the password store access from within the console.

#Windows server 2008 security guide manual#

This is a manual process but helps to ensure no data required to access the stored passwords remains static indefinitely.

Change the program encryption key periodically.

Export the encryption key post installation and store in a secured location, preferably as an encrypted file.

For better protection consider disabling SSLv3 at the server level and force the use of the latest TLS scheme. The use of SSL certificates to implement an HTTPS connection is a function of IIS.

Use SSL protection from the web server to the client browser.

Enable Transparent Data Encryption (TDE) in the program data store to further protect data at rest.

Thus we are never sending clear text passwords, though there is other auditing and system information which would be passed in the clear and the SSL connection would help further protect that. In the same breath, whenever we transmit passwords to or from the database, those values are already encrypted by our crypto provider or the HSM if implemented. This has the benefit of ensuring absolutely no data is transmitted in clear text over the wire.

SQL Server supports SSL connections for its network traffic and we support those methods as well.

Use Secure Sockets Layer (SSL) protection for the SQL database connections.

Whether this is provided as a network device or a local PCI device is up to you local PCI is obviously faster but can be much harder to manage when dealing with virtual machines or distributed components. Using an HSM will remove the key management from main system memory and provide further encryption protection as addressed by FIPS 140-2 level 2 and level 3 mechanisms.

#Windows server 2008 security guide software#

Although the software encryption is the Federal Information Processing Standards (FIPS)Р’В certified algorithm, it is encryption done in software which means the clear text information and encryption keys are in main system memory and CPU.

Encryption of passwords in the database - Use a Hardware Security Module (HSM)Р’В such as those offered by Safenet or Entrust nCipher.