Study guide
5.4 Mandatory Account Properties, Account Types & Linked Accounts
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
5.4 Mandatory Account Properties, Account Types & Linked Accounts
Key Takeaways Explain This Topic AI
Every managed account in CyberArk strictly requires three core mandatory properties: Address (target network endpoint/FQDN), UserName (target account identity), and Platform ID (governing management platform).
Target accounts span four primary operational types—Local, Domain, Database, and Cloud/IAM accounts—each defining unique address resolutions and CPM plugin interactions.
A Logon Account is a linked non-privileged account used to establish an initial SSH or RDP connection before elevating or switching context (via su or sudo) to the target privileged account.
An Enable Account is a linked credential that supplies the secondary enable secret required to transition network devices (e.g., Cisco IOS) into privileged configuration mode.
A Reconciliation Account is an elevated linked administrative identity that enables CPM to force-reset an out-of-sync credential on a target endpoint without knowing the current invalid password.
Last updated: September 2026
5.4 Mandatory Account Properties, Account Types & Linked Accounts
Quick Answer: Every managed account in CyberArk requires three mandatory properties: Address (the network hostname, IP, or domain of the target), UserName (the account name on the target endpoint), and Platform ID (the governing policy defining rotation rules and plugin mechanics). Beyond standard account classifications (Local, Domain, Database, Cloud), CyberArk uses a Linked Accounts architecture to resolve complex operational constraints. This architecture includes Logon Accounts (for navigating SSH/RDP environments that prohibit direct privileged login), Enable Accounts (for network appliances requiring secondary privilege elevation), and Reconciliation Accounts (for resetting out-of-sync credentials without knowing the existing password).
Mandatory Account Properties: The Triad of Managed Accounts
When onboarding an account into CyberArk—whether through the PVWA web portal, Discovery rules, REST API payloads, or PACLI scripts—the Digital Vault enforces three mandatory attributes. Together, these form the fundamental identity triad of any managed credential:
1. Address
Definition: The network address used by the Central Policy Manager (CPM) and Privileged Session Manager (PSM) to locate and establish communication with the target system.
Permitted Formats: IPv4 address ( 192.168.10.50 ), Fully Qualified Domain Name ( app01.corp.internal ), or NetBIOS name ( APP01 ).
Domain vs. Local Scoping: For local accounts, Address points directly to the target server hosting the local SAM database or /etc/passwd . For Active Directory domain accounts, Address points to the Active Directory domain FQDN (e.g., corp.internal ) or a specific domain controller.
2. UserName
Definition: The literal account logon name configured on the target operating system, database, or directory (e.g., Administrator , root , oracle , svc_backup ).
3. Platform ID
Definition: The unique string identifier linking the account to its governing target platform (e.g., WinServerLocal , UnixSSH , OracleDB , AWSConsole ).
Functional Role: The Platform ID dictates all policy parameters: password complexity rules, rotation frequency, CPM plugin execution binaries ( .dll or .exe ), process/prompts script references, PSM connection components, and Dual Control settings.
Optional & Custom Properties (File Categories)
Safes store additional optional properties defined by the platform or created as custom categories:
Port : Overrides default connection ports (e.g., targeting SSH on port 2222 or MS SQL on port 14333).
Database / ServiceName : Specifies the database instance or Oracle SID/Service Name.
Business Metadata: Custom attributes such as Department , AssetOwner , EnvironmentTier , or ChangeTicket used for search indexing and reporting.
Target Account Classifications
Understanding target account classifications is essential for selecting appropriate platforms and scoping CPM communication paths:
Account Type Primary Storage Location Address Property Resolution CPM Management Protocol
Local Account Local SAM / /etc/shadow on target host Target server IP or FQDN SMB/RPC (TCP 445/135) or SSH (TCP 22)
Domain Account Active Directory / LDAP directory Domain FQDN (e.g., corp.com ) NetAPI / Kerberos / LDAP to Domain Controller
Database Account Database data dictionary (e.g., Oracle DBA_USERS ) Database listener IP/FQDN Native database client / SQL Net (1521, 1433)
Cloud / IAM Cloud Identity Provider (AWS, Azure, GCP) Cloud endpoint or tenant ID REST APIs over HTTPS (TCP 443)
Linked Accounts Architecture
In enterprise environments, security policies, network barriers, and target OS constraints often prevent CyberArk from directly authenticating with the target account. CyberArk overcomes these challenges by establishing relationships between credential objects using Linked Accounts .
A Linked Account is an auxiliary account object (stored in the same Safe or an isolated administrative Safe) associated with a target account at the platform or account level.
1. The Logon Account
Operational Problem: Enterprise OS hardening commonly disables direct remote administrative logins over SSH or RDP (e.g., PermitRootLogin no in /etc/ssh/sshd_config , or disabling direct RDP as Administrator ).
Architectural Solution: A non-privileged personal account or dedicated machine user is designated as the Logon Account and linked to the target privileged account ( root ).
Workflow:
When PSM initiates an SSH session or CPM triggers a password rotation, it first connects to the target machine using the Logon Account credentials.
Once the unprivileged shell session is established, CyberArk's terminal automation script issues an elevation command ( su - or sudo su - ).
When prompted for the target credential, CyberArk injects the password of the target privileged account, seamlessly transitioning the session into the elevated administrative context.
2. The Enable Account
Operational Problem: Enterprise network appliances (Cisco routers, switches, firewalls) enforce two distinct authentication tiers: a user-level login credential to access the unprivileged CLI terminal, followed by an enable secret required to enter privileged EXEC mode ( Router# ).
Architectural Solution: The Enable Account stores the secondary enable secret and is linked to the network device account.
Workflow: When CPM rotates the device credential or PSM brokers an administrative session, CyberArk logs in using the primary target credentials, issues the enable command, and injects the password stored inside the linked Enable Account when prompted.
3. The Reconciliation Account
Operational Problem: If a target account password is changed out-of-band (e.g., an administrator manually resets it locally during a disaster recovery outage), the Vault credential falls out of sync. When CPM performs its scheduled verification ( Verify ), authentication fails. A standard CPM Change command also fails because standard changes require authenticating with the existing password before issuing the replacement.
Architectural Solution: A Reconciliation Account is linked to the target account. This account possesses elevated rights on the target system (e.g., Domain Admin in Active Directory, or an account with sudo passwd rights on Linux) permitting it to override and reset passwords for other accounts.
Workflow:
CPM detects that the target account is out of sync ( LastCPMStatus: Verification Failed ).
CPM authenticates directly to the target system using the Reconciliation Account .
Operating under the administrative authority of the Reconciliation Account, CPM issues a force-reset command (e.g., passwd <username> on Linux or Set-ADAccountPassword on Windows), applying a newly generated random password to the target account.
CPM writes the new password to the Vault object, releasing the operational lock and restoring synchronization without human intervention.
Comparison of Linked Account Types
Linked Account Type Primary Use Case Target Environment Required Privileges on Target
Logon Account Bypass PermitRootLogin no ; provide initial SSH/RDP session Linux / Unix / Windows Servers Minimal / Unprivileged user (with sudo or su rights)
Enable Account Secondary password to enter privileged EXEC mode Network Appliances (Cisco, Juniper, Fortinet) Possesses the appliance's enable secret
Reconciliation Account Force-reset out-of-sync credentials without existing password Windows, Linux, Databases, Directories Elevated administrative rights to reset target user passwords