JSON Web Token
Also called JWT.
A signed, self-contained token carrying claims between parties.
What it is
A compact, URL-safe token format consisting of a header, a claims payload, and a signature, used to convey identity and authorization data that a recipient can verify without a server-side session lookup.
Why it matters
JWTs are everywhere in modern auth, and their pitfalls (accepting unsigned tokens, weak signing keys, or skipping verification) lead to authentication bypass, so inspecting their claims and validation is common in app reviews.
In practice
A token whose signature is never verified, letting an attacker edit the payload to claim administrator rights.
What to look for
- alg set to none or switched from RS256 to HS256.
- Missing exp or very long lifetimes.
- Tokens stored where scripts can read them.
Common mistake
Trusting claims without verifying the signature and algorithm.
Use it in CyberKit
In the field
Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.
-
Microsoft Entra ID Protection Commercial
Scores sign-in and user risk in Microsoft Entra ID and can force MFA or a reset.
-
Okta Identity Threat Protection Commercial
Evaluates session risk continuously and can end sessions when it changes.
-
BloodHound Open source
Maps attack paths through Entra ID and Active Directory relationships.
Read next
- OAuth: A framework for delegating limited access without sharing a password.
- Broken Access Control: Failure to enforce what authenticated users are allowed to do.
- API Security: Protecting application programming interfaces from abuse and data exposure.