Join our Newsletter — 33% off our NHI Course
Home› FAQ› Authentication, Authorisation & Trust› What is the difference between something you know,…
Authentication, Authorisation & Trust

What is the difference between something you know, something you have, and something you are in authentication?

← Back to all FAQ
By NHI Mgmt Group Editorial Team Updated October 31, 2026 Domain: Authentication, Authorisation & Trust

Something you know is a knowledge factor such as a password or PIN. Something you have is an ownership factor such as a phone, security key, or hardware-backed credential. Something you are is an inherence factor such as a fingerprint or face scan. Stronger authentication often combines factors, but each option introduces its own usability and operational trade-offs.

How the three authentication factors differ in practice

The difference is the kind of evidence the authenticator asks for. Knowledge factors rely on recall, ownership factors rely on possession of a device or credential, and inherence factors rely on a physical or behavioural trait. The practical distinction matters because each factor fails in a different way, and each can be stronger or weaker depending on how it is implemented.

Knowledge factors are the most familiar, but they are also the easiest to share, guess, phish, or reuse. Ownership factors can be stronger because an attacker must usually steal or duplicate a device or secret, but they can still be exposed through session theft, SIM swapping, push fatigue, or compromised backup channels. Inherence factors are convenient, but they raise privacy, spoofing, and fallback concerns if they are treated as a standalone guarantee of identity.

Common practice is to combine factors so one compromise does not automatically break sign-in. In that model, the factor types matter less than the total assurance they create, especially when the login protects administrative access, remote access, or sensitive data.

What each factor actually proves

A password or PIN proves that the user knows a shared secret. A phone, security key, or hardware-backed credential proves that the user has access to a physical or cryptographic authenticator. A fingerprint or face scan proves that a biometric reader matched an enrolled characteristic to the presenter, within the limits of the sensor, template, and liveness checks.

That is why these factors are not interchangeable. A password can be reset, a device can be lost, and a biometric cannot be changed in the same way a secret can. For that reason, organisations should treat the factor itself and the recovery path as part of the authentication design, not just the sign-in screen.

The same factor type can also be implemented very differently. A code sent by SMS is still something you have in a loose sense, but it is weaker than a phishing-resistant security key or passkey because the delivery channel and recovery path introduce extra attack surface. Current guidance increasingly favours phishing-resistant methods for higher-risk accounts, which is why a modern NIST SP 800-63 Digital Identity Guidelines approach is more useful than a simple factor checklist.

For practitioners, the important question is not only which factor is used, but whether the factor survives the most likely abuse path for that account. MFA Guide is a useful reference when you need to compare how those abuse paths differ across passwords, push prompts, one-time codes, security keys, and passkeys.

Why factor choice changes risk, usability, and recovery

Different factor types create different trade-offs. Knowledge factors are easy to deploy but hard to defend at scale if users must remember many secrets. Ownership factors improve resistance to credential theft, but they add dependency on devices, telecoms, token provisioning, and account recovery. Inherence factors can reduce friction, yet they often need a fallback factor anyway, and that fallback can become the weakest link.

Recovery is where many authentication designs fail operationally. If a forgotten password, lost phone, or failed biometric fallback can be handled by weak help desk procedures, the stronger factor provides less protection than it appears to. That is why a sign-in design should be judged together with reset, re-enrolment, and exception handling.

The difference also matters for risk acceptance. For low-sensitivity services, a simple knowledge factor may be tolerable if paired with rate limiting and monitoring. For privileged or high-value access, the question becomes whether the authentication method is resistant to phishing, replay, and social engineering, not merely whether it counts as a second factor.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

NIST SP 800-63, NIST SP 800-53 Rev 5, OWASP ASVS and CIS Controls v8 set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
NIST SP 800-63Digital Identity GuidelinesCovers authenticator assurance, phishing resistance, and recovery choices for factor-based sign-in.
Recommendation — Use phishing-resistant authenticators and align recovery with the assurance level you need.
NIST SP 800-53 Rev 5IA-5 — Authenticator ManagementDirectly applies to passwords, tokens, keys, and lifecycle handling of authenticators.
Recommendation — Manage authenticator issuance, rotation, revocation, and reset as controlled lifecycle events.
OWASP ASVSV6 — AuthenticationCovers authentication factor handling, strength, and verification requirements in applications.
V7 — Session ManagementSession theft and reuse materially affect what a factor proves after sign-in.
Recommendation — Verify authentication methods against strength, recovery, and abuse-resistance requirements. Bind sessions securely and invalidate them promptly when assurance is lost.
CIS Controls v8CIS-5 — Account ManagementAccount lifecycle and recovery paths determine whether factor controls hold up operationally.
Recommendation — Restrict account recovery and admin access with strong, auditable account controls.

Practitioner Guidance

What to verify: Check whether the factor actually binds to the intended user or session, or whether it can be relayed, reused, or reset through a weaker channel. A method that is easy to bypass during recovery should not be treated as materially stronger than the password it protects.

Decision rule: If the account can reach sensitive systems, prefer phishing-resistant ownership factors over codes delivered through shared channels, and treat biometrics as an unlock mechanism or convenience layer rather than the only control unless the full recovery path is equally strong.

What practitioners underestimate: The recovery flow often determines the real security level. If attackers can defeat password reset, device replacement, or help desk verification, the nominal factor mix will not prevent account compromise.

Practitioner takeaway: Strong authentication is about the whole assurance chain, not just the named factor, so the best design is the one whose sign-in, recovery, and fallback paths are all equally hard to abuse.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on October 31, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org