Organizations have been relying on secure socket layer to protect passwords, credit card details and personal information. But if the U.S. is collecting encrypted information, does it need strengthening?

One of the fallouts from the leaks by former NSA consultant Edward Snowden is that people are paying more attention now to what data intelligence agencies are collecting.

In the wake of a report last month from The Guardian that the NSA can keep encrypted information indefinitely comes a blog from Internet security firm Netcraft that SSL, one of the oldest security protocols, isn’t safe any more. Instead organizations should turn to PFS – perfect forward secrecy – for better encryption

Serdar Yegulalp of Network Computing interviewed a software engineer who adds some extra context. The link is below.
(Image from Shutterstock)

Some background: SSL – short for security sockets layer, and more recently called TLS – is used by browsers to protect passwords, credit card details and personal information. You’ll find it enabled when the browser URL reads “https”. But, argues Netcraft, if SSL’s private key is cracked or made available through a court order, then all of a Web site’s traffic can be decrypted at once.

 PFS, used in conjunction with SSL, makes that very difficult because it generates a temporary key. If you follow along, Yegulalp’s engineer agrees that SSL works best with PFS enabled.

Web site administrators will find this informative.

Read the whole story here.

Related Download
Cisco Secure Mobility Knowledge Hub Sponsor: Cisco
Cisco Secure Mobility Knowledge Hub
This Knowledge Hub provides an end-to-end look at what it takes to discover, plan, and implement a successful Secure Mobility strategy.
Learn More
Share on LinkedIn Share with Google+ Comment on this article
More Articles