How might strong encryption be successfully employed within our Web server environment?
Web servers rely upon strong encryption to protect the data sent between users and the Web server. In the absence of strong encryption, any such communications are vulnerable to eavesdropping and modification. This threat could potentially undermine the confidentiality and integrity of financial transactions or other sensitive data that is exchanged with end users.
There are two steps to ensuring strong encryption is being used to protect Web communications. One requires the use of a secure cryptographic protocol, and the other requires that the selected protocol make use of strong cipher algorithms. The cryptographic protocol describes how the Web user and server set-up communications and exchange encryption keys while the cipher algorithm specifies the mathematical operations used to encrypt and decrypt data.
There are two main cryptographic protocols in use on the Web today; the Secure Sockets Layer (SSL) and Transport Layer Security (TLS). TLS is the successor to SSL and is, generally speaking, more secure and preferred to SSL. However, many older Web browsers do not provide support for TLS, so Web servers used by the general public must also support the older SSL protocol. When configuring the protocols used on a Web server, an organization should choose to support both TLS and SSL version 3. Earlier versions of SSL have critical vulnerabilities and should not be used.
To acquire the use of SSLv3 and TLS on a Microsoft IIS Web server, see this Microsoft Knowledge Base article. For Apache servers, include the following directive in your httpd.conf file:
SSLProtocol -ALL +SSLv3 +TLSv1
Both SSL and TLS support a number of cipher algorithms. It is equally important to configure the server to only use cipher algorithms considered secure by the cryptographic community. For Microsoft IIS configuration instructions, see this Microsoft Knowledge Base article. On Apache servers, use this configuration directive:
Related Q&A from Mike Chapple, Enterprise Compliance
The HHS security risk assessment tool is designed to help healthcare providers meet the HIPAA security requirement. Expert Mike Chapple explains how ...continue reading
PCI DSS requirement 6.6 demands application security compliance through one of two options: an application firewall or a code review. Expert Mike ...continue reading
Are HIPAA-compliant hosting services a better option for compliance than a secure storage API? Expert Mike Chapple analyzes.continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.