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.

Threat Intelligence

3/8/2019
02:45 PM
Connect Directly
Facebook
Twitter
RSS
E-Mail
50%
50%

DHS: No Investigation Planned for Electrical Grid Incursions

The subtext to a panel discussion during RSA is that risks to national infrastructure are fraught with political considerations.

RSA CONFERENCE 2019 – San Francisco – Despite concrete evidence of Russian infiltration of the US electrical grid and acknowledgment of the hacking by the US government, no formal investigation is planned, according to a Department of Homeland Security (DHS) official who spoke here at this week's RSA Conference.

"[Our] worldwide threat assessment looks at threats and capabilities," said Bob Kolasky, director of the National Risk Management Center, which is part of DHS. The complexity of the malware like what attacked Ukraine's electrical grid "is still largely theoretical," he added. "We will look at what's going on, but we don't do technical investigations. We have some idea of the threat."

Pressed by an audience member about whether there was sufficient evidence and cause to investigate bad actors and vulnerabilities associated with the US electrical grid, Kolasky demurred. "We jump on planes when we're asked to jump on planes,” he said. "There's the reality of malware that [electrical grid operators] don't want on their systems."

Kolasky's comments were part of a panel discussion Monday night examining security challenges to critical infrastructure in the US. More than once, panelists invoked 9/11 and the many lessons learned around threat assessment, preparedness, and defense. Several also highlighted the ongoing challenges of getting multiple government entities to work together, share information, and decide who leads an investigation.

In other words, the politics of malware.

"From a threat perspective, we start with nation-states – China, Russia, North Korea, and Iran – and look at what they're interested in," Kolasky explained.

In general, he added, their intent is to advance their own industries and take out competitors. Russia, according to Kolasky, is most interested in undermining liberal democracy, whether it's elections, social media, or just sowing general contempt. "There are risks to information systems and information," he said. "Where does it become an issue, undermining the economy and the nation? That's the conversation we want to have."

The interlude over what might prompt the feds to mount a full-bore cybersecurity investigation was in contrast to the rest of the discussion, where panelists with long federal government resumés vigorously agreed plenty of progress has been made around information sharing among agencies and departments. They were also quick to add that plenty of challenges remain.

"9/11 was the bloody nose for us – what's happened in counter-terrorism is really the model for cybersecurity going forward," said Brig. Gen. Francis X. Taylor, who once served as undersecretary for intelligence and analysis at DHS and was the first CSO at General Electric Co. Just as the feds learned to work with and share information with local police departments after the 2001 attacks, federal agencies and departments can do a better job of working with their state and local counterparts and private-sector security pros, he said.

Taylor advocated for more sharing of unclassified information; what's less clear is who manages that or what the sharing platform should be. "It takes a leader, and I think DHS is the right leader," he said, adding that information can't just be shared on a "need-to-know" basis – a common stalling tactic in the intelligence community. Information about cybersecurity needs to be always available, Taylor said.

Cybersecurity politics aren't limited to the feds; highly regulated industries like oil and gas are extra cautious about what they do, noted Suzanne Lemieuxmanager, midstream and industry operations, at the American Petroleum Institute, and another panelist. "Our companies are limited in what they can share with each other as competitors [operating] under antitrust restrictions," she explained.

Lemieux noted improvements for cybersecurity, such as the formation of the ONG information analysis center. API members share threats they see with other industries, like with electrical grid opportunities, because oil and gas companies recognize they're not the only targets.

"We also have partnerships with DHS, TSA, and others, but [sharing information] is just as much a challenge outside the government," Lemieux said. "We're trying to figure out what that model looks like."

Related Content:

 

 

 

Join Dark Reading LIVE for two cybersecurity summits at Interop 2019. Learn from the industry's most knowledgeable IT security experts. Check out the Interop agenda here.

Terry Sweeney is a Los Angeles-based writer and editor who has covered technology, networking, and security for more than 20 years. He was part of the team that started Dark Reading and has been a contributor to The Washington Post, Crain's New York Business, Red Herring, ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Major Brazilian Bank Tests Homomorphic Encryption on Financial Data
Kelly Sheridan, Staff Editor, Dark Reading,  1/10/2020
Exploits Released for As-Yet Unpatched Critical Citrix Flaw
Jai Vijayan, Contributing Writer,  1/13/2020
Microsoft Patches Windows Vuln Discovered by the NSA
Kelly Sheridan, Staff Editor, Dark Reading,  1/14/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Post a Comment
Current Issue
The Year in Security: 2019
This Tech Digest provides a wrap up and overview of the year's top cybersecurity news stories. It was a year of new twists on old threats, with fears of another WannaCry-type worm and of a possible botnet army of Wi-Fi routers. But 2019 also underscored the risk of firmware and trusted security tools harboring dangerous holes that cybercriminals and nation-state hackers could readily abuse. Read more.
Flash Poll
[Just Released] How Enterprises are Attacking the Cybersecurity Problem
[Just Released] How Enterprises are Attacking the Cybersecurity Problem
Organizations have invested in a sweeping array of security technologies to address challenges associated with the growing number of cybersecurity attacks. However, the complexity involved in managing these technologies is emerging as a major problem. Read this report to find out what your peers biggest security challenges are and the technologies they are using to address them.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-3686
PUBLISHED: 2020-01-17
openQA before commit c172e8883d8f32fced5e02f9b6faaacc913df27b was vulnerable to XSS in the distri and version parameter. This was reported through the bug bounty program of Offensive Security
CVE-2019-3683
PUBLISHED: 2020-01-17
The keystone-json-assignment package in SUSE Openstack Cloud 8 before commit d7888c75505465490250c00cc0ef4bb1af662f9f every user listed in the /etc/keystone/user-project-map.json was assigned full "member" role access to every project. This allowed these users to access, modify, create and...
CVE-2019-3682
PUBLISHED: 2020-01-17
The docker-kubic package in SUSE CaaS Platform 3.0 before 17.09.1_ce-7.6.1 provided access to an insecure API locally on the Kubernetes master node.
CVE-2019-17361
PUBLISHED: 2020-01-17
In SaltStack Salt through 2019.2.0, the salt-api NEST API with the ssh client enabled is vulnerable to command injection. This allows an unauthenticated attacker with network access to the API endpoint to execute arbitrary code on the salt-api host.
CVE-2019-19142
PUBLISHED: 2020-01-17
Intelbras WRN240 devices do not require authentication to replace the firmware via a POST request to the incoming/Firmware.cfg URI.