What this policy is
Defines the joiner/mover/leaver process from a security and access perspective — what's provisioned when, who approves it, and what's revoked at each transition.
Why every organization needs one
Most insider-risk findings trace back to a leaver who kept access or a mover whose old role's permissions were never revoked. The policy is the rule book.
What a competent Onboarding And Offboarding Policy typically contains
- Purpose and scope
- Roles and responsibilities
- Definitions
- Pre-day-1 provisioning checklist
- Role-change re-certification trigger
- Last-day revocation checklist
- Equipment recovery
- Review cadence (typically annual) and version control
- Approval, sign-off and effective date
How iCompaas tracks this policy
The icompaas policy-doc producer manages this document through an 8-state lifecycle: draft → generated → internal_qa → customer_review → in_review → approved → signed (with rejected as a terminal side-state). The producer publishes a policy_doc_onboarding_and_offboarding_policy_signed compliance finding once at least one document of this kind reaches the signed state for the account being assessed; the finding then rolls up into every compliance framework that references this policy (see the table below).
Compliance frameworks that reference this policy
The icompaas compliance controls library links every policy document to the controls in each framework that require, evidence, or otherwise rely on it. Below: every control across every framework in the iCompaas catalogue that names this policy as part of its evidence base. Each control links to its own dedicated page with auditor-view content + implementation guidance.
| Framework | Control | Title | Component |
|---|---|---|---|
| ISO/IEC 27001:2022 | A.5.11 | Return of assets | Organizational controls |
| ISO/IEC 27001:2022 | A.5.16 | Identity management | Organizational controls |
| ISO/IEC 27001:2022 | A.6.5 | Responsibilities after termination or change of employment | People controls |
3 controls across 1 framework reference this policy.
About this page
This article is part of the iCompaas Policy Documents library — one page per signed-document type the icompaas policy-doc producer tracks for customer accounts. The article is intentionally framework-agnostic: a customer signing a policy of this kind gets the same regulatory benefit across every framework that references it.