Are suspended law enforcement accounts mostly attackers?

Ike Anude: When we look at the suspensions, they’re not attacks and they’re not from people we can confirm as threat actors. So out of the 727 accounts that were suspended on security grounds, only 56 of them were actually assessed as being compromised or being actual threat actors. Most of them, 671 of them, were for anomalous activity. So this could be something along the lines of maybe they log in from a location or through an IP that is very different than what they usually do or what their agency does.

Ike Anude: And this goes to show that, A, we are hypersensitive, which is a good thing in this case because we’re trying to make sure that everyone who accesses the platform is verified and that our front door is working. And it is a lot better to reject and then reconfirm someone than to allow someone in. So we’d rather fail closed than fail open because it only takes one for an attacker to compromise the network.

Ike Anude, Engineer, Integrations

Kodex Standard Report webinar · November 17, 2026

The counts behind the suspensions

The Kodex Standard Report looks at the law enforcement accounts suspended on security grounds. Ike Anude, an engineer on the Kodex integrations team, gave the numbers on the report’s webinar. Kodex suspended 727 accounts, and each one fell into one of two groups:

  • 56 accounts. Assessed as compromised or run by threat actors.
  • 671 accounts. Suspended for anomalous activity.

In Ike’s words, “only 56 of them were actually assessed as being compromised or being actual threat actors.” Anomalous activity covers the rest: “Most of them, 671 of them, were for anomalous activity.” Ike opened with the conclusion that “they’re not attacks and they’re not from people we can confirm as threat actors.”

What anomalous activity looks like

Ike gave one example. An officer logs in from a location, or through an IP address, that is “very different than what they usually do or what their agency does.” That login stands out against the person’s own history and their agency’s, and Kodex suspends the account while it checks who is on the other end.

The suspension is a flag that Kodex has found a login it can’t explain. The count of 56 gives the number of accounts where the review found a compromised account or a threat actor.

Why Kodex suspends early

Ike said the numbers show that “we are hypersensitive,” and he counts that in the network’s favor. Kodex is “trying to make sure that everyone who accesses the platform is verified and that our front door is working.” He added that “it is a lot better to reject and then reconfirm someone than to allow someone in.” His reasoning starts from the cost of one mistake. A wrongly suspended officer can be reconfirmed. An attacker who gets in can compromise the network.

“We’d rather fail closed than fail open because it only takes one for an attacker to compromise the network.”

Ike Anude, Engineer, Integrations, Kodex

Where to read more

The full benchmark is in the Kodex Standard Report, and the webinar replay has the whole session. For the sign-up side of verification, see How many law enforcement sign-ups fail verification? For the checks themselves, see How does Kodex verify law enforcement requesters?

In Ike’s words

The suspensions are not attacks, and they’re not from people we can confirm as threat actors. Out of the 727 accounts that were suspended on security grounds, only 56 were actually assessed as compromised or as threat actors. Most of them, 671, were for anomalous activity. This could be something along the lines of logging in from a location or through an IP that is very different from what they or their agency usually use.

This shows that we are hypersensitive, which is a good thing in this case, because we’re trying to make sure that everyone who accesses the platform is verified and that our front door is working. It is a lot better to reject and then reconfirm someone than to allow someone in. We’d rather fail closed than fail open, because it only takes one for an attacker to compromise the network.

Edited for length and clarity. From the Kodex Standard Report webinar, November 17, 2026

More questions

See what
we can do
for you.

Request a demo