recommended reading

Government Isn't Sharing Cyber Threats As Promised, Private Sector Says


When it comes to cyber threat information sharing, it’s government that’s not holding up its end of the bargain, industry officials told lawmakers Thursday.

Government classification frequently hinders cybersecurity companies’ ability to share information with clients and others in the private sector, effectively giving an adversary a broader playing ground, witnesses told members of the House Homeland Security Committee’s cybersecurity panel.

For example, when the U.S. Navy was breached by Iranian government-linked hackers using a very simple attack vector in 2014, government investigators’ hesitancy to share information may have put private-sector companies in danger of similar attacks, Intel Security Vice President Scott Montgomery said.

» Get the best federal technology news and ideas delivered right to your inbox. Sign up here.

“By classifying the event, what we’re doing is restricting the number of people who can lend assistance and also allowing the adversary to operate with impunity,” Montgomery said. “If we can release this information sooner, we’re actually affecting not only government, but private-sector organizations that [are vulnerable to] this same very, very common very low-hanging fruit attack.”

That particular attack relied on a common and known cyber exploit industry could easily patch against if it hadn’t already, he said.

Congress passed legislation in 2015 shielding companies from legal liability when they share cyber threat information with the government. The new law has helped ease the path for information to travel in one direction, industry representatives say, but done less in the other direction.  

If government could more readily share threat information—even wiped of much identifying information and in a classified setting with company officials who hold security clearances—it would greatly aid private companies that may face similar threats, said Daniel Nutkis, CEO of HITRUST Alliance, a nonprofit cybersecurity organization for the health care sector.

“The term I can’t stand hearing is ‘active law enforcement investigation,’ which shuts down sharing,” he said. “They’ll reach out, they’ll ask for a whole bunch of stuff or we’ll share a whole bunch of stuff with them and then everything stops. … We’re not sure why they can’t share back. We’re trying to work the same incident they are.”

There are ways in which the government has made improvements, Palo Alto Networks Vice President Ryan Gillis said, especially when multiple federal agencies work on the same private-sector breach.

Such cross-agency responses are common in cyberspace where the Homeland Security Department may be helping a critical infrastructure provider mitigate a particular breach while the FBI seeks information for a possible prosecution and an industry-specific regulator is gathering its own information.

The FBI and Secret Service, which investigates cyber crimes against financial firms, have begun working together more seamlessly when their jurisdictions overlap, Gillis said.

It’s also much less common for different federal agencies to require breached companies and private threat investigators to abide by separate nondisclosure agreements with different requirements, he said.

Threatwatch Alert

Network intrusion / Software vulnerability

Hundreds of Thousands of Job Seekers' Information May Have Been Compromised by Hackers

See threatwatch report


Close [ x ] More from Nextgov

Thank you for subscribing to newsletters from
We think these reports might interest you:

  • It’s Time for the Federal Government to Embrace Wireless and Mobility

    The United States has turned a corner on the adoption of mobile phones, tablets and other smart devices, outpacing traditional desktop and laptop sales by a wide margin. This issue brief discusses the state of wireless and mobility in federal government and outlines why now is the time to embrace these technologies in government.

  • Featured Content from RSA Conference: Dissed by NIST

    Learn more about the latest draft of the U.S. National Institute of Standards and Technology guidance document on authentication and lifecycle management.

  • A New Security Architecture for Federal Networks

    Federal government networks are under constant attack, and the number of those attacks is increasing. This issue brief discusses today's threats and a new model for the future.

  • Going Agile:Revolutionizing Federal Digital Services Delivery

    Here’s one indication that times have changed: Harriet Tubman is going to be the next face of the twenty dollar bill. Another sign of change? The way in which the federal government arrived at that decision.

  • Software-Defined Networking

    So many demands are being placed on federal information technology networks, which must handle vast amounts of data, accommodate voice and video, and cope with a multitude of highly connected devices while keeping government information secure from cyber threats. This issue brief discusses the state of SDN in the federal government and the path forward.

  • The New IP: Moving Government Agencies Toward the Network of The Future

    Federal IT managers are looking to modernize legacy network infrastructures that are taxed by growing demands from mobile devices, video, vast amounts of data, and more. This issue brief discusses the federal government network landscape, as well as market, financial force drivers for network modernization.


When you download a report, your information may be shared with the underwriters of that document.