A school administrator disputes access to a B2B learning product after a password reset. Its authentication audit log must preserve evidence for a SOC2 review: which sessions were created, verified, and revoked, even after the identity service's current state has changed. A successful reset response cannot supply that history.
Short answer: record every session create, verify, and revoke in your own searchable audit log, with the user ID and session ID. For a Node.js password-recovery flow, select the session-security policy first, then retain the evidence for the full dispute window. Treat this as an authentication audit design for a SOC2 review; no API choice alone establishes compliance.
Keep less deliberately. The constraint is completeness of the necessary evidence, not completeness of every request payload.
What authentication audit log requirements should recovery satisfy for SOC2?
The useful question is whether a reviewer can reconstruct the access decision.…