How the concept is used
During login, the user presents evidence that the service verifies. A successful result can establish a session, avoiding the need to repeat the check on every click. Security depends on more than the initial method: session protection and replacement of lost authenticators matter too. Strong login combined with a poorly protected recovery route addresses only part of the problem.
A practical example
For example, an employee signs into an online shop’s administration using a passkey. The system checks control of the registered key. A separate decision then determines whether the account may edit products, read orders or change payout details. A particularly sensitive change may justify another authentication step before it is completed. These are related controls, but they serve different purposes.
Important distinctions
Authentication does not verify every statement about the person behind an account. An account created under an invented name can still have a functioning login mechanism. Authentication is also different from authorisation: being able to sign in does not grant permission to perform every action. When selecting a method, describe both the user who needs to be recognised and the operations that need protection. Establishing an age threshold requires appropriate evidence for that separate question.
Sources
These explanations were prepared with AI assistance and draw on the sources listed.