Vulnerabilities / Threats

5/11/2017
06:20 PM
Connect Directly
Google+
Twitter
RSS
E-Mail
100%
0%

Trump Issues Previously Delayed Cybersecurity Executive Order

EO calls for immediate review of federal agencies' security postures, adoption of the NIST Framework, and a focus on critical infrastructure security.

President Donald Trump today signed an executive order on cybersecurity that squarely places on the shoulders of agency heads the security of their networks, systems, and data, as well as requires their adoption of the National Institute of Standards and Technology's cybersecurity risk framework of best security practices.

The EO, which has been in the works and revised a few times after fits and starts by the administration, for the most part echoes and builds on the policies of previous administrations, including FISMA and the Obama administration's critical infrastructure EO. The "Strengthening US Cyber Security and Critical Infrastructure" EO generally was well-received by cybersecurity experts in policy and technology, with a mix of views over whether it's a gamechanger and how it will roll out.

Among the key elements is a call for modernizing and consolidating government network technologies and infrastructures; a report on the technology supply chain risks to the US Department of Defense; support for security of critical infrastructure; an assessment of cyberattack and disruption of the nation's power grid; and a call for skilled cybersecurity talent.

"Effective immediately, each agency head shall use The Framework for Improving Critical Infrastructure Cybersecurity (the Framework) developed by the National Institute of Standards and Technology, or any successor document, to manage the agency's cybersecurity risk.  Each agency head shall provide a risk management report to the Secretary of Homeland Security and the Director of the Office of Management and Budget (OMB) within 90 days of the date of this order," the EO says.

Christopher Pierson, CSO of Viewpost, says the EO addresses one of the key elements of cybersecurity: ownership. "Each agency head is now on alert that they own cyber as a part of their duties and must govern and appropriate time, budget, and people to tackle this. This is a critical first step as it place the onus on each agency head to make sure cyber is part of their mission," Pierson says. "The one throat to choke for accountability for federal cybersecurity is now clear."

Federal government networks and systems increasingly are being attacked and leaking sensitive data: the Office of Personnel Management (OPM) breaches in 2014 and 2015 that exposed sensitive information on 22 million Americans are a major case in point.

"Every agency has its own systems and does its best theoretically to protect them, and yet we already know federal systems are extraordinarily leaky and critical information is being hacked on a constant basis," says Mike Shultz, CEO of Cybernance, a cyber-risk governance firm. The EO calls for agencies to secure "the entire enterprise, not just harden this piece or that piece, and [specify] how they will manage the whole thing."

"This really represents a dramatic culture shift in the way the federal government is looking at cybersecurity," he says.

Obama administration cybersecurity coordinator Michael Daniel notes that the EO carries on the "general approach to cybersecurity" from both the Bush and Obama administrations, and doesn't necessarily represent any new policy directions. "It will be interesting to see whether the deterrence report and the international strategy will say anything new -- but in general, I don't see anything unusual or that really goes in a different policy direction.  Of course, this order is more of a plan for a plan, because an EO can only direct federal agencies to do things they can already do within the law, but the reports it calls for are good ones to have, for the most part," Daniel says.

Just how federal agencies will meet those goals depends on their in-house expertise, of course. Like the private sector, the feds are struggling to find and hire cybersecurity talent amid a talent gap crisis. It's unclear as yet whether Trump's hiring freeze on federal agencies includes cybersecurity positions, and just how proposed budget cuts could affect their ability to protect their infrastructures, experts say.

Paul Vixie, CEO of Farsight Security, says the EO's section on workforce development is a good addition. "This is a very interesting thing for the executive branch to be focusing on," he says.

The EO calls for the Secretaries of Commerce, Homeland Security, Defense, Labor, Education, and OPM, to assess a report on the US education and training efforts in cybersecurity of the public and private "workforce of the future, including cybersecurity-related education curricula, training, and apprenticeship programs, from primary through higher education."

The cabinet members are tasked with providing their findings and recommendations on this within 120 days, according to the EO. "What recommendations come out of that, I'll be interested to see," Vixie says. "They seem to be saying we need to start teaching 0s and 1s earlier on."

The think-tank Information Technology and Innovation Foundation (ITIF) expressed disappointment in the Trump administration EO. "We are disappointed to see that this executive order is mostly a plan for the government to make a plan, not the private sector-led, actionable agenda that the country actually needs to address its most pressing cyber threats," said Daniel Castro, vice president of ITIF, in a statement. "The last administration put together a commission which left a comprehensive set of action items for the new administration to pursue that should have been the starting point for this order. While the executive order checks most of the boxes thematically, it generally kicks the can down the road instead of taking any decisive actions."

Related Content:

 

Kelly Jackson Higgins is Executive Editor at DarkReading.com. She is an award-winning veteran technology and business journalist with more than two decades of experience in reporting and editing for various publications, including Network Computing, Secure Enterprise ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
'Shift Left' & the Connected Car
Rohit Sethi, COO of Security Compass,  6/12/2018
Why CISOs Need a Security Reality Check
Joel Fulton, Chief Information Security Officer for Splunk,  6/13/2018
Microsoft Fixes 11 Critical, 39 Important Vulns
Kelly Sheridan, Staff Editor, Dark Reading,  6/12/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-1061
PUBLISHED: 2018-06-19
python before versions 2.7.15, 3.4.9, 3.5.6 and 3.7.0 is vulnerable to catastrophic backtracking in the difflib.IS_LINE_JUNK method. An attacker could use this flaw to cause denial of service.
CVE-2018-1073
PUBLISHED: 2018-06-19
The web console login form in ovirt-engine before version 4.2.3 returned different errors for non-existent users and invalid passwords, allowing an attacker to discover the names of valid user accounts.
CVE-2018-12557
PUBLISHED: 2018-06-19
An issue was discovered in Zuul 3.x before 3.1.0. If nodes become offline during the build, the no_log attribute of a task is ignored. If the unreachable error occurred in a task used with a loop variable (e.g., with_items), the contents of the loop items would be printed in the console. This could ...
CVE-2018-12559
PUBLISHED: 2018-06-19
An issue was discovered in the cantata-mounter D-Bus service in Cantata through 2.3.1. The mount target path check in mounter.cpp `mpOk()` is insufficient. A regular user can consequently mount a CIFS filesystem anywhere (e.g., outside of the /home directory tree) by passing directory traversal sequ...
CVE-2018-12560
PUBLISHED: 2018-06-19
An issue was discovered in the cantata-mounter D-Bus service in Cantata through 2.3.1. Arbitrary unmounts can be performed by regular users via directory traversal sequences such as a home/../sys/kernel substring.