They only prove that a secret was entered, not that the actor is still trustworthy after authentication. AI-generated impersonation can trick humans into revealing secrets or approving access, while session hijacking bypasses re-entry altogether. That makes static credentials a poor trust signal for modern cloud communication.
Why passwords and OTPs stop being reliable trust signals
Passwords and OTPs are still useful for proving that a user knew a secret at one point in time, but that is a much weaker claim than “the current actor is trustworthy.” Modern impersonation attacks exploit the human layer, while stolen or replayed sessions bypass the challenge entirely. The practical failure is not only authentication weakness, but trust decay after login.
Passwords are vulnerable to phishing, vishing, help-desk abuse, credential stuffing, and AI-generated pretexting that makes fake requests sound legitimate. OTPs raise the bar against password reuse, but they remain shareable, relayable, and often easy to capture in real time. Once an attacker can induce disclosure or intercept the code, the second factor no longer proves the actor’s legitimacy.
For identity teams, the deeper issue is that static secrets are point-in-time signals. They do not continuously bind the session to the original device, channel, or user intent. That is why modern guidance increasingly favours phishing-resistant methods and session controls that reduce the value of a stolen secret after authentication.
How AI-driven impersonation changes the attack path
AI-driven impersonation scales social engineering by making voice, chat, and email lures more convincing, more contextual, and faster to iterate. A fabricated executive call, a fake support conversation, or a believable internal message can pressure a user to reveal a password, approve a push, read out an OTP, or complete an account recovery step that feels routine.
That human manipulation matters because the attacker does not need to defeat cryptography if they can defeat judgement. The control failure is often in the recovery and exception path, where urgency, authority cues, and out-of-band communication are used to override normal caution. This is why impersonation is often paired with help-desk social engineering, MFA fatigue, or consent abuse rather than brute-force attacks.
In the cloud and SaaS context, impersonation also targets delegated trust. A compromised user can be turned into a stepping stone to broader access if the environment treats authentication as a one-time gate instead of a continuously assessed risk condition. Deepfakes, Social Engineering and AI Impersonation Guide is useful here because it shows why out-of-band verification and identity-based checks matter more than conversational plausibility.
Why session hijacking defeats re-entering credentials
session hijacking attacks a different layer. Once a browser session, bearer token, or cookie is stolen or replayed, the attacker inherits an already authenticated context and does not need the password or OTP again. That is why re-prompting for a secret is often too late if the active session itself has already been captured.
Common failure modes include token theft from malware, reverse proxies that proxy the user’s login in real time, cookie replay from exposed browser state, and edge-device flaws that leak session material from memory. In those cases, the original login may have been legitimate, but the session becomes the object being abused. The protection problem shifts from “who signed in?” to “can the current session still be trusted?”
That is also why token lifetime, revocation, sender-constraining, and step-up controls matter. A strong password or OTP can coexist with a weak session model, and then the stronger login factor still fails to protect the account. Token and Session Security Guide is the clearest internal reference for the controls that make stolen sessions harder to replay.
Risk and Threat Considerations
When passwords and OTPs are treated as the main trust boundary, attackers can aim for the easier target: the person, the recovery workflow, or the live session. The result is not just account compromise, but impersonation inside trusted business channels, unauthorized approvals, and lateral movement through SaaS or cloud services.
Failure mechanism: AI-generated pretexting increases the success rate of secret capture, while session theft or replay bypasses the need to authenticate again. The control fails when authentication is mistaken for ongoing trust.
Impact: Organisations can lose control of mailboxes, identity providers, admin consoles, and downstream applications even when the original password policy looks strong. The blast radius grows when the stolen session has high privilege or long lifetime.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
OWASP Non-Human Identity Top 10 and MITRE ATT&CK address the attack and risk surface, while NIST SP 800-53 Rev 5, NIST SP 800-63 and NIST Zero Trust (SP 800-207) set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | IA-5 — Authenticator Management | Passwords and OTPs are authenticators whose lifecycle and strength drive this failure mode. |
| IA-2 — Identification and Authentication (Organizational Users) | The question is about login trust and why initial authentication is insufficient. | |
| IA-9 — Identification and Authentication (Non-Organizational Users) | Session hijacking and impersonation affect services, apps, and externally mediated access too. | |
| Recommendation — Harden authenticator lifecycle, rotation, and recovery to reduce secret-based compromise. Require stronger user authentication and step-up for sensitive actions. Apply stronger authentication patterns for non-human and external access paths. | ||
| NIST SP 800-63 | Digital Identity Guidelines | The subject hinges on phishing-resistant authentication and authenticator assurance. |
| Recommendation — Adopt phishing-resistant authenticators and bind assurance to the transaction risk. | ||
| NIST Zero Trust (SP 800-207) | Zero Trust Architecture | The answer depends on not trusting a one-time login as ongoing trust. |
| Recommendation — Continuously evaluate session trust and verify access requests at runtime. | ||
| OWASP Non-Human Identity Top 10 | NHI-02 — Secret Leakage | Passwords, OTPs, and session material fail when secrets are captured or replayed. |
| NHI-04 — Insecure Authentication | Static secrets and OTPs are the core authentication weakness discussed here. | |
| NHI-07 — Long-Lived Secrets | Long-lived passwords and sessions increase the value of stolen credentials. | |
| Recommendation — Reduce secret exposure and monitor for leaked credentials and tokens. Replace easily phishable authentication with stronger, phishing-resistant methods. Shorten secret and session lifetimes to shrink replay windows. | ||
| MITRE ATT&CK | Credential Access | The threat path involves phishing, impersonation, and session theft for access. |
| Recommendation — Map impersonation and session theft tactics to detect credential access activity. | ||
Practitioner Guidance
What to prioritise: Treat passwords and OTPs as baseline controls, not final proof of trust. If the account can reach sensitive systems, add phishing-resistant authentication, session binding, and high-risk action revalidation before relying on any login event.
What to verify: Confirm that your highest-value workflows, especially password reset, MFA reset, admin elevation, and help-desk recovery, cannot be completed with only a secret and a convincing story. If they can, the organisation is still vulnerable to impersonation.
Common mistake: Teams often over-invest in stronger OTP delivery while leaving session duration, token theft detection, and recovery procedures weak. That improves the front door but leaves the attacker with a usable back door.
Practitioner takeaway: The real security question is not whether a secret was entered, it is whether the current actor and session are still trustworthy enough to keep acting.
Related resources from NHI Mgmt Group
Deepen Your Knowledge
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.
Reviewed and updated by the NHIMG editorial team on October 11, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org