The popular services of Google, Facebook and Twitter are improving in terms of security, says Scott Behrens, head of Neohapsis Labs, which took a security snapshot of them on May 28 through an analysis that included looking at server headers sent during responses to the websites.
Here are some observations Behrens makes about what Neohapsis Labs found:
1. Forcing browsers to use SSL
Companies like Google, Facebook and Twitter are using a technology called HTTP Strict Transport Security (HSTS) to forces browsers over SSL. For example, when users type www.google.com in a browser, the request automatically goes over SSL, making the browsing user experience more secure on the transport layer and helping mitigate man-in-the-middle attacks.
2. Mitigating cross-site scripting
3. Rendering browser content only as explicitly stated
Facebook, Live.com and Gmail utilize X-Content-Type-Options: nosniff, which finally fixes an age old problem where content type is "sniffed" by the browser and rendered even when the Content-Type is explicitly stated. What this means is, when a document's content type is specified as a plain text document, but contains HTML, the browser "sniffs" the content and decides to actually render it as HTML. This can cause serious security issues. The nosniff header is strict and enforces the browser to render content only as explicitly stated.
4. Preventing clickjacking attacks
Clickjacking attacks take advantage of embedded content in iframes by placing elements over those frames and tricking users into clicking actions that seem innocuous, but may be performing malicious actions on the attacker's behalf. Companies like Google, Facebook, Twitter, PayPal, eBay and Live.com are using X-Frame-Options HTTP response header, which either permits or denies the rendering of a page in a frame or iframe element. Since this can block content from being embedded into other sites, it can prevent clickjacking attacks.
Sign up for CIO Asia eNewsletters.