Appearance
NIST Controls
This page lists SBS controls tagged for this regulation or framework. The mappings are indicative only and help readers identify controls that directly support demonstrating compliance.
These entries are an index into the benchmark. The canonical control content remains on the benchmark pages.
- Total tagged controls: 28
- Benchmark sections represented: 8
Controls By Benchmark Section
Access Controls
12 control(s) in this benchmark section.
SBS-ACS-001: Enforce a Documented Permission Set Model
High Source pageControl Statement: All permission sets, permission set groups, and profiles must conform to a documented model maintained in a system of record and enforced continuously.
Why tagged: Requires a defined, auditable access structure for account management, access enforcement, and least privilege.
SBS-ACS-002: Documented Justification for All API-Enabled Authorizations
High Source pageControl Statement: Every authorization granting the API Enabled permission must have documented business or technical justification recorded in a system of record.
Why tagged: Requires least privilege and documented justification for elevated or programmatic access.
SBS-ACS-003: Documented Justification for Approve Uninstalled Connected Apps Permission
Critical Source pageControl Statement: The Approve Uninstalled Connected Apps permission must only be assigned to highly trusted users with documented justification and must not be granted to end-users.
Why tagged: Access enforcement requires controlling which applications can be authorized to access system data.
SBS-ACS-004: Documented Justification for All Super Admin–Equivalent Users
High Source pageControl Statement: All users with simultaneous View All Data, Modify All Data, and Manage Users permissions must be documented in a system of record with clear business or technical justification.
Why tagged: Privileged access must be documented, justified, and limited to authorized individuals.
SBS-ACS-005: Only Use Custom Profiles for Active Users
High Source pageControl Statement: All active users must be assigned custom profiles. The out-of-the-box standard profiles must not be used.
Why tagged: Access enforcement and least privilege require the organization to define and maintain access boundaries.
SBS-ACS-006: Documented Justification for Use Any API Client Permission
Critical Source pageControl Statement: The Use Any API Client permission, which bypasses default behavior in orgs with "API Access Control" enabled, must only be assigned to highly trusted users with documented justification and must not be granted to end-users.
Why tagged: Access enforcement requires controlling which API clients can be used to access system data.
SBS-ACS-007: Maintain Inventory of Non-Human Identities
High Source pageControl Statement: Organizations must maintain an authoritative inventory of all non-human identities, including integration users, automation users, bot users, and API-only accounts.
Why tagged: Account management requires an inventory of all accounts, including non-human and system accounts.
SBS-ACS-008: Restrict Broad Privileges for Non-Human Identities
High Source pageControl Statement: Non-human identities must not be assigned permissions that bypass sharing rules or grant administrative capabilities unless documented business justification exists.
Why tagged: Least privilege applies to all accounts, including non-human; broad privileges require justification.
SBS-ACS-009: Implement Compensating Controls for Privileged Non-Human Identities
Moderate Source pageControl Statement: Non-human identities with permissions that bypass sharing rules or grant administrative capabilities must have compensating controls implemented to mitigate risk.
Why tagged: Defense-in-depth for privileged accounts is an expected control family requirement.
SBS-ACS-010: Enforce Periodic Access Review and Recertification
Moderate Source pageControl Statement: All user access and configuration influencing permissions and sharing must be formally reviewed and recertified at least annually by designated busines stakeholders, with documented approval and remediation of unauthorized or excessive access.
Why tagged: Access reviews and recertification are required for account and access management.
SBS-ACS-011: Enforce Governance of Access and Authorization Changes
High Source pageControl Statement: All changes to Salesforce user access and authorization must be governed through a documented process that requires approval, records business justification, and produces an auditable record of the change.
Why tagged: Access enforcement requires approval and audit trail for access grants and changes.
SBS-ACS-012: Classify Users for Login Hours Restrictions
Moderate Source pageControl Statement: Organizations must maintain a documented classification of users requiring login hours restrictions or equivalent off-hours authentication monitoring.
Why tagged: Session and access control requirements include time-based or monitored access where appropriate.
Authentication
4 control(s) in this benchmark section.
SBS-AUTH-001: Enable Organization-Wide SSO Enforcement Setting
Critical Source pageControl Statement: Salesforce production orgs must enable the org-level setting that disables Salesforce credential logins for all users.
Why tagged: Access control and authentication management; SSO enforcement is a direct technical control.
SBS-AUTH-002: Govern and Document All Users Permitted to Bypass Single Sign-On
Moderate Source pageControl Statement: All users who do not have the "Is Single Sign-On Enabled" permission must be explicitly authorized, documented in a system of record, and limited to approved administrative or break-glass use cases.
Why tagged: Account management and access control require documented justification for exceptions.
SBS-AUTH-003: Prohibit Broad or Unrestricted Profile Login IP Ranges
Moderate Source pageControl Statement: Profiles in Salesforce production orgs must not contain login IP ranges that effectively permit access from the full public internet or other overly broad ranges that bypass network-based access controls.
Why tagged: Access control includes network-based restrictions and boundary enforcement.
SBS-AUTH-004: Enforce Strong Multi-Factor Authentication for External Users with Substantial Access to Sensitive Data
Critical Source pageControl Statement: All Salesforce interactive authentication flows for external human users with substantial access to sensitive data must enforce multi-factor authentication that includes at least one strong authentication factor.
Why tagged: Authentication and access control; MFA for high-risk users is a named NIST expectation.
Customer Portals
3 control(s) in this benchmark section.
SBS-CPORTAL-001: Prevent Insecure Direct Object Reference (IDOR) in Portal Apex
Critical Source pageControl Statement: All Apex methods exposed to Experience Cloud or customer portal users must enforce server-side authorization for every record accessed or modified. User-supplied parameters (including record IDs, filters, field names, or relationship references) must not be trusted as the basis for access control and must be validated against the running user's sharing, CRUD, and FLS permissions before use.
Why tagged: Access control and enforcement; authorization must be validated server-side for every access.
SBS-CPORTAL-002: Restrict Guest User Record Access
Critical Source pageControl Statement: Unauthenticated guest users in customer portals must be restricted to authentication and registration flows only, with no direct access to business objects or custom Apex methods that query organizational data.
Why tagged: Access control requires restricting unauthenticated access to organizational data.
SBS-CPORTAL-004: Prevent Parameter-Based Record Access in Portal-Exposed Flows
Critical Source pageControl Statement: Autolaunched Flows exposed to customer portal users must not accept user-supplied input variables that directly determine which records are accessed.
Why tagged: Access control; user-supplied parameters must not bypass authorization in flows.
Deployments
3 control(s) in this benchmark section.
SBS-DEP-001: Require a Designated Deployment Identity for Metadata Changes
High Source pageControl Statement: Salesforce production orgs must designate a single deployment identity that is exclusively used for all metadata deployments and high-risk configuration changes performed through automated or scripted release processes.
Why tagged: Account management and attributable administrative activity require production deployments to use a defined identity.
SBS-DEP-002: Establish and Maintain a List of High-Risk Metadata Types Prohibited from Direct Production Editing
High Source pageControl Statement: Salesforce production orgs must maintain an explicit list of high-risk metadata types that must never be edited directly in production by human users, defaulting at minimum to the SBS baseline list while allowing organizations to extend or refine it as needed.
Why tagged: Access enforcement and least privilege require defined boundaries around who may directly modify high-risk production metadata.
SBS-DEP-006: Configure Salesforce CLI Connected App with Token Expiration Policies
High Source pageControl Statement: Organizations must configure the Connected App used for Salesforce CLI authentication with refresh token expiration of 90 days or less and access token timeout of 15 minutes or less.
Why tagged: Authenticator lifecycle and session management require expiration controls for persistent OAuth tokens used for administrative access.
Event Monitoring
2 control(s) in this benchmark section.
SBS-MON-003: Monitor for Suspicious Logins
High Source pageControl Statement: Organizations must continuously monitor and alert on anomalous login patterns to promptly detect and mitigate compromised accounts and application credentials.
Why tagged: Monitoring login anomalies is a direct access-auditing control used to detect compromised accounts.
SBS-MON-004: Monitor for Suspicious API Activity
High Source pageControl Statement: Organizations must continuously monitor and alert on all API activity to establish a baseline, detect anomalous and malicious activity, and identify potential application and integration abuse in a timely manner.
Why tagged: Audit of access and account activity includes monitoring API use for anomalous or unauthorized behavior.
File Security
1 control(s) in this benchmark section.
SBS-FILE-002: Require Passwords on Public Content Links for Sensitive Content
High Source pageControl Statement: Organizations must ensure that Public Content links to sensitive content have a password.
Why tagged: Access control requires restricting anonymous access to sensitive content distributed through public links.
Integrations
1 control(s) in this benchmark section.
SBS-INT-004: Retain API Total Usage Event Logs for 30 Days
High Source pageControl Statement: The organization must retain API Total Usage event log data (EventLogFile EventType=ApiTotalUsage) for at least the immediately preceding 30 days using Salesforce-native retention or automated external export and storage.
Description:
If the organization’s Salesforce does not provide at least 30 days of ApiTotalUsage EventLogFile availability in Salesforce, the organization must automatically export newly available ApiTotalUsage event log files at least once every 24 hours to an external log store that retains a minimum of 30 days of data.
Why tagged: Audit of access includes retaining API usage logs so investigators can attribute and reconstruct activity.
OAuth Security
2 control(s) in this benchmark section.
SBS-OAUTH-001: Require Formal Installation of Connected Apps
Critical Source pageControl Statement: Organizations must formally install all connected apps used for OAuth authentication rather than relying on user-authorized OAuth connections.
Why tagged: Access control and account management require administrators to govern which OAuth applications can establish access.
SBS-OAUTH-002: Require Profile or Permission Set Access Control for Connected Apps
Critical Source pageControl Statement: Organizations must control access to each formally installed connected app exclusively through assigned profiles or permission sets.
Why tagged: Least privilege and access enforcement require connected apps to be limited to explicitly authorized users.