Authentication and current presence
Authentication establishes that required evidence was successfully presented. It does not by itself establish who remains present at the next action.
Passwords, multifactor authentication, passkeys, certificates, biometrics, hardware tokens, and device-bound credentials can strengthen the decision to grant access. Existence does not replace those credentials, and possession of an EAID alone does not authorize access. The research asks what current condition remains necessary after the organization’s access requirements succeed.
The authentication decision
Authentication evaluates evidence under a policy.
A system receives one or more proofs, evaluates them, and decides whether the claimant has satisfied the required authentication policy. Stronger methods can reduce reliance on reusable secrets and make impersonation more difficult.
That decision is essential. The existence question does not challenge it. It begins when the authenticated relationship is allowed to continue into later protected actions.
The time distinction
Authentication occurred. The next action is occurring now.
A successful login is an event. A session is a continuation. The protected actions inside that session may occur seconds, minutes, or hours later.
The evidence that justified access may remain valid while the human condition has changed. Present participation therefore cannot be assumed merely because authentication previously succeeded.
Multifactor authentication
More authentication factors establish stronger authentication, not a different fact.
Knowledge, possession, inherence, device binding, and cryptographic proof can be combined to make unauthorized authentication more difficult. Each factor contributes evidence to the authentication decision.
Existence is not proposed as another copy of those factors. It is a maintained operational condition: the governed participant relationship is currently active and independently recognized at the decision point.
Credential remains required
The identification establishes existence; the organization’s credential establishes access.
The EAID is a governed identification and runtime origin. It is not the password, passkey, certificate, PIN, biometric decision, or other credential by which the organization permits entry into its application.
This separation prevents a found identification from becoming sufficient access. The organization page must still apply its own credential, identity, role, and authorization requirements.
Not continuous authentication
Recurring existence renewal does not repeat the credential decision.
Authentication determines whether the organization’s required evidence has been satisfied. Existence is established through a different dependency chain and does not repeatedly authenticate the participant.
After private arrival, existence maintains itself through recurring heartbeat. The network observes the current binary result without turning that observation into another credential check.
Runtime authority
Authority is issued for the present relationship rather than inherited indefinitely.
The activated identification presents itself to the Authority Server, completes a current challenge, receives volatile runtime session authority, registers with the Existence Beacon, and reaches the first successful heartbeat. The Rendering Agent is then released and the organization’s page loads. That private arrival completes existence establishment.
The organization’s page still requires its own credential and authorization before access is permitted. From arrival forward, existence maintains itself through recurring heartbeat, and the network observes the current result for the active relationship.
At the protected function
Credentials and authorization answer whether access is permitted. Existence supplies the separately observed condition after private arrival.
verify_existence(...)The protected action requests the current presence determination in addition to the organization’s authentication, authorization, and transaction policy.
Limits
A present authenticated participant may still be unauthorized for the requested action.
Existence does not replace identity proofing, phishing-resistant authentication, credential protection, session management, authorization, device integrity, fraud controls, or approval workflows.
It prevents one necessary fact from being inferred from another: successful authentication is not permanent proof of current existence, and a present EAID is not permission to enter without the organization’s credential.
Related research paths
Authentication begins authority. Other disciplines govern where it may continue.
Examine the governed identity, role, privilege, and lifecycle behind the authentication event.
Zero TrustExamine repeated decisions after initial authentication succeeds.
Network securityExamine the difference between continuing connectivity and continuing participation.
All research topicsReturn to the complete cybersecurity research library.
Examine the distinction