Harbor Access / 02 / PRACTICE GUIDE
MFA, recovery and session security
Look beyond an MFA-enabled label. Separate evidence for enrollment, identity recovery, phishing resistance and token/session termination.
Download guide and workpapersOriginal AI-assisted SecNet educational content; examples are fictional. Not a source organization publication or endorsement. Sources checked: 2026-10-21.
EVIDENCE REVIEW DESK
Move from observations to decisions.
Code here is a local policy model with no target connection. Passing model cases are not security approval or device tests.
MFA indicator / Incomplete decision
Inspect an incomplete decision based on record existence or another positive signal. Consider denial cases alongside permitted use.
s => s.mfaEnabled === trueAn MFA indicator establishes neither method suitability nor protected recovery. Review enrollment, method and recovery together before drawing an assurance conclusion.
Choices and outputs last only on this open page; they do not update account progress, career status, points or certificates.
01 / EXPLANATION
Second factors offer different assurance
MFA requires appropriate use of independent factors; two passwords are not two different factors. OTP and simple approval prompts do not offer the same properties as phishing-resistant cryptographic methods. Assess method selection against user and task risk, enrollment and recovery together. NIST SP 800-63B-4 supplies method and assurance context; this package certifies no AAL. Method labels in Harbor are evidence assumptions, not tests of actual devices or identity providers. Learners explain why a checked MFA box alone cannot demonstrate the intended level of protection.
02 / EXPLANATION
Enrollment and method changes
Strong sign-in does not suffice if an attacker can enroll their own authenticator. Initial enrollment, adding a device and removing an old method require appropriate identity checks and audit trails. Define what support staff may do and what evidence they need. Review compromise and social-engineering risks of recovery channels separately. Harbor records the request, verifying role and independent approval. It includes no real phone, biometric data or recovery codes and performs no actual authenticator binding. The evidence question concerns the process around the method, not just its product name.
03 / EXPLANATION
Password changes do not imply session termination
Passwords, refresh tokens, access tokens and application-owned cookies may have different lifecycles. Success of one operation does not demonstrate immediate loss of every access path. Record supported revocation behavior, timing and verification for each provider and application. Harbor asks for evidence concerning refresh capability and application sessions alongside a password change. It promises no universal instant session termination. During an actual incident, authorized teams assess user effects, recovery and verified target-application outcomes together instead of treating a central identity event as sufficient proof.
04 / EXPLANATION
Make recovery usable and accountable
Recovery should not permanently lock out legitimate users; evaluate emergency access and accessibility needs. Removing identity evidence for speed, however, defeats the control. Define approval ownership, audit records, appropriate user notification and misuse review. Do not store actual secrets or authentication codes as clear text in tickets. Harbor workpapers separate known facts, missing evidence and the person responsible for validating the outcome. A robust recovery process considers trusted end-to-end account use rather than merely increasing the number of available sign-in methods.
Build the evidence yourself.
Blank workpapers are not completed tests. Fill them in your authorized environment without secrets or real personal data.
Full guide with code, outputs and reasoning ↓Primary references
Explanations are authored by SecNet. References support method and platform context; verify current editions and organizational policy for real use.