Implementing Privileged Access Management With Cyberark

Implementing Privileged Access Management with CyberArk

Overview

Deploy CyberArk Privileged Access Management to discover, vault, rotate, and monitor privileged credentials across enterprise infrastructure. This skill covers vault architecture, session isolation, credential rotation policies, and integration with NIST 800-53 access control requirements.

When to Use

• When deploying or configuring implementing privileged access management with cyberark capabilities in your environment
• When establishing security controls aligned to compliance requirements
• When building or improving security architecture for this domain
• When conducting security assessments that require this implementation

Common Misconfigurations & Verification

CyberArk gives strong audit only if every privileged path goes through the vault and PSM — these silently undermine it:

• PSM bypass via direct connection: accounts are vaulted but admins still RDP/SSH straight to targets using the same credentials, so no session recording occurs. Verify targets accept connections only from PSM server IPs (host firewall / jump-host enforcement), then attempt a direct connect — it must fail. Cross-check that every Retrieve audit event correlates to a PSM session; retrievals with no session indicate copy-paste of the password.
• CPM rotation not actually running: a platform is assigned but rotation/verification is failing silently (no reconciliation account, network block). Confirm via PVWA/REST that each account shows recent Last Successful Change and Last Successful Verification, not just "managed = true," and triage the CPM Failed queue.
• Reconciliation account missing: after a rotation drift the account locks out and admins fall back to a known break-glass password. Confirm a reconcile account is set per platform.
• Dual control / exclusive / one-time password set only on some Safes: audit Master Policy exceptions and confirm Tier-0 Safes enforce dual control and one-time passwords, not just the defaults.
• Break-glass / vault-unavailable procedure unmonitored: confirm the emergency credential is itself vaulted or sealed, and that any use raises a PTA/SIEM alert.
• Audit events not in SIEM: verify CyberArk forwards CEF/Syslog and that PTA alerts (credential theft, unmanaged privileged account use) are firing, not just enabled.

Prerequisites

• Familiarity with identity access management concepts and tools
• Access to a test or lab environment for safe execution
• Python 3.8+ with required dependencies installed
• Appropriate authorization for any testing activities

Objectives

• Design CyberArk vault architecture with high availability
• Implement automated privileged credential discovery and onboarding
• Configure credential rotation policies for different account types
• Deploy Privileged Session Manager (PSM) for session isolation and recording
• Integrate CyberArk with SIEM for privileged access monitoring
• Implement just-in-time (JIT) privileged access workflows

Key Concepts

CyberArk Architecture Components

1. Digital Vault: Encrypted credential storage with FIPS 140-2 validated encryption
2. Central Policy Manager (CPM): Automated password rotation and verification
3. Privileged Session Manager (PSM): Session isolation, recording, and keystroke logging
4. Password Vault Web Access (PVWA): Web interface for credential management
5. Privileged Threat Analytics (PTA): Behavioral analytics for privileged accounts
6. Conjur Secrets Manager: Application identity and secrets management

Vault Security Model

• Master Policy: Global security settings (dual control, exclusive access, one-time passwords)
• Safes: Logical containers for credentials with granular permissions
• Platforms: Configuration profiles defining rotation, verification, and reconciliation
• Account Groups: Link accounts sharing rotation dependencies

Credential Lifecycle

1. Discovery: Scan infrastructure for privileged accounts
2. Onboarding: Import accounts into vault with platform assignment
3. Rotation: Automated password changes per policy schedule
4. Verification: Periodic validation that vaulted credentials work
5. Reconciliation: Re-sync credentials when vault and target are out of sync
6. Decommissioning: Remove accounts no longer needed

Workflow

Step 1: Vault Architecture Design

1. Deploy primary vault server in secured network segment
2. Configure vault high availability with DR vault
3. Harden vault server OS (remove unnecessary services, disable RDP)
4. Configure firewall rules (only port 1858 from authorized components)
5. Set up vault backup with encryption

Step 2: Safe and Policy Configuration

1. Create safe hierarchy aligned with business units
2. Define safe members with least-privilege roles:
   • Safe Admins: manage safe membership
   • Credential Managers: add/modify accounts
   • Auditors: view audit logs only
   • Users: retrieve/use credentials
3. Configure Master Policy settings:
   • Require dual control for credential retrieval
   • Enable exclusive access (one user per credential at a time)
   • Set one-time password mode for sensitive accounts

Step 3: Platform Configuration

• Windows Domain Admin: Rotate every 24 hours, verify every 4 hours
• Linux Root: Rotate every 72 hours with SSH key rotation
• Database Admin (Oracle, SQL Server): Rotate every 24 hours
• Network Devices: Rotate every 7 days
• Service Accounts: Rotate on schedule with dependency management
• Cloud IAM Keys: Rotate every 90 days with dual-key strategy

Step 4: Privileged Session Management

1. Deploy PSM servers behind load balancer
2. Configure session recording (video, keystroke, command logs)
3. Set up session isolation (users connect through PSM, never directly)
4. Define connection components for RDP, SSH, databases, web apps
5. Configure live session monitoring and termination capabilities
6. Set session recording retention (minimum 1 year for compliance)

Step 5: Integration and Monitoring

1. Forward CyberArk audit logs to SIEM (CEF/Syslog format)
2. Configure PTA for behavioral analytics:
   • Detect credential theft indicators
   • Alert on suspicious privileged session activity
   • Monitor unmanaged privileged account usage
3. Integrate with ticketing system for access request workflows
4. Set up alerts for failed rotation, verification failures, policy violations

Security Controls

Common Pitfalls

• Not configuring reconciliation accounts leading to lockouts after rotation
• Setting rotation schedules too aggressive for service accounts with dependencies
• Failing to test PSM connection components before production deployment
• Not establishing break-glass procedures for vault unavailability
• Overlooking network device credential management

Verification

• Vault accessible only from authorized components
• Credential rotation succeeds for all onboarded accounts
• PSM sessions recorded and searchable
• Dual control enforced for sensitive credential checkout
• SIEM receives CyberArk audit events
• Break-glass procedure tested and documented
• DR vault failover tested successfully

Source: xalgord/xalgorix — distributed by TomeVault.