CyberArk Operations Guide (2026): System Health, Safe Management, Platform & Master Policy Explained
Learn CyberArk Operations in detail including System Health checks, Safe Management, Platform configuration, Reports, and Master Policy. Complete guide for PAM engineers.
π Introduction to CyberArk Operations
CyberArk CyberArk Operations is the day-to-day activity performed by L1, L2, and L3 engineers to ensure the PAM environment runs smoothly.
π It includes:
- Monitoring system health
- Managing safes and access
- Configuring platforms
- Generating reports
- Enforcing security policies etc...
π‘ Strong operations knowledge = strong real-time project performance
π― Why CyberArk Operations is Important
Without proper operations:
β Components may go down unnoticed
β Password rotation may fail
β Users may lose access
β Security risks increase
π With proper operations:
β System stability
β Secure access control
β Compliance & auditing
β Smooth password management
π§© 1. System Health (L1 Engineer Task)
π What is System Health?
Monitoring the status of all CyberArk components.
π What You Check Daily
β Components status (Connected / Disconnected)
β Vault, PVWA, CPM, PSM availability
β Installed versions
β Number of onboarded accounts
β Accounts managed by CPM
β Active user sessions in PVWA
β Number of PSM connections
β Internal users used by components
π― Why It Matters
π Early detection of issues prevents downtime
π 2. CyberArk Reports
π Key Reports in PVWA
1οΈβ£ Privileged Account Inventory
- Lists all accounts in CyberArk
- Includes:
- Account Name
- Address
- Last Accessed
- Last Modified
2οΈβ£ Privileged Account Compliance
β Compliant:
- CPM successfully rotates password
β Non-Compliant:
- CPM fails to rotate password
3οΈβ£ Application Inventory
- Applications onboarded for:
4οΈβ£ Entitlement Report
- The Entitlement Report in the Privileged Identity Management (PIM) suite provides a comprehensive overview of user access and permissions. It details each user’s effective access control, authorization level, and privileges for every account stored within the vault or specific safe. This report ensures complete visibility into which users have access to which accounts, making it a critical tool for access governance, compliance auditing, and security management in CyberArk environments.
5οΈβ£ Activity Logs
- Tracks user actions:
- Login
- Account changes
- Deletion and much more...
π New Reports (Version 14+)
β License Capacity
β User List
β Safe Owners
β Active vs Non-Active Safes
ποΈ 3. Safe Management
π What is a Safe?
π A Safe is a secure container used to store:
- Accounts
- Passwords
- Certificates
- Files
π‘ Without Safe → No storage possible
π§ Safe Creation Steps
- Login to PVWA
- Navigate to Policies → Safes
- Create Safe with:
- Safe Name (Max 28 characters)
- Description
- OLAC (Object Level Access Control)
- Password history settings
- Assign CPM
β οΈ Important Rule
π If CPM is NOT assigned:
β Password rotation will NOT work
π₯ Default Safe Members
When a Safe is created:
β Master
β DR Users
β Backup Users
β Operators
β Batch
β PasswordManager
β Notification Engine
β Auditors β PSMAppUsers
β Administrator is NOT added by default
π Safe Permissions
π€ End Users
β List Account
β Use Account
π¨πΌ Managers / Leads
β List
β Use
β Retrieve
β Authorize Request
π Important Permissions
- Retrieve → View password
- Use → Connect via PSM
- Add/Update/Delete → Manage accounts
- Move → Transfer account between safes
- Access Without Confirmation → Bypass approval
βοΈ 4. Platform Management
π What is a Platform?
π A Platform defines:
- Password policies
- CPM settings
- PSM connection settings
π§± Platform Types
- Windows
- Unix/Linux
- Database (Oracle, SQL, MySQL)
- Cloud (AWS, Azure, GCP) etc..
β οΈ Critical Rule
π Wrong Platform =
β CPM password rotation fails
β PSM session connection fails
π‘ Best Practice
β Always duplicate and customize platform
β Use correct platform per account type
π 5. Master Policy (Vault Settings)
π What is Master Policy?
π Global security rules applied across CyberArk
π Important Policies
1οΈβ£ Dual Control (Approval)
- User must request access
- Manager approves
β Supports:
- Single approval
- Multi-level approval
π Bypass Approval
Permission:
π Access Safe Without Confirmation
2οΈβ£ Check-in / Check-out
- Locks account to one user
- Prevents concurrent usage
3οΈβ£ One-Time Password (OTP)
- Password changes after every use
4οΈβ£ Specify Reason
- User must provide reason before access
- Used for auditing
5οΈβ£ Click-to-Connect
- Enable/Disable PSM connection & View Password
π CPM Policies (Password Management)
β Password Change: Default 90 days
β Password Verify: Default 7 days
π CPM ensures:
- Password rotation
- Password validation
π₯οΈ PSM Policies (Session Management)
β Session Recording: Enabled
β Session Monitoring: Optional
π Ensures:
- Secure access
- Full session audit
π§Ύ Audit Retention Policy
β Default: 90 Days
π Stores:
- Logs
- User activities
- Session details
π§ Key Takeaways
β CyberArk Operations is daily activity
β System Health ensures uptime
β Safes control access
β Platforms control behavior
β Master Policy enforces security
π― Final Thoughts
CyberArk Operations is where real engineering happens.
π Anyone can learn theory…
π But operations define your real expertise
Comments ()