Cloud

6/15/2017
10:30 AM
Carson Sweet
Carson Sweet
Commentary
Connect Directly
Twitter
LinkedIn
RSS
E-Mail vvv
50%
50%

Trumps Executive Order: What It Means for US Cybersecurity

The provisions are all well and good, but it's hardly the first time they've been ordered by the White House.

The WannaCry ransomware attack has dominated headlines recently, and with good reason - it has infected hundreds of thousands of computers in close to 100 countries, shutting down hospitals in the UK, causing problems for companies as large as FedEx, and has so far earned the attackers at least $70,000 in ransom money.

It’s no surprise, then, that President Donald Trump’s Executive Order that seeks to improve cybersecurity across the federal government has flown under the radar since it was signed on May 11. The EO includes provisions for securing critical infrastructure, protecting against botnets and distributed attacks, and encouraging the development of more cybersecurity experts in the government’s workforce.

These provisions are all well and good, but this is hardly the first time they’ve been ordered by the White House. President Barack Obama issued a similar order in 2016, and another one in 2013. Even the Bush administration was concerned about cybersecurity.

High-level orders just like this one come out with every administration, and they all essentially say the same thing: Thou Shalt Assess and Protect. The problem is that the follow-through usually doesn’t deliver the resources agencies need to get it done. Many of the security and compliance requirements, while necessary, are so onerous to implement that they obviate much of the value that agencies seek from cloud models. The question then becomes how well the administration can identify and eliminate the obstructions agencies face as they consider adopting cloud and shared services.

Black Hat USA returns to the fabulous Mandalay Bay in Las Vegas, Nevada, July 22-27, 2017. Click for information on the conference schedule and to register.

In particular, the explicit botnet research component of the order stands out as very odd. It feels almost like it was authored by someone who only very recently learned what a botnet is, was shocked to learn they existed, and now believes they’re the root of many problems. It’s entirely unclear why botnets are highlighted instead of APTs, malware, etc. Ransomware is particularly notable in its absence considering the timing of WannaCry. But in any case, a government directive at this level should be more broadly focused than to call out one individual threat vector in a sea of thousands.

The EO gives both the Office of Management and Budget (OMB) and The Department of Homeland Security (DHS) 60 days to assess how well the current state of federal cybersecurity lives up to all these provisions AND to create a full plan to tackle any and all weaknesses.

The first part of this, simply putting the audit reports together, shouldn’t be too difficult since agencies are likely to have most of this info on hand and will just need to assemble it. The bigger question is how OMB will manage to get through reports for every department of the federal government in only 60 days. Even if the reports are available tomorrow, (and they won’t be), that timeframe is … ambitious. It really doesn’t seem to be informed by a solid understanding of practicalities.

If this Executive Order was part of a truly well-coordinated effort, it would call for the hiring of a Federal CISO to work with all departments to ensure security is consistently implemented across the entire government. This person would be accountable for actually understanding the practicalities and dealing with them, which is key since accountability is trumpeted throughout the order.

Most agencies already have their own CISOs and significant security organizations in place. They not only work to keep their departments secure, but also act as a convenient place for department heads to point fingers when things go awry. The EO emphasizes that this isn’t acceptable and that department heads will have to take full responsibility for their security failures, just as a corporate CEO is held accountable if their own CISO fails to live up to his or her job.

Like so much else in this order, though, this is nothing new. Agency heads have been accountable for some time, so if anything this is really just a loud reiteration of accountability. FISMA (and related standards tied to it) are one example of where accountability has already been established. Without a Federal CISO to oversee everything, it’s hard to see how repeating that people will be held accountable will actually make them accountable.

Only time will tell if this new order will be any more successful than its near identical predecessors at improving government security and keeping future WannaCry level exploits from making their way into the wild.

Related Content:

Carson Sweet is co-founder and chief technology officer for CloudPassage. As founding CEO, Carson led the team that created Halo, the patented security platform that changes the way enterprises achieve infrastructure protection and compliance. Carson's information security ... View Full Bio
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Google Engineering Lead on Lessons Learned From Chrome's HTTPS Push
Kelly Sheridan, Staff Editor, Dark Reading,  8/8/2018
White Hat to Black Hat: What Motivates the Switch to Cybercrime
Kelly Sheridan, Staff Editor, Dark Reading,  8/8/2018
PGA of America Struck By Ransomware
Dark Reading Staff 8/9/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Now about that mortgage refinance offer from Wells Fargo .....
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-6970
PUBLISHED: 2018-08-13
VMware Horizon 6 (6.x.x before 6.2.7), Horizon 7 (7.x.x before 7.5.1), and Horizon Client (4.x.x and prior before 4.8.1) contain an out-of-bounds read vulnerability in the Message Framework library. Successfully exploiting this issue may allow a less-privileged user to leak information from a privil...
CVE-2018-14781
PUBLISHED: 2018-08-13
Medtronic MMT 508 MiniMed insulin pump, 522 / MMT - 722 Paradigm REAL-TIME, 523 / MMT - 723 Paradigm Revel, 523K / MMT - 723K Paradigm Revel, and 551 / MMT - 751 MiniMed 530G The models identified above, when paired with a remote controller and having the "easy bolus" and "remote bolu...
CVE-2018-15123
PUBLISHED: 2018-08-13
Insecure configuration storage in Zipato Zipabox Smart Home Controller BOARD REV - 1 with System Version -118 allows remote attacker perform new attack vectors and take under control device and smart home.
CVE-2018-15124
PUBLISHED: 2018-08-13
Weak hashing algorithm in Zipato Zipabox Smart Home Controller BOARD REV - 1 with System Version -118 allows unauthenticated attacker extract clear text passwords and get root access on the device.
CVE-2018-15125
PUBLISHED: 2018-08-13
Sensitive Information Disclosure in Zipato Zipabox Smart Home Controller allows remote attacker get sensitive information that expands attack surface.