IDENTITY-AND-ACCESS-MANAGEMENT-ARCHITECT practice question 18 of 30

The security team at Universal Containers (UC) has identified exporting reports as a high-risk action and would like to require users to be logged…

Full set: 248 questions
The security team at Universal Containers (UC) has identified exporting reports as a high-risk action and would like to require users to be logged into Salesforce with their Active Directory (AD) credentials when doing so. For all other users of Salesforce, users should be allowed to use AD Credentials or Salesforce credentials. What solution should be recommended to prevent exporting reports except when logged in using AD credentials while maintaining the ability to view reports when logged in with Salesforce credentials?
Answer options
A: Use SAML Federated Authentication and block access to reports when accessed through a Standard Assurance session.
B: Use SAML Federated Authentication and Custom SAML JIT Provisioning to dynamically and or remove a permission set that grants the Export Reports Permission.
C: Use SAML federated Authentication, treat SAML Sessions as High Assurance, and raise the session level required for exporting reports. Correct answer
D: Use SAML federated Authentication with a Login Flow to dynamically add or remove a Permission Set that grants the Export Reports Permission.
Correct Answer:
C. Use SAML federated Authentication, treat SAML Sessions as High Assurance, and raise the session level required for exporting reports.
Explanation

This solution correctly uses Salesforce's built-in Session Security Level framework. By configuring the SAML Single Sign-On (SSO) with Active Directory to establish a 'High Assurance' session, and leaving the standard username/password login as 'Standard Assurance,' a distinction is created based on the authentication method. The 'Export Reports' permission, which is part of a Profile or Permission Set, can then be configured to require a High Assurance session. This enforces the security requirement precisely: users authenticated via AD (High Assurance) can export reports, while users logged in with Salesforce credentials (Standard Assurance) can view reports but are blocked from exporting them until they elevate their session.

Why Incorrect

A: This is incorrect because it would block all access to reports, including viewing, for Standard Assurance sessions. The requirement is only to block the export action. B: Just-In-Time (JIT) provisioning manages user record creation and updates at login. It is not designed for per-session permission management and would permanently assign the permission. D: A Login Flow modifies the user's record (e.g., assigning a permission set) at the point of login. The permission would persist for the user across different sessions, failing to meet the session-specific security requirement.

References

1. Salesforce Help, "Session Security Levels": This document outlines the concept of Standard and High Assurance session levels. It states, "By default, when a user logs in to Salesforce, they get a standard-assurance session... When a user logs in with a more secure verification method, such as MFA, they get a high-assurance session." SAML can be configured as such a method.

2. Salesforce Help, "Edit Session Policies in Profiles": This guide explains how to enforce session-level security. It specifies, "For each profile, you can set whether a high-assurance session is required for users to access reports and dashboards." This directly supports raising the session level for the reporting function. The same control is available on Permission Sets.

3. Salesforce Help, "Create a SAML Single Sign-On Setting": In the configuration steps for a SAML SSO provider, the documentation details the "Session Security Level" setting. An administrator can choose "Standard" or "High Assurance" for sessions initiated through that specific SSO configuration, which is the foundation of the solution in option C.

Scroll to Top