CyberArk PrivilegeCloud BreakglassProcedures
CyberArk PrivilegeCloud BreakglassProcedures
Environment
1 definitions
cyberark.com
cyberark.com
Customer
2 Environment
cyberark.com
PSM CPM Secure Tunnel
• Single PSM failure • Always a manual failover to avoid risk of ‘split • Single tunnel failure
brain’
• Recommendation – automatically • Supports high availability. Automatic
handled by load-balancer • If not urgently required – no action failover to next available tunnel
necessary
• Alternative – DNS round robin • All tunnel failure
• Pending rotations will happen when
• Alternative – manual failover by editing CPM started • Root cause needs to be investigated
Platform settings based on affected integration e.g.,
• If needed urgently – e.g. if using OTP + LDAP, SAML, HTML5 Gateway, RADIUS
• All PSM failure Exclusive Access
• Temporarily allow ‘retrieve’ via Web • Passive CPM can assume identity of
Portal (PVWA) normally active CPM by performing 5
CPM failover
cyberark.com
Privilege Cloud
3 Service
cyberark.com
• CyberArk service availability and security is committed to an SLA of 99.95%
• A monitoring system is responsible for a service health check and interacts with an on-call automatic management system
• The Privilege Cloud portal and vault instances are both immutable
• Each customer has isolated tenant and dedicated service components (e.g. instances, network, security groups etc.)
• DDoS protection, WAF and additional AWS Security services are applied to protect and secure the service
• CSA CAIQ
• SIG LITE
cyberark.com
3.1 Offline Access
cyberark.com
Solution Overview
• Utilizes the CyberArk Mobile app (Available on iOS and Android) that allows for offline syncing of credentials
• Can configure notification interval (days) to prompt the user to sync credentials
9
• Supports biometric and SAML authentication
• Domain Admin, Unix Root, Network equipment admin, other mission critical accounts
• Password syncing is a manual process and frequent rotation may cause passwords to become out of sync
• Limit the scope to a small number of users who have access to these accounts
• Consider using ‘split password’ functionality (like a physical safe requiring two people to access)
10
12
cyberark.com
• The scope of credentials should be limited to a small number of users and accounts. Similar to offline access.
• Rotate and update the credentials in the safe once the service is restored
14
cyberark.com
More Information
Configure Offline Access to target machines
15
cyberark.com