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.
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
- Digital Vault: Encrypted credential storage with FIPS 140-2 validated encryption
- Central Policy Manager (CPM): Automated password rotation and verification
- Privileged Session Manager (PSM): Session isolation, recording, and keystroke logging
- Password Vault Web Access (PVWA): Web interface for credential management
- Privileged Threat Analytics (PTA): Behavioral analytics for privileged accounts
- 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
- Discovery: Scan infrastructure for privileged accounts
- Onboarding: Import accounts into vault with platform assignment
- Rotation: Automated password changes per policy schedule
- Verification: Periodic validation that vaulted credentials work
- Reconciliation: Re-sync credentials when vault and target are out of sync
- Decommissioning: Remove accounts no longer needed
Implementation Steps
Step 1: Vault Architecture Design
- Deploy primary vault server in secured network segment
- Configure vault high availability with DR vault
- Harden vault server OS (remove unnecessary services, disable RDP)
- Configure firewall rules (only port 1858 from authorized components)
- Set up vault backup with encryption
Step 2: Safe and Policy Configuration
- Create safe hierarchy aligned with business units
- 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
- 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
- Deploy PSM servers behind load balancer
- Configure session recording (video, keystroke, command logs)
- Set up session isolation (users connect through PSM, never directly)
- Define connection components for RDP, SSH, databases, web apps
- Configure live session monitoring and termination capabilities
- Set session recording retention (minimum 1 year for compliance)
Step 5: Integration and Monitoring
- Forward CyberArk audit logs to SIEM (CEF/Syslog format)
- Configure PTA for behavioral analytics:
- Detect credential theft indicators
- Alert on suspicious privileged session activity
- Monitor unmanaged privileged account usage
- Integrate with ticketing system for access request workflows
- Set up alerts for failed rotation, verification failures, policy violations
Security Controls
| Control |
NIST 800-53 |
Description |
| Privileged Access |
AC-6(7) |
Privileged account controls |
| Credential Management |
IA-5 |
Automated credential rotation |
| Session Recording |
AU-14 |
Session audit capability |
| Access Enforcement |
AC-3 |
Vault-enforced access policies |
| Separation of Duties |
AC-5 |
Dual control for sensitive operations |
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
1---2name: none-393description: Deploy CyberArk Privileged Access Management to discover, vault, rotate, and monitor privileged credentials across enterprise infrastructure. This skill covers vault architecture, session isolation, c4domain: cybersecurity5subdomain: identity-access-management6tags: [iam, identity, access-control, privileged-access, pam, cyberark]7version: "1.0"8author: mahipal9license: MIT10metadata:11 source: https://skillmd.com/skills/njones17/none-3912---1314# Implementing Privileged Access Management with CyberArk1516## Overview17Deploy 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.1819## Objectives20- Design CyberArk vault architecture with high availability21- Implement automated privileged credential discovery and onboarding22- Configure credential rotation policies for different account types23- Deploy Privileged Session Manager (PSM) for session isolation and recording24- Integrate CyberArk with SIEM for privileged access monitoring25- Implement just-in-time (JIT) privileged access workflows2627## Key Concepts2829### CyberArk Architecture Components301. **Digital Vault**: Encrypted credential storage with FIPS 140-2 validated encryption312. **Central Policy Manager (CPM)**: Automated password rotation and verification323. **Privileged Session Manager (PSM)**: Session isolation, recording, and keystroke logging334. **Password Vault Web Access (PVWA)**: Web interface for credential management345. **Privileged Threat Analytics (PTA)**: Behavioral analytics for privileged accounts356. **Conjur Secrets Manager**: Application identity and secrets management3637### Vault Security Model38- **Master Policy**: Global security settings (dual control, exclusive access, one-time passwords)39- **Safes**: Logical containers for credentials with granular permissions40- **Platforms**: Configuration profiles defining rotation, verification, and reconciliation41- **Account Groups**: Link accounts sharing rotation dependencies4243### Credential Lifecycle441. **Discovery**: Scan infrastructure for privileged accounts452. **Onboarding**: Import accounts into vault with platform assignment463. **Rotation**: Automated password changes per policy schedule474. **Verification**: Periodic validation that vaulted credentials work485. **Reconciliation**: Re-sync credentials when vault and target are out of sync496. **Decommissioning**: Remove accounts no longer needed5051## Implementation Steps5253### Step 1: Vault Architecture Design541. Deploy primary vault server in secured network segment552. Configure vault high availability with DR vault563. Harden vault server OS (remove unnecessary services, disable RDP)574. Configure firewall rules (only port 1858 from authorized components)585. Set up vault backup with encryption5960### Step 2: Safe and Policy Configuration611. Create safe hierarchy aligned with business units622. Define safe members with least-privilege roles:63 - Safe Admins: manage safe membership64 - Credential Managers: add/modify accounts65 - Auditors: view audit logs only66 - Users: retrieve/use credentials673. Configure Master Policy settings:68 - Require dual control for credential retrieval69 - Enable exclusive access (one user per credential at a time)70 - Set one-time password mode for sensitive accounts7172### Step 3: Platform Configuration73- Windows Domain Admin: Rotate every 24 hours, verify every 4 hours74- Linux Root: Rotate every 72 hours with SSH key rotation75- Database Admin (Oracle, SQL Server): Rotate every 24 hours76- Network Devices: Rotate every 7 days77- Service Accounts: Rotate on schedule with dependency management78- Cloud IAM Keys: Rotate every 90 days with dual-key strategy7980### Step 4: Privileged Session Management811. Deploy PSM servers behind load balancer822. Configure session recording (video, keystroke, command logs)833. Set up session isolation (users connect through PSM, never directly)844. Define connection components for RDP, SSH, databases, web apps855. Configure live session monitoring and termination capabilities866. Set session recording retention (minimum 1 year for compliance)8788### Step 5: Integration and Monitoring891. Forward CyberArk audit logs to SIEM (CEF/Syslog format)902. Configure PTA for behavioral analytics:91 - Detect credential theft indicators92 - Alert on suspicious privileged session activity93 - Monitor unmanaged privileged account usage943. Integrate with ticketing system for access request workflows954. Set up alerts for failed rotation, verification failures, policy violations9697## Security Controls98| Control | NIST 800-53 | Description |99|---------|-------------|-------------|100| Privileged Access | AC-6(7) | Privileged account controls |101| Credential Management | IA-5 | Automated credential rotation |102| Session Recording | AU-14 | Session audit capability |103| Access Enforcement | AC-3 | Vault-enforced access policies |104| Separation of Duties | AC-5 | Dual control for sensitive operations |105106## Common Pitfalls107- Not configuring reconciliation accounts leading to lockouts after rotation108- Setting rotation schedules too aggressive for service accounts with dependencies109- Failing to test PSM connection components before production deployment110- Not establishing break-glass procedures for vault unavailability111- Overlooking network device credential management112113## Verification114- [ ] Vault accessible only from authorized components115- [ ] Credential rotation succeeds for all onboarded accounts116- [ ] PSM sessions recorded and searchable117- [ ] Dual control enforced for sensitive credential checkout118- [ ] SIEM receives CyberArk audit events119- [ ] Break-glass procedure tested and documented120- [ ] DR vault failover tested successfully