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.
Anti-Rationalization Table
| Rationalization |
Reality |
| "I'll figure it out as I go" |
A structured approach saves time and reduces errors. Follow the workflow in this skill rather than improvising. |
| "I already know this topic" |
Familiarity breeds shortcuts. Use the checklist to verify you haven't missed critical steps. |
| "This doesn't apply to my situation" |
The patterns here generalize across contexts. Adapt, don't skip — the underlying principles hold. |
| "One more tool will fix it" |
Adding complexity rarely solves process gaps. Master the core workflow first. |
When to Use
Trigger phrases:
"implementing privileged access management with cyberark"
"Deploy CyberArk Privileged Access Management to discover, vault, rotate, and mon"
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
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
This section covers key concepts for implementing privileged access management with cyberark.
- Ensure all prerequisites are met before proceeding
- Follow the documented workflow steps in sequence
- Record results and any anomalies encountered during this phase
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
Workflow
# Example: IOC detection
import re
IOC_PATTERNS = {
"ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",
"domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",
"hash_md5": r"\b[a-f0-9]{32}\b",
"hash_sha256": r"\b[a-f0-9]{64}\b",
}
def extract_iocs(text: str) -> dict:
return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}
- Scope the task — define objectives, boundaries, and success criteria
- Gather information — collect all necessary data and context before proceeding
- Execute the core workflow — follow the domain-specific steps methodically
- Validate results — verify outputs against expected outcomes or baselines
- Document findings — record results, anomalies, and recommendations
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
When NOT to Use
- You need to test the implementation (use performing-* skills)
- Task is about configuring existing tools (use configuring-* skills)
- You need to analyze security events (use analyzing-* skills)
- Task is about building detection rules (use building-* skills)
- You don't have access to the target environment
- Task requires vendor-specific expertise (consult vendor docs)
Red Flags
- Performing actions without explicit written authorization from the asset owner
- Testing against production systems without a defined scope and rules of engagement
- Sharing sensitive findings or credentials in unencrypted communications
- Failing to properly scope and contain the assessment before starting
Process
- Analyze the task requirements
- Apply domain expertise
- Verify output quality
1---2name: implementing-privileged-access-management-with-cyberark3description: Use when deploying CyberArk Privileged Access Management to discover,4 vault, rotate, and monitor privileged credentials across enterprise infrastructure.5 This skill covers vault architecture, session isolation, c6domain: cybersecurity7subdomain: identity-access-management8tags:9- iam10- identity11- access-control12- privileged-access13- pam14- cyberark15version: '1.0'16author: oyi7717license: Apache-2.018nist_csf:19- PR.AA-0120- PR.AA-0221- PR.AA-0522- PR.AA-0623category: cybersecurity24metadata:25 source: https://skillmd.com/skills/oyi77/implementing-privileged-access-management-with-cyberark26---2728# Implementing Privileged Access Management with CyberArk2930## Overview31Deploy 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.32333435## Anti-Rationalization Table3637| Rationalization | Reality |38|---|---|39| "I'll figure it out as I go" | A structured approach saves time and reduces errors. Follow the workflow in this skill rather than improvising. |40| "I already know this topic" | Familiarity breeds shortcuts. Use the checklist to verify you haven't missed critical steps. |41| "This doesn't apply to my situation" | The patterns here generalize across contexts. Adapt, don't skip — the underlying principles hold. |42| "One more tool will fix it" | Adding complexity rarely solves process gaps. Master the core workflow first. |4344## When to Use45**Trigger phrases:**46- "implementing privileged access management with cyberark"47- "Deploy CyberArk Privileged Access Management to discover, vault, rotate, and mon"484950- When deploying or configuring implementing privileged access management with cyberark capabilities in your environment51- When establishing security controls aligned to compliance requirements52- When building or improving security architecture for this domain53- When conducting security assessments that require this implementation5455## Prerequisites5657- Familiarity with identity access management concepts and tools58- Access to a test or lab environment for safe execution59- Python 3.8+ with required dependencies installed60- Appropriate authorization for any testing activities6162## Objectives63- Design CyberArk vault architecture with high availability64- Implement automated privileged credential discovery and onboarding65- Configure credential rotation policies for different account types66- Deploy Privileged Session Manager (PSM) for session isolation and recording67- Integrate CyberArk with SIEM for privileged access monitoring68- Implement just-in-time (JIT) privileged access workflows6970## Key Concepts7172This section covers key concepts for implementing privileged access management with cyberark.7374- Ensure all prerequisites are met before proceeding75- Follow the documented workflow steps in sequence76- Record results and any anomalies encountered during this phase77### CyberArk Architecture Components781. **Digital Vault**: Encrypted credential storage with FIPS 140-2 validated encryption792. **Central Policy Manager (CPM)**: Automated password rotation and verification803. **Privileged Session Manager (PSM)**: Session isolation, recording, and keystroke logging814. **Password Vault Web Access (PVWA)**: Web interface for credential management825. **Privileged Threat Analytics (PTA)**: Behavioral analytics for privileged accounts836. **Conjur Secrets Manager**: Application identity and secrets management8485### Vault Security Model86- **Master Policy**: Global security settings (dual control, exclusive access, one-time passwords)87- **Safes**: Logical containers for credentials with granular permissions88- **Platforms**: Configuration profiles defining rotation, verification, and reconciliation89- **Account Groups**: Link accounts sharing rotation dependencies9091### Credential Lifecycle921. **Discovery**: Scan infrastructure for privileged accounts932. **Onboarding**: Import accounts into vault with platform assignment943. **Rotation**: Automated password changes per policy schedule954. **Verification**: Periodic validation that vaulted credentials work965. **Reconciliation**: Re-sync credentials when vault and target are out of sync976. **Decommissioning**: Remove accounts no longer needed9899## Workflow100101```python102# Example: IOC detection103import re104105IOC_PATTERNS = {106 "ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",107 "domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",108 "hash_md5": r"\b[a-f0-9]{32}\b",109 "hash_sha256": r"\b[a-f0-9]{64}\b",110}111112def extract_iocs(text: str) -> dict:113 return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}114```1151161. **Scope the task** — define objectives, boundaries, and success criteria1172. **Gather information** — collect all necessary data and context before proceeding1183. **Execute the core workflow** — follow the domain-specific steps methodically1194. **Validate results** — verify outputs against expected outcomes or baselines1205. **Document findings** — record results, anomalies, and recommendations121### Step 1: Vault Architecture Design1221. Deploy primary vault server in secured network segment1232. Configure vault high availability with DR vault1243. Harden vault server OS (remove unnecessary services, disable RDP)1254. Configure firewall rules (only port 1858 from authorized components)1265. Set up vault backup with encryption127128### Step 2: Safe and Policy Configuration1291. Create safe hierarchy aligned with business units1302. Define safe members with least-privilege roles:131 - Safe Admins: manage safe membership132 - Credential Managers: add/modify accounts133 - Auditors: view audit logs only134 - Users: retrieve/use credentials1353. Configure Master Policy settings:136 - Require dual control for credential retrieval137 - Enable exclusive access (one user per credential at a time)138 - Set one-time password mode for sensitive accounts139140### Step 3: Platform Configuration141- Windows Domain Admin: Rotate every 24 hours, verify every 4 hours142- Linux Root: Rotate every 72 hours with SSH key rotation143- Database Admin (Oracle, SQL Server): Rotate every 24 hours144- Network Devices: Rotate every 7 days145- Service Accounts: Rotate on schedule with dependency management146- Cloud IAM Keys: Rotate every 90 days with dual-key strategy147148### Step 4: Privileged Session Management1491. Deploy PSM servers behind load balancer1502. Configure session recording (video, keystroke, command logs)1513. Set up session isolation (users connect through PSM, never directly)1524. Define connection components for RDP, SSH, databases, web apps1535. Configure live session monitoring and termination capabilities1546. Set session recording retention (minimum 1 year for compliance)155156### Step 5: Integration and Monitoring1571. Forward CyberArk audit logs to SIEM (CEF/Syslog format)1582. Configure PTA for behavioral analytics:159 - Detect credential theft indicators160 - Alert on suspicious privileged session activity161 - Monitor unmanaged privileged account usage1623. Integrate with ticketing system for access request workflows1634. Set up alerts for failed rotation, verification failures, policy violations164165## Security Controls166| Control | NIST 800-53 | Description |167|---------|-------------|-------------|168| Privileged Access | AC-6(7) | Privileged account controls |169| Credential Management | IA-5 | Automated credential rotation |170| Session Recording | AU-14 | Session audit capability |171| Access Enforcement | AC-3 | Vault-enforced access policies |172| Separation of Duties | AC-5 | Dual control for sensitive operations |173174## Common Pitfalls175- Not configuring reconciliation accounts leading to lockouts after rotation176- Setting rotation schedules too aggressive for service accounts with dependencies177- Failing to test PSM connection components before production deployment178- Not establishing break-glass procedures for vault unavailability179- Overlooking network device credential management180181## Verification182- [ ] Vault accessible only from authorized components183- [ ] Credential rotation succeeds for all onboarded accounts184- [ ] PSM sessions recorded and searchable185- [ ] Dual control enforced for sensitive credential checkout186- [ ] SIEM receives CyberArk audit events187- [ ] Break-glass procedure tested and documented188- [ ] DR vault failover tested successfully189## When NOT to Use190191- You need to test the implementation (use performing-* skills)192- Task is about configuring existing tools (use configuring-* skills)193- You need to analyze security events (use analyzing-* skills)194- Task is about building detection rules (use building-* skills)195- You don't have access to the target environment196- Task requires vendor-specific expertise (consult vendor docs)197198199## Red Flags200201- Performing actions without explicit written authorization from the asset owner202- Testing against production systems without a defined scope and rules of engagement203- Sharing sensitive findings or credentials in unencrypted communications204- Failing to properly scope and contain the assessment before starting205206## Process2072081. Analyze the task requirements2092. Apply domain expertise2103. Verify output quality