- 15 Non-Certified IT Skills Growing in Demand
- How 19 Tech Titans Target Healthcare
- Twitter Suffering From Growing Pains (and Facebook Comparisons)
- Agile Comes to Data Integration
Network World - Joe Lieberman (I-Conn.) retired in January after quite a colorful two-dozen years in the U.S. Senate. One of the major issues he pushed for during his last few years in office was protection of the U.S. critical infrastructure. Along with Sen. Susan Collins (R-Maine), Lieberman put forth a series of bills aimed at requiring some level of protection for such infrastructure, the last of these being voted down in November.
President Obama has now issued a "Presidential Policy Directive" on "Critical Infrastructure Security and Resilience." This directive was accompanied by an Executive Order on "Improving Critical Infrastructure Cybersecurity." Sadly, the president's efforts may turn out to be about as useful as Lieberman's.
[ RELATED: Obama signs cybersecurity order ]
The senator's efforts ultimately failed because 2012 was an election year. But the big beef against his bill was that it actually called for companies to take responsibility for the risks that they had created. Sen. John McCain (R-Ariz.) headed the attacks saying, "unelected bureaucrats at the DHS could promulgate prescriptive regulations on American businesses, which own roughly 90% of critical cyber infrastructure."
I will admit that the fact that the Lieberman/Collins bill would have put the Department of Homeland Security -- you know, the people that bring you the security theater that is the TSA -- in charge of protecting critical infrastructure made it a lot harder to take the proposal seriously. But the McCain assumption that the folks that run our power plants, hospitals, transportation and financial networks will suddenly wake up on their own and start protecting the infrastructures they have so carelessly and assiduously left exposed strains credibility.
The Obama executive order says that the "critical infrastructure" of concern is "where a cybersecurity incident could reasonably result in catastrophic regional or national effects on public health or safety, economic security, or national security." OK, you got me at "catastrophic ... effects." According to the dictionary that came with my Mac, "catastrophic" means "involving or causing sudden great damage or suffering." The type of things that Joel Brenner wrote about in his book "America the Vulnerable." Lots of people dying, the economy collapsing -- fun things like that.
Right now there is no actual legal requirement that the controls for a power company's plants be secure from hacking. There is also no personal liability for anyone working at the power company if they do not exercise common sense to try to protect against vendor stupidity that builds in security vulnerabilities. Nor is there any liability for a vendor that purposefully decides to make its products insecure and fails to tell customers.
There are regulations that require hospitals to protect medical records and universities to protect student educational records, but there are none that require a power company to protect its generating capacity or a hospital to protect its physical plant -- which is just as important to patient care as are the records. Imagine, if you will, what might happen to critically ill patients in a hospital in Dallas if the AC was turned off in mid-August. In this case the hacker went to jail, but what about the hospital engineers who installed the AC controllers in such a way that they were accessible over the Internet? In my opinion, they should share the blame.