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.
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.
In this post I’m going to show by example how parallel networking works. Before I do, let me just make one point: Cradlepoint didn't invent parallel networking or another way of protecting data: “air-gapped” networks.
As I mentioned in my previous post (Cradlepoint Makes Its Mark at Mobile World Congress), LTE in Europe is not being used nearly as much as it is in the U.S.—with a few notable exceptions.
On Thursday, Dec. 19, 2013, Target revealed that data from 40 million of its customers’ credit and debit card accounts had been accessed by hackers. I’d like to discuss how and why this happened. But before I do, I want to make it clear that I’m not singling out Target as having done anything wrong. I’m using what happened to them simply to illustrate the kind of situation many companies are facing—even those with very good security systems and personnel.
I recently returned from Mobile World Congress, held annually in Barcelona. It was huge: 85,000 visitors a day and eight enormous halls full of everything from consumer goods to emerging gear for LTE networking.
Part of a network manager’s job is to make sure the stakeholders in your projects understand what you are doing, why you’re doing it, and how well it’s working. NetCloud Manager provides you with the data to support what you’re doing—and it helps you communicate that information to people who may not feel comfortable diving deep inside the data.