Skip to content

Research resources

Every feature starts from a spec and an attack, not from someone’s opinion. This page collects the sources. The roadmap lists which ones apply to each phase.

Keep these open throughout.

  • API Security in Action, Neil Madden
  • OAuth 2 in Action, Justin Richer and Antonio Sanso
  • Real-World Cryptography, David Wong
  • Threat Modeling: Designing for Security, Adam Shostack
Area Specs
Password hashing RFC 9106 (Argon2)
Cookies RFC 6265bis (draft)
OAuth 2.0 RFC 6749, RFC 9700 (security BCP), RFC 7636 (PKCE), RFC 8252 (native apps), RFC 8628 (device flow)
OpenID Connect OIDC Core 1.0, OIDC Discovery
One-time passwords RFC 6238 (TOTP), RFC 4226 (HOTP)
Passkeys WebAuthn Level 3, passkeys.dev
Tokens RFC 7519 (JWT), RFC 8725 (JWT BCP), RFC 9068 (JWT access tokens), RFC 9449 (DPoP)
Provider mode RFC 7662 (introspection), RFC 7009 (revocation)
Enterprise SAML 2.0, RFC 7643 and RFC 7644 (SCIM)
Disclosure RFC 9116 (security.txt)

Drafts such as OAuth 2.1 and RFC 6265bis change over time. Check for newer revisions before implementing.

  • Sudhodanan and Paverd, “Pre-hijacked accounts: An Empirical Study of Security Failures in User Account Creation on the Web”, USENIX Security 2022.
  • Pang et al., “Zanzibar: Google’s Consistent, Global Authorization System”, USENIX ATC 2019.
  • Better Auth: a TypeScript auth library. Study its plugin model and access control.
  • Kanidm: a Rust identity server with a strong security posture.
  • webauthn-rs: a WebAuthn implementation in Rust.
  • Cedar: a formally verified policy language written in Rust.
  • SpiceDB and OpenFGA: open-source implementations of Zanzibar.