Sekit CSF · Identity & Access Management · Policy
RCF-0067Least privilege / RBAC
Users only have access to what their role requires
Mapping at a glance
RCF-0067Least privilege / RBACIdentity & Access Management · Policy
RCF-0067 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.15Access controlsupportsSekit's Least privilege / RBAC control defines the access each role needs and makes that the default grant, the policy half of A.5.15's set-and-enforce requirement; the platform-level enforcement that completes it is mapped separately on this page.A.5.18Access rightssupportsDefining the access each role needs and granting from that definition rather than copying a colleague supports A.5.18's provisioning step, though the review and revocation legs the control also requires sit with other Sekit controls.A.8.3Information access restrictionsupportsThis Sekit policy commits each role's access needs to a written definition and makes it the default grant, laying the groundwork for the access restriction A.8.3 requires without itself restricting anything until enforced elsewhere.
Maps to NIST CSF 2.0
Curated mapping with the reasoning, not just the codes.
Maps to Cyber Essentials
Curated mapping with the reasoning, not just the codes.
This topic through the other lenses
All Identity & Access Management controls
Ask Sekura: “What evidence proves RCF-0067?”
Also via MCP, free with account