Heartbleed Bug in Business

Code BugDo You Still Need to Worry?

There are still worries about the Heartbleed bug in business. How worried should companies and individuals be about their identity and account information online? According to a recent scan from Sucuri, the threat isn’t 100 percent gone. Many websites have fixed the issue yet others are still at risk.

Top Sites Correct Heartbleed Bug in Business Issue

Based on Alexa rankings, Sucuri scanned the top one million websites online for indication of a Heartbleed fix. All sites ranked in the top 1,000 showed up as safe. That covers many sites individuals are likely to visit on a daily basis, including LinkedIn, Facebook, Google, and Twitter. The next level of sites — 10,000 of them — were almost all safe. Only 53 showed susceptibility to the Heartbleed bug. Many of the top 10,000 sites are likely to be banking, shopping, and other popular sites, and experts say the sites consumers and businesses regularly use are unlikely to remain compromised at this time.

20,000 Sites Affected

Even though most large sites have stepped up to answer concerns about the Heartbleed bug in business and personal web use, the Internet isn’t completely clear of this danger. Out of a million sites, Sucuri detected approximately 20,000 sites that still had issues.

Protecting Yourself and Your Business

If you’ve received notification from a site that the Heartbleed bug has been corrected, immediately change your password and other login information. If you aren’t sure whether Heartbleed still impacts a site, you can run a test to see if the OpenSSL code for the site in question is vulnerable.

If you’re serious about protecting yourself and your business from data breaches and identity theft, then you likely already promote common-sense procedures for online security. Put procedures in place in your personal browsing and business computing to check websites for Heartbleed just to be sure your information is protected.

Are you still worried about the Heartbleed bug in your business?