Harbor Access / 01 / PRACTICE GUIDE
Identity lifecycle: join, move and leave
Move from account tickets to verified access outcomes. Track ownership and lifecycle separately for employees, suppliers and application identities.
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.
Ticket exists: is the source authoritative? / Incomplete decision
Inspect an incomplete decision based on record existence or another positive signal. Consider denial cases alongside permitted use.
s => s.requestExists === trueA ticket alone verifies neither identity, effective date nor access ownership. Without an authoritative record and named owner, provisioning is not tied to a traceable business decision.
Choices and outputs last only on this open page; they do not update account progress, career status, points or certificates.
01 / EXPLANATION
Identity source and account distinction
Ada joins fictional Harbor. An HR record identifies the person and effective date; an application account represents access in one system. One person may hold multiple accounts, while an application identity may represent no person at all. Map stable identity, authoritative source, manager/sponsor and access owner. Treating email as immutable person identity risks mismatches after renaming or reuse. Every name here is synthetic. NIST SP 800-63-4 became final in July 2025; identity assurance and the organization’s business authorization still require separate assessments.
02 / EXPLANATION
Provision access for an actual need
Instead of copying a colleague’s entire access, specify the job task, resource, action and duration. Even default role-catalog entitlements need resource-owner review. Record the sponsor’s request, approver authority and actual target-application outcome. Closing a ticket does not establish correct provisioning scope. Review appropriate enrollment and recovery arrangements before first use. Harbor creates no real accounts; learners locate gaps between requests, authoritative records, approval and target verification. A neat request form is useful evidence but is not proof that the application enforced the intended permissions.
03 / EXPLANATION
Access accumulation after a move
When Ada moves from procurement to audit, adding the new role while leaving the old one creates access accumulation. Review prior entitlements, group memberships, temporary privileges and separation-of-duties conflicts together. If a brief overlap is needed, document its rationale, expiry and risk owner. A manager change does not automatically supply application-owner approval. Distinguish future effective dates from actual execution times. Verify target outcomes and failed-operation queues; a successful synchronization indicator cannot establish that every downstream application applied the intended change.
04 / EXPLANATION
Leaving involves more than blocking a directory account
Departure review covers directory access, application sessions, local accounts, vendor access and person-dependent automations. Transfer record and data ownership through authorized processes; keeping access because colleagues share its password is not a solution. Document provider-specific token and session behavior. Exit evidence distinguishes requested time, operation applied at the target and authorized verification results. This exercise blocks no real person, makes no HR decision and ends no application session. It teaches why lifecycle closure must demonstrate an outcome rather than merely a completed central-directory ticket.
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.