---
schema_version: "1"
id: d349f7a20f757f47b4812e7e0fdca8b2ed0f7e52b89a9c524620932364c347aa
title: Follow the Principle of Least Privilege
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/cc/264-0-0/b2c_follow_the_principle_of_least_privilege.md
canonical_url: https://help.salesforce.com/s/articleView?id=cc.b2c_follow_the_principle_of_least_privilege.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 23e8d13a8458b4d3a83d113baaefe8409091ecb288720b68a8d5f7a6c3b0798a
description: The principle of least privilege is a core zero trust concept. Implementing least privilege means that you give users, applications, B2C Commerce systems, and other components only the minimum privilege level required to do their job.
products:
  - Commerce
  - B2C Commerce
release: "264"
---
# Follow the Principle of Least Privilege

The principle of least privilege is a core zero trust concept. Implementing least privilege means that you give users, applications, B2C Commerce systems, and other components only the minimum privilege level required to do their job.

Design granularity into the application to allow for separation of responsibilities within an organization. For example, a user account for the sole purpose of checking analytics doesn’t need permission to manage the product catalog. So, the user account only has rights to view analytics reports. Other privileges, such as managing the catalog, are blocked.

Effectively managed role-based access control (RBAC) makes these implementations possible. RBAC lets you create roles based on a set of permissions. Managing users’ permissions is now as simple as assigning them to their corresponding roles.

Least privilege provides the following benefits.

- Users can’t accidentally perform high-privilege actions without explicit permission.
- Malicious insiders can’t leverage over-privileged accounts to further their attacks.
- Attackers can’t take advantage of poor permissions to make their attacks easier.

For example, all Business Manager users and Open Commerce API (OCAPI) clients are set up with deny-by-default permissions. It's the administrator's responsibility to provide the permissions that allow each user to do their job.

The administrator must also ensure that all users, roles, and permissions are updated and relevant. Regular audits on the accounts can help the process.