# BSI C5 IDM-01 — Policy for user accounts and access rights

- Source: https://support.icompaas.com/support/solutions/articles/a_gen_bsic5_idm01_e9e12e1d4d-bsi-c5-idm-01-policy-for-user-accounts-and-access-rights
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [BSI C5 (German Cloud)](https://support.icompaas.com/support/solutions/c_gen_bsi_c5) › [Identity & Access Management](https://support.icompaas.com/support/solutions/folders/f_gen_cgenbsic5_identityaccessmanagement)
- Last updated: 2026-05-30
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

BSI C5 · Control IDM-01 · Priority: high · Component: Identity & Access Management

### What this control covers

Documents role-based access policies per SP-01, enforcing least privilege, segregation of duties, and two-factor authentication for privileged access. Specifies account management, regular reviews, and automated blocking to protect cloud customer data from unauthorized access.

### Why it matters

Risk is the language an executive team understands; this control connects technical reality to board-level decisions and budget allocation.

### How to implement

#### AWS

Codify the policy intent as **SCPs, AWS Config conformance packs, and Security Hub standards** so the cloud enforces what the document says.

#### Azure

Codify in **Azure Policy initiatives** (built-in regulatory compliance for CIS, ISO 27001, SOC 2, HIPAA) and assign at management-group level.

#### GCP

Use **Cloud Identity** (or Workspace) as the IdP and **IAM** for resource access. Grant roles at the lowest scope (project > folder > org) using **Workload Identity Federation** for CI/CD and **service accounts** for workloads — never download service-account keys when avoidable. Enable **Policy Intelligence** recommenders to right-size privileges and detect dormant identities.

#### Google Workspace

Enforce **2-Step Verification** (preferably hardware keys for admins) for the entire org, set session length to ≤ 12 hours, and disable less-secure-app access. Use **Context-Aware Access** levels to restrict admin sign-in by IP/device posture. Provision and de-provision users via **SCIM** from your HRIS so leavers lose access on day one.

#### GitHub

Require **SSO + SCIM** from your IdP on the organisation; enforce **2FA** org-wide and use **fine-grained PATs** (or, better, GitHub Apps) instead of classic tokens. Restrict **outside collaborators**, require signed commits on protected branches, and use **OIDC** from Actions to short-lived AWS/GCP/Azure credentials rather than stored secrets.

#### Zoho Mail

Make **two-factor authentication** mandatory for all users (TOTP, OneAuth, or YubiKey) in _Admin Console → Security_. Configure **SAML SSO** against your IdP and disable password-based logins for admins. Use **role-based privileges** (Admin / Spam Moderator / Mail Account Admin) and review the _Login history_ report monthly for anomalies.

#### On-premises

Maintain a policy library with a documented review cadence (annual minimum); store in your GRC tool with attestation tracking. Map each policy to controls so an audit pull cites the exact policy clause.

### Evidence to collect

-   `identity_scan` — See the iCompaas Evidence library for the canonical source for this evidence type.
-   `policy_document` — A signed, version-controlled policy stating leadership intent and the named owner.

Identity analytics (Okta, SailPoint, Access Analyzer) demonstrates least-privilege. Signed policy or standard documents the safeguard. Focus: Policy for user accounts and access rights.

### Quick checklist

-   Segregation — Access Rights / Cloud Customer Data
-   Risk — Access Rights / Cloud Customer Data
-   Review — Access Rights / Cloud Customer Data
-   Data — Access Rights / Cloud Customer Data
-   Policy — Access Rights / Cloud Customer Data
-   Access — Access Rights / Cloud Customer Data

### Related articles on this site

-   [Ensure periodic IAM user access reviews are performed to ensure users have least privilege access](https://support.icompaas.com/support/solutions/articles/62000229691-ensure-periodic-iam-user-access-reviews-are-performed-to-ensure-users-have-least-privilege-access)
-   [Ensure Access Review is Set Up for External Users in Azure AD Privileged Identity Management (PIM](https://support.icompaas.com/support/solutions/articles/62000229788-ensure-access-review-is-set-up-for-external-users-in-azure-ad-privileged-identity-management-pim)
-   [Implement and Periodically Review Access Policies for Azure Cache for Redis to Enforce RBAC and Least Privilege](https://support.icompaas.com/support/solutions/articles/62000234774-implement-and-periodically-review-access-policies-for-azure-cache-for-redis-to-enforce-rbac-and-least)
-   [NIST 800-171 3.1.5 Employ the principle of least privilege, including for specific security functions and privileged accounts.](https://support.icompaas.com/support/solutions/articles/62000229227-nist-800-171-3-1-5-employ-the-principle-of-least-privilege-including-for-specific-security-functions)

## Related compliance guidance

- [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Configuration checks like this one are the technical half of a SOC 2 / ISO 27001 programme — the guide shows where they fit, what else an auditor expects, and how to evidence them.
- [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): ISO 27001 Annex A.8 (technological controls) is where cloud hardening evidence lands; the guide shows how to run the ISMS around it.