CyberArk Dual Control establishes an approval-based security mechanism for accessing privileged credentials. When the Master Policy rule requiring dual-control password access approval is enabled, users must obtain authorization from an appropriate Safe member before accessing protected credentials.
Exceptions to this approval requirement can be implemented through the underlying authorization model.
At the Safe level, the Access Safe without Confirmation permission allows designated users or groups to access protected accounts without obtaining the normal dual-control approval. This capability should be restricted to explicitly authorized identities, such as designated emergency-access administrators.
Where Object Level Access Control (OLAC) is enabled, permissions can be managed more granularly for individual objects. This permits account-specific authorization arrangements rather than applying identical permissions throughout the Safe.
Option D is incorrect because Master Policy exceptions primarily control policy applicability for platforms; they are not the same mechanism as granting individual users or groups approval-bypass permissions.
Option C concerns PSM connectivity, which is separate from the Safe authorization mechanism. Vault-level permissions do not provide the specific per-account Dual Control exception described.
[Reference:CyberArk PAM Self-Hosted — Master Policy, Dual Control, Safe Member Authorizations, Access Safe without Confirmation and Object Level Access Control.]
Submit