Using SSL to secure all websites may seem like an odd choice; most websites enclose no "nuggets" value taking, SSL apparently slows the page load time (especially on over provisioned hosting platforms), and it isn't clear if doing so can kibosh any search engine optimizations.
Back when I worked at the Bank, I attempted to advance the idea that each page ought to be SSL protected however a number of these same arguments were thrown back to me - “why will it matter if we don’t encrypt the communications when somebody looks for ATM locations?” or “this will totally throw off our gomez rating”. I swear that Gomez is law-of-unintened-consequences accountable for why the majority of banks proffer the less-secure pratice of inserting the unencrypted login page on their main home page - they'll do therefore without compromising the load-time of their web site when measuring the speediness of their own web site against those of their peers. It’s nice to work out that some firms (thanks, Fidelity!) are coming around and imposing the employment of SSL for their entire website.
Oops - I got abstracted. The rationale why I prefer that this blog uses SSL is easy and at one amongst my core philosophies - what you do on the internet ought to be your own business, and net sites ought to help you maintain this level of confidentiality. Even if each web site used (and protected) their own self-signed certificates, users might still profit from the knowledge that no matter they were doing on the web site wasn't visible to others. After all, everybody would need to click "OK" on the certificate error pages, however that behavior already seems well established.
As a lot of as I am for doing this on my own blog, I additionally administer content-filtering for a medium-sized monetary services company -- protecting every web site with SSL would render the bulk of most content filtering applications to straightforward IP-based mostly rules, or cause management to implement clear proxy technologies which would result in really important SSL-protected traffic being visible to a few workers (for that I wouldn't subject myself or my staff to that liability). Additionally, content-filtering systems would probably fail to address massive hosted environments with shared IP addresses.
Therefore - toolsets would need to evolve to address a replacement "always confidential" internet. This includes Google AdWords, which has nevertheless to support SSL websites. Google Analytics still works - however that is a privacy issue, and not a confidentiality one. :)
Author Resource:
Learn more about modern it audit tools at the blog of professional IT Auditor at itechaudit.com
![[Valid RSS feed]](http://www.look4articles.com/images/icon_Rss.png "XML Feed For RSS"){kind=icon}
Category Rss Feed
Print This Article
Add To Favorites
![[Valid RSS feed]](http://www.look4articles.com/images/rss.jpg "XML Feed For RSS")