Technology

FBI and USDA Reportedly Hit by Back-to-Back Cyberattacks

Martin HollowayPublished 3 min readBased on 3 sources
Reading level
FBI and USDA Reportedly Hit by Back-to-Back Cyberattacks
Photo by Tony Webster / CC BY 2.0

The FBI and the US Department of Agriculture were reportedly targeted in back-to-back cyberattacks earlier this week, and the intrusions may have given the attackers access to the USDA's payments systems and the FBI's criminal database, according to Engadget.

The USDA incident surfaced first. NBC News reported that some USDA systems went offline on Thursday because of a "cybersecurity incident." The breach affected the department's payments database. NBC News also reported that the USDA warned its employees that accessing the payments system could expose more sensitive information.

The FBI case involves a different class of data. CNN first reported the FBI breach on Friday, citing "two people briefed on the issue." The target was the National Crime Information Center (NCIC), the database that holds criminal information such as warrants and background checks. Law enforcement agencies across the country query it routinely. The reported access was to that system specifically, not to the agency's broader networks.

Several basic questions remain open. Reporting has not established who was behind either incident, or whether the two attacks were related. Both were described as reported rather than confirmed, so the scope of any data taken, and whether the two intrusions share tooling, infrastructure or an operator, is not yet known.

The two systems sit at very different points in the trust model, meaning the rules that decide which accounts and systems may reach which data. A payments database carries financial records, banking details and personal identifiers tied to program recipients. The USDA's warning to staff suggests the exposure extends beyond those transaction records. The NCIC is a different kind of asset. Officers in the field query it in real time, and its records feed decisions about arrests, stops and firearm eligibility. Read-only access to such a store would be a serious problem. Write access, if it occurred, would be far worse. Neither possibility has been established.

The broader context here is a pattern government agencies have faced for years. Legacy systems, shared credentials and third-party integrations create lateral movement paths, the routes an intruder can take from one system to another, and defenders often struggle to map them. A payments platform and a law enforcement database have very different threat models, yet both can be reached by the same kind of adversary, one that exploits weak identity controls and misconfigured remote access. Whether these incidents reflect a single campaign or two unrelated intrusions that landed in the same week will shape the response. That answer will come from forensic work, not from press accounts.

In my view, the most useful lesson for practitioners is that the blast radius of a federal breach, meaning how much damage one compromise can do, is set by how systems are segmented and how identity is enforced. It is not set by the classification label on the data. An agency that keeps its payments path and its criminal records path on separate identity planes, with privileged access gated and logged, limits the damage from any single compromise. These are standard controls, not new ones. They are often the difference between an incident that takes a system offline for a day and one that exposes records for years.

There is also a constructive side to the story. Both agencies have a visible incident to work from, and systems like the NCIC and the payments platform generate large volumes of audit data. Once examined, that forensic record should clarify what was accessed, for how long, and through which path. That clarity is what allows the government to tighten its controls and, eventually, to say precisely what happened. For now, the rest depends on what the investigation establishes.