The work begins with knowing who's on the other end.
Kodex verifies every requester against a network of 15,000 government agencies and 140,000+ vetted agents. Continuously, before they reach your team.
.png)
banks, and telcos run on Kodex.
The old way of verifying a requester doesn't hold up anymore.




The Kodex identity assurance program.
Identity assurance is a measured discipline. NIST publishes the standards the rest of the industry references. Kodex meets those standards and adds what NIST does not define.

Identity proofing
NIST IAL2 for remote proofing, with IAL3-grade controls on the highest-risk reviews. Agency affiliation, credential validation, evidence collection, and trained human review.

Authentication
NIST AAL2 enforcement, with phishing-resistant options available.

Network data
Cross-customer signal correlation across 15,000 agencies and 140,000+ investigators. Detection at one company becomes protection for all of them.

Threat intelligence
Dark web monitoring, stealer log indexing, threat actor tracking, forged document detection. Built for the law enforcement request channel and run continuously.
How verification works on Kodex.
Every requester is checked against the Kodex Global Network before they get in, and the check never really ends. Verification on Kodex happens in four places, each one closing a gap the others can't see.

Onboarding
Agency affiliation, credentials, device, network signal. Clean applicants clear automatically. The rest go to the Kodex Threat Intelligence team for human review. No one gets on the network on the strength of an email address alone.

Continuous
Verification doesn't stop at sign-up. Every active agent is re-checked against sign-in metadata, behavioral patterns, and credential state in the wild. A credential compromised on Tuesday is flagged before it gets used on Wednesday.

Per request
Every request is re-verified against the live state of the requester at the moment of submission. Not the state at sign-up. Not the state last week. This is what closes the gap on procedurally correct requests sent from compromised accounts.

Network-wide
Signals from one customer correlate against signals from every other customer. A device fingerprint flagged at a crypto exchange shows up the next day at a telco. One company sees what shows up at its door. The network sees the actor.
The signal layer
Verification is built on six categories of signal. The engine reads all of them, every time.
Identity
Who they say they are.
Network
Where they're coming in from.
Behavior
What they do once they're in.
Domain hygiene
Whether the domain itself is real.
External intelligence.
What the rest of the internet says about them.
Cross-customer correlation
What they look like across every other door.
Where customers
point the engine first.
A few of the workflows the engine runs on day one.
Block fraudulent emergency data requests before a human reviewer ever sees them.
Re-verify every requester at the moment of submission, not just at sign-up.
Catch compromised credentials in your inbound channel before someone uses them.
Block fraudulent emergency data requests before a human reviewer ever sees them.
Re-verify every requester at the moment of submission, not just at sign-up.
Catch compromised credentials in your inbound channel before someone uses them.
Verification on demand.
Some companies want the engine; others want the engine and team. Verification On Demand from Kodex Threat Intelligence verifies requesters for you. Some use it to support a small team; others to replace one.
The work is done by the network's creators.


The network is the product







































































































Don't trust. Verify. And never stop verifying.
Twenty minutes is enough to see what gets caught in your channel today. We'll show you what the network sees that you don't.



Questions teams ask before they deploy.
Identity proofing to NIST IAL2, authentication to NIST AAL2, threat intelligence against the law enforcement request channel, and cross-customer signal correlation across the network. Most requesters clear automatically. The high-risk ones go to the Kodex Threat Intelligence team.
They don't reach your team. The request is blocked at the gate and logged for your audit trail. Your reviewers only see requests from verified agents.
Yes. Verification can run as a gate on your Kodex portal, as a one-tap Sign in with Kodex button on your own legal center, or as a Verification API call from your existing systems. The engine is the same in all three.
A domain check tells you the email looks legitimate. An agency lookup tells you the agency is real. Neither tells you the person sending the request is who they claim to be, or that their credentials haven't been compromised since the last time you checked. Kodex verifies the requester, not just the envelope.
Verification runs in the same window the request takes to submit. Legitimate requests clear in seconds. The fraudulent ones pay the cost of being slow.
No. Most customers run on the engine alone. If you want the team that built the engine to handle the highest-risk reviews on your behalf, that's Verification On Demand.
Verification is the layer in front of whatever you already have. You don't have to replace your intake, your case management, or your review process to add it.






