Threat Intelligence

5/22/2018
03:45 PM
Connect Directly
Twitter
LinkedIn
Google+
RSS
E-Mail
50%
50%

US Senator to DOD CIO: 'Take Immediate Action' on HTTPS

US Senator Ron Wyden pens a letter to the Department of Defense CIO, urging stronger security on public-facing government sites.

HTTPS adoption has grown to the point where it can, and should, be considered the standard for Web security. The problem is that not all organizations have jumped on board — including the United States Department of Defense (DOD), which runs several sites that lack HTTPS encryption.

In a strongly worded letter to DOD CIO Dana Deasy, US Senator Ron Wyden, D-Ore., urges "immediate action" on the adoption of cybersecurity best practices for all publicly accessible DOD Web services.

A handful of DOD sites, including the Army, Air Force, and National Security Agency homepages, have HTTPS by default and use certificates trusted by major browsers, Wyden writes. Several others — namely, the websites for the Navy, Marines, and the CIO office itself — either don't encrypt connections or only verify their authenticity with a DOD Root Certificate Authority.

"Many mainstream web browsers do not consider these DoD certificates trustworthy and issue scary security warnings that users are forced to navigate before accessing the website's information," writes Wyden in his letter. The poor user experience affects civilians and service members, all of whom must face security warnings when visiting DOD webpages.

This isn't the first time the government has been mandated to improve its Web security. In 2015, the Office of Management and Budget (OMB) issued a memo instructing federal agencies to enable HTTPS encryption and enforce it with HTTP Strict Transport Security (HSTS) by the end of 2016. In 2017, the Department of Homeland Security issued a directive emphasizing the OMB's requirements and requiring civilians to practice better security hygiene.

"Any public-facing website is a gateway to exposing personal information, getting any sorts of data that can be detrimental against the Department of Defense," says Mike Chung, head of government solutions at Bugcrowd, which last year ran the Hack the Pentagon event to improve security for public-facing government websites.

The security implications if Wyden's requests aren't fulfilled could affect all government agencies, which hold personal data that can be exposed or extracted, he continues. "To me, it's all that sensitive data they hold in their IT infrastructure that has the potential to be hacked into," Chung says of the repercussions. "That could be the absolute worst-case scenario."

HackerOne advisor Lisa Wiswell agrees. "HTTPS has been industry best practice for way too long to not have every single public facing website owned or operated by the US Federal or State Governments converted," she says. "Plain text is not acceptable - no matter if you're inputting personallu identifiable information or just browsing a website."

There's little doubt the security community will be watching the response from Deasy, who was appointed to the role of DOD CIO in April and most recently held the position of CIO at JPMorgan Chase. Addressing these issues is "absolutely a must" for him, Chung notes.

Wyden says "the DoD cannot continue these insecure practices" because the consequences of staying stagnant are growing greater. Starting in July, Google plans to acknowledge HTTPS as the expected standard by removing the "secure" label from HTTPS websites and marking all HTTP sites as "not secure," alerting users whenever they visit unencrypted pages.

Google's warnings will weaken public trust in the DOD's ability to defend against cybercrime, according to Wyden. The DOD sets a poor example by teaching people to dismiss critical security warnings as irrelevant. Normalizing these alerts drives the risk of cyberattacks and foreign-government hacking: if the DOD doesn't prioritize security, civilians have less incentive to do the same.

The letter closes with three key security recommendations. Wyden urges Deasy to adopt the guidelines described in memos from the OMB and DHS, obtain and deploy certificates trusted by major Web browsers for all publicly accessible services, and evaluate the use of shorter-lived, machine-generated certificates.

That said, Deasy will need to do more than adopt HTTPS to strengthen the government's security posture. "My hope is that this new CIO will take it to the next level and really have the opportunity to do an assessment across all DOD public-facing websites, as well as mobile apps," Chung says. This may mean, for example, launching more crowdsourced initiatives to mitigate the lack of skilled security pros in the government.

It's a difficult time for government cybersecurity, which finds itself in a tough position as it loses a cybersecurity coordinator amid growing threats. Data shows federal agencies have the least-secure applications across industry sectors, with just 4% of federal apps scanned weekly.

"I don't know if the DOD is well-prepared to fight the cyber war," says Chung. "There's a lack of resources, lack of preparedness, lack of understanding of where these different attack vectors can come from."

Related Content

Kelly Sheridan is the Staff Editor at Dark Reading, where she focuses on cybersecurity news and analysis. She is a business technology journalist who previously reported for InformationWeek, where she covered Microsoft, and Insurance & Technology, where she covered financial ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Russia Hacked Clinton's Computers Five Hours After Trump's Call
Robert Lemos, Technology Journalist/Data Researcher,  4/19/2019
Tips for the Aftermath of a Cyberattack
Kelly Sheridan, Staff Editor, Dark Reading,  4/17/2019
Why We Need a 'Cleaner Internet'
Darren Anstee, Chief Technology Officer at Arbor Networks,  4/19/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
5 Emerging Cyber Threats to Watch for in 2019
Online attackers are constantly developing new, innovative ways to break into the enterprise. This Dark Reading Tech Digest gives an in-depth look at five emerging attack trends and exploits your security team should look out for, along with helpful recommendations on how you can prevent your organization from falling victim.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-11498
PUBLISHED: 2019-04-24
WavpackSetConfiguration64 in pack_utils.c in libwavpack.a in WavPack through 5.1.0 has a "Conditional jump or move depends on uninitialised value" condition, which might allow attackers to cause a denial of service (application crash) via a DFF file that lacks valid sample-rate data.
CVE-2019-11490
PUBLISHED: 2019-04-24
An issue was discovered in Npcap 0.992. Sending a malformed .pcap file with the loopback adapter using either pcap_sendqueue_queue() or pcap_sendqueue_transmit() results in kernel pool corruption. This could lead to arbitrary code executing inside the Windows kernel and allow escalation of privilege...
CVE-2019-11486
PUBLISHED: 2019-04-23
The Siemens R3964 line discipline driver in drivers/tty/n_r3964.c in the Linux kernel before 5.0.8 has multiple race conditions.
CVE-2019-11487
PUBLISHED: 2019-04-23
The Linux kernel before 5.1-rc5 allows page->_refcount reference count overflow, with resultant use-after-free issues, if about 140 GiB of RAM exists. This is related to fs/fuse/dev.c, fs/pipe.c, fs/splice.c, include/linux/mm.h, include/linux/pipe_fs_i.h, kernel/trace/trace.c, mm/gup.c, and mm/hu...
CVE-2018-7576
PUBLISHED: 2019-04-23
Google TensorFlow 1.6.x and earlier is affected by: Null Pointer Dereference. The type of exploitation is: context-dependent.