Connect with us

Hi, what are you looking for?


Incident Response

DHS Details Cyber Incident Reporting Process

DHS Explains Process of Reporting Cyber Incidents to the Federal Government

DHS Explains Process of Reporting Cyber Incidents to the Federal Government

The U.S. Department of Homeland Security (DHS) has published guidelines on when, how and to which government agency US organizations should report cyber incidents. This follows last week’s release of Presidential Policy Directive 41 (PPD-41) on United States Cyber Incident Coordination — which specifically requires the DHS to ‘maintain and update’ such a fact sheet.

The fact sheet (PDF) makes no mention of PPD-41’s Incident Severity Schema. That schema defined six levels (0-5) that provide a common framework for evaluating incident severity; and according to PPD-41, government agencies should get involved from level 3 upwards.

The DHS guidelines first define a cyber incident (“an event that could jeopardize the confidentiality, integrity, or availability of digital information or information systems”), and then define whether the severity of the incident warrants reporting. “Victims,” it explains, “are encouraged to report all cyber incidents that result in significant loss; impact a large number of victims; indicate a compromise of critical IT systems; affect the critical infrastructure; or impact national security, economic security, or public health and safety. Fundamentally, it remains a value judgment by the affected organization.

The primary purpose of the document is to help victim organizations report significant incidents to the correct federal agency. The problem is the range of different agencies with different areas of focus. PPD-41 tried to simplify the problem by dividing incidents into three separate categories: threats, assets, and intelligence, with different agencies taking the lead in different categories. This document makes no mention of the ‘intelligence’ element that would involve the Office of the Director of National Intelligence. 

In some ways, however, it further confuses the reporting by specifying five different agencies for five different nuances of incident. The agencies are:

FBI — for cybercrime ranging from fraud to ‘foreign intelligence activity’

Advertisement. Scroll to continue reading.

National Cyber Investigative Joint Task Force — for major cyber crimes that require assessment for action and investigation

U.S. Secret Service — for intrusions that include password trafficking or involve the theft of payment cards or other financial information

ICE/HSI — for IP theft, illicit e-commerce, smuggling, child pornography and ‘internet-facilitated proliferation of arms and strategic technology’

National Cybersecurity and Communications Integration Center (NCCIC) — for government assistance in removing the adversary and restoring operations

It does, however, make clear that whichever agency receives the initial report, that agency will be responsible for bringing in the other agencies as necessary.

“The federal agency receiving the initial report,” it explains, “will coordinate with other relevant federal stakeholders in responding to the incident.” It also makes clear that such reporting does not negate any separate legal or contractual requirement to report an incident.

Since the majority of the incidents described in the DHS fact sheet will at least start with a cybercrime ranging from fraud to ‘foreign intelligence activity’, it is likely that many organizations seeking government assistance will simply report the incident to the FBI, and leave it to that agency to decide which and when other agencies should be brought in.

Written By

Kevin Townsend is a Senior Contributor at SecurityWeek. He has been writing about high tech issues since before the birth of Microsoft. For the last 15 years he has specialized in information security; and has had many thousands of articles published in dozens of different magazines – from The Times and the Financial Times to current and long-gone computer magazines.

Click to comment

Daily Briefing Newsletter

Subscribe to the SecurityWeek Email Briefing to stay informed on the latest threats, trends, and technology, along with insightful columns from industry experts.

SecurityWeek’s Threat Detection and Incident Response Summit brings together security practitioners from around the world to share war stories on breaches, APT attacks and threat intelligence.


Securityweek’s CISO Forum will address issues and challenges that are top of mind for today’s security leaders and what the future looks like as chief defenders of the enterprise.


Expert Insights

Related Content


A recently disclosed vBulletin vulnerability, which had a zero-day status for roughly two days last week, was exploited in a hacker attack targeting the...

Data Breaches

LastPass DevOp engineer's home computer hacked and implanted with keylogging malware as part of a sustained cyberattack that exfiltrated corporate data from the cloud...

Application Security

GitHub this week announced the revocation of three certificates used for the GitHub Desktop and Atom applications.

Data Breaches

GoTo said an unidentified threat actor stole encrypted backups and an encryption key for a portion of that data during a 2022 breach.

Incident Response

Microsoft has rolled out a preview version of Security Copilot, a ChatGPT-powered tool to help organizations automate cybersecurity tasks.

Incident Response

Meta has developed a ten-phase cyber kill chain model that it believes will be more inclusive and more effective than the existing range of...

Artificial Intelligence

Two new surveys stress the need for automation and AI – but one survey raises the additional specter of the growing use of bring...

Application Security

Password management firm LastPass says the hackers behind an August data breach stole a massive stash of customer data, including password vault data that...