# Digital Personal Data Protection Act SE-002 — Role-Based Access Control (RBAC) & Least Privilege

- Source: https://support.icompaas.com/support/solutions/articles/a_gen_dpdp_se002_6758aac952-digital-personal-data-protection-act-se-002-role-based-access-control-rbac-least-privilege
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [DPDP Act (India)](https://support.icompaas.com/support/solutions/c_gen_dpdpa) › [Security](https://support.icompaas.com/support/solutions/folders/f_gen_cgendpdpa_security)
- Last updated: 2026-05-30
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

Digital Personal Data Protection Act · Control SE-002 · Priority: high · Component: Security

### What this control covers

Implement role-based access control (RBAC) for all systems containing personal data, enforcing least-privilege access. Conduct quarterly access reviews. Disable credentials unused for 90 days. Enforce MFA for all users with access to personal data systems. Objective: Prevent unauthorised access to personal data by limiting access to only those with a legitimate business need, in accordance with Rule 6(1).

### Why it matters

Identity is the new perimeter — most breaches start with a stolen credential or over-privileged account, so this control is one of the single highest-leverage items you can implement.

### How to implement

#### AWS

Use **IAM Identity Center** (formerly AWS SSO) as the single source of truth for human access; back it with your corporate IdP via SAML/SCIM. Avoid IAM users for people — they don't get MFA-by-default, rotation, or session lifetimes. For workloads, use **IAM Roles** (assumed by EC2/Lambda/EKS service accounts via IRSA) and never long-lived access keys. Run [IAM Access Analyzer](https://docs.aws.amazon.com/IAM/latest/UserGuide/access-analyzer.html) weekly to surface unused access and external-account exposure.

#### Azure

Centralize identity on **Microsoft Entra ID** (formerly Azure AD). Require **Conditional Access** policies: MFA for all admin roles, block legacy auth, location/device gating. Use **Privileged Identity Management (PIM)** to make admin roles just-in-time and time-bound. For Azure resources, prefer **Managed Identities** over service principals with secrets.

#### 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.

### 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.

Signed policies, procedures, and registers document the safeguard. IAM analytics confirm RBAC, MFA, and access reviews. Focus: Role-Based Access Control (RBAC) & Least Privilege.

### Quick checklist

-   Implement — Role / Based Access Control (Rbac)
-   Conduct — Role / Based Access Control (Rbac)
-   Review — Role / Based Access Control (Rbac)

### Related articles on this site

-   [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)
-   [Ensure Role-Based Access Control (RBAC) for Azure Key Vault is Enabled (Automated)](https://support.icompaas.com/support/solutions/articles/62000234052-ensure-role-based-access-control-rbac-for-azure-key-vault-is-enabled-automated-)
-   [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)

## Related compliance guidance

- [India's DPDP Act 2023: a practical compliance guide for cloud teams](https://support.icompaas.com/compliance/india-dpdp-act-2023): The DPDP Act and 2025 Rules explained as an implementation plan, including what is in force today.
- [GDPR compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/gdpr): A GDPR programme covers most DPDP obligations; the guide shows the overlap and the India-specific gaps.