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.

Risk

Feds, ISPs Team On Cybersecurity For Defense Contractors

The Departments of Defense and Homeland Security are providing cyber threat intelligence to 25 defense contractors and their Internet service providers.

Inside DHS' Classified Cyber-Coordination Headquarters
(click image for larger view)
Slideshow: Inside DHS' Classified Cyber-Coordination Headquarters
The Department of Defense (DOD) and the Department of Homeland Security (DHS) are working with Internet service providers to provide stronger cybersecurity protection for defense contractors, a DOD official said this week.

The DOD is sharing classified information about cyber threats with defense contractors and their network providers through an experimental program called the Defense Industrial Base (DIB) Cyber Pilot, Deputy Secretary of Defense William J. Lynn said in a speech in Paris. A transcript of his comments is available online.

Through the pilot--which began last week--the agencies also work with defense contractors to use the threat information in a practical way to shore up their networks, he said.

"By furnishing network administrators with this threat intelligence, we will be able to strengthen the existing cyber defenses at defense companies," Lynn said.

While the pilot is a collaborative effort between the DOD and DHS, the National Security Agency is providing technical advice and cyber security information upon request by the DOD, DOD spokesperson April Cunningham said in an email.

She declined to name the ISPs or defense contractors participating in the pilot, but said that there are about 25 of the latter involved. A published report by the Washington Post identifies the ISPs as AT&T, Verizon, and CenturyLink, and some of the contractors--of which the report said there are 15--as Lockheed Martin, CSC, SAIC and Northrop Grumman.

The move is yet another example of the Obama administration's willingness to forge partnerships between the public and private sector to secure critical U.S. networks and infrastructure, which mainly are owned, managed, or controlled by entities outside the public sector.

The federal government currently has a number of early efforts under way to share intelligence information around cyber threats between the public and private sectors to improve cybersecurity. Through one pilot program launched last year, the DHS shares threat intelligence information with some private-sector CIOs and cyber security officers if it will protect their networks.

Still, the federal government has struggled to achieve the right balance and to disseminate information in a way that satisfies all stakeholders.

Lynn said the pilot "breaks new grounds on several fronts" in its breakdown of barriers between the public and private sector for the good of cybersecurity.

However, he acknowledged the feds still "have a long way to go and a lot of work to do" to fully secure critical infrastructure, and he said he believes the DIB Cyber Pilot could be a framework in the future for similar work with other industry stakeholders.

"By establishing a lawful and effective framework for the government to help operators of one critical infrastructure sector defend their networks, we hope the DIB Cyber Pilot can be the beginning of something bigger," Lynn said. "It could serve as a model that can be transported to other critical infrastructure sectors."

What industry can teach government about IT innovation and efficiency. Also in the new, all-digital issue of InformationWeek Government: Federal agencies have to shift from annual IT security assessments to continuous monitoring of their risks. Download it now. (Free registration required.)

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 4/7/2020
The Coronavirus & Cybersecurity: 3 Areas of Exploitation
Robert R. Ackerman Jr., Founder & Managing Director, Allegis Capital,  4/7/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
6 Emerging Cyber Threats That Enterprises Face in 2020
This Tech Digest gives an in-depth look at six emerging cyber threats that enterprises could face in 2020. Download your copy today!
Flash Poll
State of Cybersecurity Incident Response
State of Cybersecurity Incident Response
Data breaches and regulations have forced organizations to pay closer attention to the security incident response function. However, security leaders may be overestimating their ability to detect and respond to security incidents. Read this report to find out more.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-11655
PUBLISHED: 2020-04-09
SQLite through 3.31.1 allows attackers to cause a denial of service (segmentation fault) via a malformed window-function query because the AggInfo object's initialization is mishandled.
CVE-2020-11656
PUBLISHED: 2020-04-09
In SQLite through 3.31.1, the ALTER TABLE implementation has a use-after-free, as demonstrated by an ORDER BY clause that belongs to a compound SELECT statement.
CVE-2019-20637
PUBLISHED: 2020-04-08
An issue was discovered in Varnish Cache before 6.0.5 LTS, 6.1.x and 6.2.x before 6.2.2, and 6.3.x before 6.3.1. It does not clear a pointer between the handling of one client request and the next request within the same connection. This sometimes causes information to be disclosed from the connecti...
CVE-2020-11650
PUBLISHED: 2020-04-08
An issue was discovered in iXsystems FreeNAS 11.2 and 11.3 before 11.3-U1. It allows a denial of service.
CVE-2020-11653
PUBLISHED: 2020-04-08
An issue was discovered in Varnish Cache before 6.0.6 LTS, 6.1.x and 6.2.x before 6.2.3, and 6.3.x before 6.3.2. It occurs when communication with a TLS termination proxy uses PROXY version 2. There can be an assertion failure and daemon restart, which causes a performance loss.