A few weeks ago I had a chance to attend the PCI Security Standards Council’s 2014 North American Community Meeting in Orlando, Florida. (PCI is shorthand for the Payment Card Industry Data Security Standard, a guideline to help organizations that process, store or transmit card payments.) Two highlights for me were presentations by the PCI’s new general manager Stephen W. Orfei, and another by Adm.
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.
One of the key metrics of network performance is uptime—the percentage of time a company’s system is connected to a network or the Internet. Typically, when people look for the causes of the loss of connectivity, they usually think in terms of service interruptions: a physical line being cut or lightening striking a utility pole.