As the old saying goes, when you’re being chased by a bear, you don’t have to run faster than the bear. You just have to run faster than the people you’re with. The same is true when it comes to data security.
Everyone's Blog in All from May 2014
Post Heartbleed, those of us involved in network security could take a lesson from the CDC. One of the biggest barriers to stopping the repeated threats of an Avian Flu pandemic is the resistance on the part of many nations to share information when the flu takes hold in their country. We saw this in May 2013 when China refused to release English-language versions of relevant statistics and facts about an outbreak in their country of a new bird flu called H7N9.
I talked last week about how the Heartbleed bug was unique in how long it went undiscovered, how many things it affected, and how hard it was to tell if anyone had used it to access data. Today I’d like to talk about what Cradlepoint did to reestablish protections for our customers.
Now that the dust has settled in the aftermath of the Heartbleed bug, I thought it might be useful to summarize some of the things Cradlepoint learned and did that will help us better protect our clients in the future. Let me be clear that Cradlepoint acted swiftly to resolve the issues created by Heartbleed as soon as the vulnerability was discovered. I’ll talk about the remediation steps we took in my next post.
Cradlepoint recently announced that we’ve joined the CSA (Cloud Security Alliance), a not-for-profit organization that helps promote the use of best practices for security within cloud computing. As we noted in our press release, our participation within the alliance aligns our cloud-based management solution, NetCloud Manager, with an industry-accepted security framework.