JWT validation checklist for API servers, based on RFC 8725
A checklist for what an API must verify on every JWT: algorithm, signature, issuer, audience, expiry and type. Based on RFC 8725 and OWASP guidance.
Deep dives, practical guides, and incident analyses from engineers who build Safeguard. No fluff, no vendor FUD — just what you need to ship secure software.
A checklist for what an API must verify on every JWT: algorithm, signature, issuer, audience, expiry and type. Based on RFC 8725 and OWASP guidance.
Five common beliefs about JWTs in APIs, checked against RFC 8725 and OWASP guidance: the none algorithm, header trust, expiry, revocation and secrets.
Header fields in a JWT are attacker controlled. RFC 8725 says to sanitize kid and allowlist jku and x5u. A practical validation order for your verifier.
A correct signature only proves who signed a token. RFC 8725 also says to check issuer, subject, audience and token type to stop cross-service misuse.
A researcher blog can be excellent or overstated. Check for reproduction, scoped claims, vendor response and fix status before deciding it matters to you.
A short checklist for vetting a phone app that touches your code or alerts: permissions, network use, sign-in, data storage and updates, per Android docs.
Jeopardy CTFs suit most internal training; attack-defense suits mature teams with time to spare. Here is how the two formats differ and how to choose.
Prototype pollution lets attackers change shared object behavior. Practical defenses: Map, Object.create(null), freezing prototypes and --disable-proto.
Reduce Java native deserialization risk with serialization filters and class allowlists, which libraries are safe by default, and why filters are no cure.
Weekly insights on software supply chain security, delivered to your inbox.
Your first fix PR is minutes away.
No sales call required, even your agent can complete the purchase over MCP.