Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Cloud

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

Trump’s 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
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 7/9/2020
Russian Cyber Gang 'Cosmic Lynx' Focuses on Email Fraud
Kelly Sheridan, Staff Editor, Dark Reading,  7/7/2020
Why Cybersecurity's Silence Matters to Black Lives
Tiffany Ricks, CEO, HacWare,  7/8/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal, a Dark Reading Perspective
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
The Threat from the Internet—and What Your Organization Can Do About It
The Threat from the Internet—and What Your Organization Can Do About It
This report describes some of the latest attacks and threats emanating from the Internet, as well as advice and tips on how your organization can mitigate those threats before they affect your business. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-15504
PUBLISHED: 2020-07-10
A SQL injection vulnerability in the user and admin web interfaces of Sophos XG Firewall v18.0 MR1 and older potentially allows an attacker to run arbitrary code remotely. The fix is built into the re-release of XG Firewall v18 MR-1 (named MR-1-Build396) and the v17.5 MR13 release. All other version...
CVE-2020-8190
PUBLISHED: 2020-07-10
Incorrect file permissions in Citrix ADC and Citrix Gateway before versions 13.0-58.30, 12.1-57.18, 12.0-63.21, 11.1-64.14 and 10.5-70.18 allows privilege escalation.
CVE-2020-8191
PUBLISHED: 2020-07-10
Improper input validation in Citrix ADC and Citrix Gateway versions before 13.0-58.30, 12.1-57.18, 12.0-63.21, 11.1-64.14 and 10.5-70.18 and Citrix SDWAN WAN-OP versions before 11.1.1a, 11.0.3d and 10.2.7 allows reflected Cross Site Scripting (XSS).
CVE-2020-8193
PUBLISHED: 2020-07-10
Improper access control in Citrix ADC and Citrix Gateway versions before 13.0-58.30, 12.1-57.18, 12.0-63.21, 11.1-64.14 and 10.5-70.18 and Citrix SDWAN WAN-OP versions before 11.1.1a, 11.0.3d and 10.2.7 allows unauthenticated access to certain URL endpoints.
CVE-2020-8194
PUBLISHED: 2020-07-10
Reflected code injection in Citrix ADC and Citrix Gateway versions before 13.0-58.30, 12.1-57.18, 12.0-63.21, 11.1-64.14 and 10.5-70.18 and Citrix SDWAN WAN-OP versions before 11.1.1a, 11.0.3d and 10.2.7 allows the modification of a file download.