Kenneth van Wyk: Looking beyond Heartbleed
We can do things now to make things a little easier should we face another widespread security defect in code like OpenSSL
Computerworld - I have a good idea what you spent the last week and a half doing: putting out Heartbleed fires. But don't stop now! Keep that momentum going for just a bit longer. Let me explain why.
The simple explanation is that Heartbleed was a nasty one. The vulnerability was in OpenSSL, a system library that nearly every piece of networked software relied on. Not only that, but it was used on nearly every network server we might connect to. And not only that, but it had a remote exploit that could render real business-sensitive data to attackers.
In other words, Heartbleed took all the ingredients for a massive migraine and packed them into one little bug. Now, let's do just a bit of a post-mortem and see if there are some opportunities for improvement.
First of all, why is this one such a big deal? We've had other network software zero days before and we've survived those just fine. Well, for one thing, OpenSSL isn't just a piece of network software; it's a library. Any software that was statically linked with the OpenSSL library inherits all of OpenSSL's problems. Let's hear it for dependencies!
Now, in terms of putting out the fires, you should probably have a checklist. Start with fixing OpenSSL itself. Then rebuild (or otherwise update) all the software on your system that was dependent on OpenSSL. What, you don't have a list of those? Uh-oh. Then rebuild everything. Not feasible? OK, now you're getting the picture of just how big a deal Heartbleed was and is.
And that's not even where it ends. You should probably change your password on any third-party Web and mobile apps you use. In fact, many of them have probably been forcing you to do just that. Then there's the actual data that may have gotten breached on any of those systems. Are you concerned about the credit card numbers you left on those systems? You should be.
We're going to be cleaning up after Heartbleed for a long time to come. The direct and indirect impacts of this kind of bug are big, and they don't just go away by updating one piece of software like OpenSSL.
But I said we should look for things we can do to improve. What I'm talking about are things that should make things a little easier should we face another widespread security defect in code like OpenSSL.
Clearly, what made Heartbleed such a heartache for so many people is that so much software is dependent on OpenSSL. One thing I often find lacking in terms of security management is an up-to-date inventory of system dependencies. On any given mission-critical system, it's vital to know not only what software is on that system, but all of its dependencies. This should start with libraries with which the software was linked during its build, but continue on to all of the software frameworks that were used to build the software.
More by Kenneth van Wyk
- Kenneth van Wyk: We can't just blame users
- Kenneth van Wyk: If you want developers to give a hoot about security, take a lesson from the squirrels
- Kenneth van Wyk: Looking beyond Heartbleed
- Kenneth van Wyk: Where mobile apps go wrong
- Kenneth van Wyk: Apple's big fail
- Kenneth van Wyk: After Snowden
- Kenneth van Wyk: Target breach underscores how backward U.S. payment tech is
- Kenneth van Wyk: Enjoy your trip, but protect the data you take with you
- Kenneth van Wyk: Lingering faults with security by default
- Kenneth van Wyk: High hopes for iPhone's Touch ID
- Enable secure remote access to 3D data without sacrificing visual perfomance Design and manufacturing companies must adapt quickly to the demands of an increasingly global and competitive economy. To speed time to market for...
- Virtually Delivered High Performance 3D Graphics "A picture is worth a thousand words." That old phrase is as true today as it ever was. Pictures (i.e., those with heavy...
- Best Practices for Securing Hadoop Historically, Apache Hadoop has provided limited security capabilities. To protect sensitive data being stored and analyzed in Hadoop, security architects should use a...
- Top Tips for Securing Big Data Environments: Why Big Data Doesn't Have to Mean Big Security Challenges Organizations must come to terms with the security challenges they introduce. As big data environments ingest more data, organizations will face significant risks...
- What should I look for in a Next Generation Firewall? SANS Provides Guidance With so many vendors claiming to have a Next Generation Firewall (NGFW), it can be difficult to tell what makes each one different....
- Responding to New SSL Cybersecurity Threat The featured Gartner research examines current strategies to address new SSL cybersecurity threats and vulnerabilities. All Security White Papers | Webcasts
Our new bimonthly Internet of Things newsletter helps you keep pace with the rapidly evolving technologies, trends and developments related to the IoT. Subscribe now and stay up to date!