Authentication
The process of establishing sufficient confidence that an actor controls one or more authenticators bound to a claimed digital identity.
Download Markdown (.md)Soroush’s Product Wiki · https://wiki.soroush.uk/topic/authentication/
01What it means
Authentication, often abbreviated authn, verifies a claim about who or what is acting by testing control of an authenticator such as a password, cryptographic key, or device. It produces an identity assertion with some assurance; it does not decide which actions that identity may perform.[1][2]
- 01EnrollmentBind identity and authenticator
- 02ClaimPresent identity
- 03ProofDemonstrate control
- 04VerifyCheck proof and risk
- 05Session or assertionBounded assurance and lifetime
Authentication establishes an identity claim with some assurance; it does not decide what that identity may do.
02Why it matters
Authentication protects accounts, data, and high-impact actions from impersonation. Its strength, recovery paths, usability, and session handling directly shape fraud risk, user access, support burden, and trust.
03When to use it
Authenticate when a service must associate an interaction with a returning person, workload, or device. Avoid demanding identity where anonymous or pseudonymous access is sufficient, and require stronger or repeated proof when risk increases.
04How it works
- Register an identity and bind one or more authenticators through a trusted enrollment process.
- Ask the claimant to prove control of an authenticator using a secure protocol.
- Verify the proof, rate-limit failures, and assess relevant risk signals without treating them as factors.
- Create an authenticated session or assertion with an appropriate assurance level and lifetime.
- Support secure recovery, authenticator replacement, revocation, monitoring, and reauthentication.
05A practical example
A payroll service verifies an employee with a password and phishing-resistant security key, then creates a bounded session. Viewing a payslip uses that session, while changing bank details requires fresh authentication.
06Where it breaks
Authentication cannot prove legal identity unless a separate identity-proofing process supports that claim, and it does not grant permission. Phishing, stolen sessions, weak recovery, malware, and compromised verifiers can bypass otherwise strong login controls.
Common mistakes
- Using authentication and authorization as synonyms.
- Treating possession of an email address as strong identity proof.
- Protecting login while leaving recovery and session lifecycle weaker.
- Requiring friction uniformly instead of matching assurance to risk.
07Sources
- Digital Identity Guidelines: Authentication and Authenticator ManagementNIST · Government standardDigital Identity Guidelines: Authentication and Authenticator Management
- Authentication Cheat SheetOWASP Foundation · Security practice guidanceAuthentication Cheat Sheet