# Authentication

The process of establishing sufficient confidence that an actor controls one or more authenticators bound to a claimed digital identity.

- Type: term
- Domain: Engineering & architecture
- Level: Foundational
- Last reviewed: 2026-09-23
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/authentication/>)

## What 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.

## Why 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.

## When 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.

## How it works

1. Register an identity and bind one or more authenticators through a trusted enrollment process.
2. Ask the claimant to prove control of an authenticator using a secure protocol.
3. Verify the proof, rate-limit failures, and assess relevant risk signals without treating them as factors.
4. Create an authenticated session or assertion with an appropriate assurance level and lifetime.
5. Support secure recovery, authenticator replacement, revocation, monitoring, and reauthentication.

## A 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.

## Where 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.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/authentication/#visualization-authentication>)

## Sources

1. [Digital Identity Guidelines: Authentication and Authenticator Management](<https://pages.nist.gov/800-63-4/sp800-63b.html>) — NIST · Government standard
2. [Authentication Cheat Sheet](<https://cheatsheetseries.owasp.org/cheatsheets/Authentication_Cheat_Sheet.html>) — OWASP Foundation · Security practice guidance

## Related topics

- [Authorization](<https://wiki.soroush.uk/topic/authorization/>)
- [Multi-Factor Authentication \(MFA\)](<https://wiki.soroush.uk/topic/multi-factor-authentication/>)
- [Session](<https://wiki.soroush.uk/topic/session/>)
