Sekit CSF · Identity & Access Management · Technical
RCF-0063Identity lifecycle
Account lifecycle is technically enforced — access is removed automatically when someone leaves
Mapping at a glance
RCF-0063Identity lifecycleIdentity & Access Management · Technical
RCF-0063 maps to 6 controls across the published frameworks. +1 more in the table below. Open in the full graph →
Maps to ISO/IEC 27001:2022
Curated mapping with the reasoning, not just the codes.
A.5.16Identity managementsupportsWiring systems so a central identity platform disable action revokes access everywhere removes the manual steps that are the usual reason A.5.16's lifecycle promises fail in practice.A.5.18Access rightssupportsAutomatic revocation everywhere once a person is disabled centrally closes the gap between deciding to remove access rights and them being removed.
Maps to NIST CSF 2.0
Curated mapping with the reasoning, not just the codes.
PR.AA-01Identities and credentials managedPR.AA-02Identities proofed and boundPR.AA-05Access permissions managed
Maps to Cyber Essentials
Curated mapping with the reasoning, not just the codes.
Evidence that proves this control
What an auditor, or Sekit's evidence engine, asks for.
Joiner-mover-leaver procedure
The process the company follows when someone joins, changes role, or leaves: how access and devices are granted and removed.
From the Sekit evidence catalog
This topic through the other lenses
All Identity & Access Management controls
Ask Sekura: “What evidence proves RCF-0063?”
Also via MCP, free with account