Study guide

6.2 Dual Control Workflows, Multi-Level Approvals & Master Approver

CyberArk Defender - PAM PAM-DEF

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Vault Architecture, Network & Security

1.1 CyberArk PAS Core Architecture & Component Topology 1.2 Vault OS Hardening, Network Isolation & Port Requirements 1.3 Vault Cryptography, Encryption Keys & Master User Recovery

2 Chapter 2: Vault Configuration, Administration & CLI Utilities

2.1 Vault Server Configuration Files & DBParm.ini Tuning 2.2 Vault Administrative Utilities & PARClient Commands 2.3 Event Notification Engine (ENE) & Notification Administration

3 Chapter 3: Password Vault Web Access (PVWA) Administration

3.1 PVWA Web Portal Architecture & Interface Configuration 3.2 PVWA REST API Administration & Lifecycle Automation 3.3 PVWA Security Settings, User Access & Session Timeouts

4 Chapter 4: Central Policy Manager (CPM) Architecture & Operations

4.1 CPM Service Architecture, Logs & Multi-CPM Load Distribution 4.2 The Credential Management State Machine: Change, Verify & Reconcile 4.3 CPM Plug-in Architecture, Process/Prompts Files & Custom Plug-in Troubleshooting 4.4 Loosely Connected Devices: Rotating Laptop & Workstation Credentials

5 Chapter 5: Safe Design, RBAC & Account Governance

5.1 Enterprise Safe Architecture & Naming Conventions 5.2 Safe Permissions, Authorizations & Safe Handler Delegation 5.3 Object Versioning, Retention Policies & Storage Quotas 5.4 Mandatory Account Properties, Account Types & Linked Accounts 5.5 Vault Users, Predefined Groups & Vault-Level Authorizations

6 Chapter 6: Account Discovery & Lifecycle Workflows

6.1 Automated Account Discovery, Detection Rules & Pending Accounts 6.2 Dual Control Workflows, Multi-Level Approvals & Master Approver 6.3 Exclusive Access, One-Time Passwords (OTP) & Check-out Automation 6.4 Bulk Onboarding: Password Upload Utility, Bulk Upload REST API & AccountUploader

7 Chapter 7: Master Policy & Platform Management

7.1 Master Policy Framework & Enterprise Compliance Rules 7.2 Platform Architecture, Settings Tree & Platform Duplication 7.3 Platform Policy Overrides, Advanced Settings & Target Tuning

8 Chapter 8: Privileged Session Manager (PSM) Core Architecture

8.1 PSM Architecture, Jump Host Isolation & Service Accounts 8.2 PSM Connection Components (PSM-RDP, PSM-SSH, PSM-Web) 8.3 PSM Universal Connector Framework & Custom Integrations 8.4 Split Workflow: Separating Session Use from Credential Retrieval

9 Chapter 9: PSMP, HTML5 Gateway & Session Security

9.1 PSM for SSH (PSMP) Architecture & Unix Proxy Brokering 9.2 PSM HTML5 Gateway Architecture & Clientless Web Access 9.3 Session Recording, Storage in Recordings Safes & Vault Retention 9.4 CyberArk Remote Access (Vendor PAM): Administering Third-Party Privileged Access

10 Chapter 10: Live Session Auditing, Reporting & Privileged Threat Analytics

10.1 Live Session Monitoring, Shadowing & Active Termination 10.2 Privileged Threat Analytics (PTA) Behavioral Anomaly Detection 10.3 PTA Automated Incident Response & SIEM Integration (CEF/Syslog) 10.4 Vault Reports, Report Authorizations & the Export Vault Data (EVD) Utility

11 Chapter 11: Application Access Manager (AAM) & Secrets Management

11.1 AAM Credential Provider (CP) Architecture & Local Memory Cache 11.2 Central Credential Provider (CCP) & Web Service Integration 11.3 Application Server Credential Provider (ASCP) & Application Authentication (AppID) 11.4 Conjur Secrets Manager & Cloud-Native DevOps Workflows

12 Chapter 12: Directory Integration, Disaster Recovery & Troubleshooting

12.1 Directory Integration: LDAP Mapping, RADIUS MFA & SAML 2.0 SSO 12.2 Disaster Recovery (DR) Vault & PADR Replication Architecture 12.3 Vault Backup Operations with PAReplicate & Safe Recovery 12.4 Diagnostic Procedures, Vault/CPM/PSM Error Codes & System Recovery

6.2 Dual Control Workflows, Multi-Level Approvals & Master Approver

Key Takeaways Explain This Topic AI

Dual Control enforces the Four-Eyes principle, requiring independent approver authorization before users can view, copy, or connect with privileged credentials.

While Master Policy mandates Dual Control enforcement, Safe Access Control Lists define authorized approvers via the 'Authorize account requests' permission.

PVWA access requests mandate justification metadata including business reason, external ticketing system ID (e.g., ServiceNow/Jira), and bounded start/end timeframes.

Multi-level approval workflows enforce sequential sign-offs where Level 1 approvers (managers) must confirm before Level 2 approvers (security) can authorize access.

Designated Master Approvers and emergency break-glass identities possessing 'Access Safe without authorization' provide authorized overrides during critical operational outages.

Last updated: September 2026

6.2 Dual Control Workflows, Multi-Level Approvals & Master Approver

Quick Answer: Dual Control (the Four-Eyes principle) is a CyberArk authorization framework enforcing multi-person integrity by preventing users from viewing, copying, or connecting with privileged credentials without authorization from designated approvers. Configured at Master Policy or platform levels and enforced at Safe level, Dual Control requires submitting access tickets in PVWA specifying a business reason, ticketing ID, and time window. Notifications are routed via the Event Notification Engine (ENE) across single-level or multi-level approval hierarchies. For emergency break-glass situations, designated Master Approvers or users with Access Safe without authorization override standard approval rules.

The Dual Control Governance Framework

Granting unconstrained access to high-privilege credentials—such as domain administrators, database root users, and break-glass identities—introduces severe insider threat and operational risks. Dual Control (the "Four-Eyes Principle" or two-person integrity) resolves this vulnerability by ensuring that no single individual can unilaterally retrieve or use a sensitive credential. At least two authorized individuals—a requester and an independent approver—must participate in every access grant.

Dual Control operates across two architectural levels:

Master Policy Level: Mandated under the Master Policy rule "Require dual control password access approval" , toggled globally or configured with specific platform exceptions.

Safe Level: The Safe Access Control List (ACL) defines authorized approvers and requesters. Approvers must possess specific Safe rights over the target accounts.

When Dual Control is active, viewing, copying, or launching PSM sessions is intercepted until formal authorization completes.

PVWA Access Request Submission Workflow

When accessing an account governed by Dual Control, PVWA intercepts the operation and presents the Request Access modal interface. Requesters must provide mandatory parameters bounding access:

Reason / Business Justification: Mandatory text explaining the operational necessity for access (e.g., "Applying quarterly security patches to production SQL cluster").

Ticketing System ID: Ticket number from enterprise ITSM platforms (ServiceNow, BMC Remedy, Jira). When ticketing integration is active, the Vault queries ITSM APIs to verify the ticket is open, approved, and assigned to the requester.

Access Timeframe (Time Window): Explicit Start Date/Time and End Date/Time bounding access. Credentials cannot be accessed before the start time, and access automatically terminates once the end time expires.

Request Type: Single Access (one connection or check-out event) or Multiple Access (unlimited sessions within the approved window).

Notification Routing via Event Notification Engine (ENE)

Submitted requests trigger the Event Notification Engine (ENE) service ( CyberArk Event Notification Engine ) running on the Vault:

Event Detection: ENE detects internal CreateRequest transaction logs in the Vault database.

Approver Resolution: ENE inspects the target Safe's ACLs to identify all users and groups possessing the Authorize account requests permission.

Email Dispatch: Over TCP port 25 (SMTP), ENE transmits email alerts containing requester identity, target account, Safe name, justification, ticket ID, timeframe, and a direct deep-link to the PVWA Request Review console.

Safe Permissions & Approver Entitlements

Dual Control relies on granular Safe permissions to strictly separate requesters from approvers:

Authorize account requests : Designates an Approver , entitling identities to view pending requests, inspect tickets, and confirm or reject submissions.

Access Safe without authorization : Allows designated emergency accounts to bypass Dual Control entirely, granting instant access without submitting requests.

Manage Safe : Grants Safe administration rights, but does not grant approval authority unless Authorize account requests is also assigned.

Standard requesters only require operational permissions on the Safe ( Use account , Retrieve accounts , List accounts ).

Single-Level vs. Multi-Level Approvals

CyberArk supports two approval hierarchies to accommodate diverse governance requirements:

Single-Level Approvals

In a single-level configuration, one or more approver groups are assigned Authorize account requests on the Safe. Any single member can confirm the request. Upon confirmation, status transitions to Authorized , allowing immediate access within the approved window.

Multi-Level Approvals (Tiered Governance)

For high-risk environments (Tier-0 domain controllers, core financial databases), enterprises enforce Multi-Level Approvals :

Sequential Sign-Off: Requires sequential authorization across two tiers: Level 1 Approvers (operational managers or asset owners) followed by Level 2 Approvers (Information Security or SOC).

Enforcement Mechanics: Level 1 approvers are notified first. The request remains pending until Level 1 confirms, after which Level 2 is notified.

Final Authorization: Only after Level 2 confirms does the request become Authorized .

Rejection Finality: If an approver at either level rejects the request, the workflow terminates immediately with a Rejected status and access is denied.

Emergency Access, Master Approver Override & Break-Glass Protocols

During Sev-1 outages when standard approvers are unreachable, CyberArk provides emergency override mechanisms:

Master Approver Role: Senior security authorities (CISO, PAM Architecture Lead, or Vault Administrator) assigned Master Approver rights can authorize pending requests across any Safe, bypassing multi-level tiers while preserving full audit logging.

Break-Glass Accounts: Dedicated emergency identities pre-assigned Access Safe without authorization on emergency Safes. Accessing credentials via break-glass identities bypasses approval gates while triggering immediate high-severity Syslog alerts (ports 514/6514) to SIEM and PTA.

Dual Control Approval Workflows & Governance Models Comparison

The following table outlines the operational differences between CyberArk authorization mechanisms:

Approval Model Required Authorizations Notification Flow Primary Use Case Risk Profile

Single-Level Approval Any single member with Authorize account requests ENE notifies Safe approver group Standard production servers, routine administration Low friction; single approver dependency

Multi-Level Approval Sequential sign-off from Level 1 AND Level 2 approvers ENE notifies Level 1, then notifies Level 2 Tier-0 Domain Controllers, core financial databases Strict governance; potential operational latency

Master Approver Override Single sign-off by designated Master Approver Bypasses standard approver tier; logs override Approver unavailability during critical outages Controlled exception; preserves full audit trail

Emergency Bypass ( Access Safe w/o Auth ) None; access granted instantly Immediate SIEM/PTA alert dispatched upon retrieval Catastrophic infrastructure outages, disaster recovery High risk; requires mandatory post-incident audit

Loading diagram... Multi-Level Dual Control Approval & Session Brokering Flow