TechValidate Research on CyberArk

Introduction

This case study of a large enterprise financial services company is based on an April 2018 survey of CyberArk customers by TechValidate, a 3rd-party research service. The profiled company asked to have their name blinded to protect their confidentiality.

Challenges

The business challenges that led the profiled company to evaluate and ultimately select CyberArk:

• Resolved the following challenges after using CyberArk:
  • Securing credentials used by applications
  • IT admins having more privileges than they truly need
  • Protecting assets running in the cloud
  • Cloud platforms not easily configured.
• Adopted CyberArk’s privileged access security because of the following compelling business drivers:
  • Initiated a proactive security project
  • Were driven by a board-level or executive mandate
• Selected a solution for privileged access security to:
  • Limit the exposure of privileged credentials
  • Enforce strong passwords, store them in an encrypted vault, and rotate them
  • Simplify audit and compliance requirements
  • Remove hard-coded credentials from applications and scripts, including applications built using DevOps methodologies
  • Secure third-party access
  • Secure privileges on endpoints
  • Secure infrastructure and assets in the cloud

Use Case

The key features and functionalities of CyberArk that the surveyed company uses:

• Uses CyberArk for the following:
  • Securing privileged credentials in a vault
  • Rotating credentials based on policies
  • Securing and rotating shared service accounts
  • Monitoring and recording privileged sessions
  • Detecting and responding to attempts to circumvent privileged access controls
  • Securing secrets used by DevOps and Continuous Integration/Continuous Delivery (CI/CD) tools
  • Flagging and reviewing high-risk activity
• Managing the following types of privileged accounts, credentials, and secrets with CyberArk in the next 12 to 18 months:
  • Domain admin accounts
  • Microsoft Windows admin accounts
  • NIX admin accounts (UNIX and Linux)
  • Database or application admin accounts
  • Cloud admin consoles for IaaS or PaaS (Amazon Web Services, Microsoft Azure, Google Cloud, OpenShift, Pivotal Cloud Foundry)
  • Local admin accounts on workstations
  • Service accounts
• Plans to integrate the following tools with CyberArk within the next 18 months:
  • Authentication (DUO or OKTA, RSA)
  • The cloud (Amazon Web Services, Microsoft Azure, Google Cloud Platform)
  • Identity and access (Sailpoint, RSA)
  • Orchestration and threat response (ServiceNow, ProofPoint)
  • SIEM (Splunk, Fortinet, LogRhythm)

Results

The surveyed company achieved the following results with CyberArk:

• Reports that since adopting CyberArk to manage their privileged accounts and credentials, they are now more secure.
• Reports that since adopting CyberArk to secure their privileged accounts and credentials, the time and cost of audit reporting has stayed the same.
• Reports that with CyberArk, the time required to manage and maintain privileged account and credential security has reduced.

Introduction

This case study of a large enterprise banking company is based on an April 2018 survey of CyberArk customers by TechValidate, a 3rd-party research service. The profiled company asked to have their name blinded to protect their confidentiality.

Challenges

The business challenges that led the profiled company to evaluate and ultimately select CyberArk:

• Resolved the following challenges after using CyberArk:
  • Balancing security with productivity
  • Rampant password reuse across multiple accounts
  • IT admins having more privileges than they truly need
  • Unmanaged or unaudited third-party / remote vendor access
• Adopted CyberArk’s privileged access security because of the following compelling business drivers:
  • Initiated a proactive security project
  • Wanted to be better prepared for an audit
  • Were driven by a board-level or executive mandate
• Selected a solution for privileged access security to:
  • Limit the exposure of privileged credentials
  • Enforce strong passwords, store them in an encrypted vault, and rotate them
  • Simplify audit and compliance requirements
  • Secure privileged accounts and credentials for non-IT users (Finance, HR, Marketing)

Use Case

The key features and functionalities of CyberArk that the surveyed company uses:

• Uses CyberArk for the following:
  • Securing privileged credentials in a vault
  • Rotating credentials based on policies
  • Securing and rotating shared service accounts
  • Monitoring and recording privileged sessions
  • Securing credentials used by applications
• Managing the following types of privileged accounts, credentials, and secrets with CyberArk in the next 12 to 18 months:
  • Domain admin accounts
  • Microsoft Windows admin accounts
  • NIX admin accounts (UNIX and Linux)
  • Network device accounts
  • Database or application admin accounts
  • Cloud admin consoles for IaaS or PaaS (Amazon Web Services, Microsoft Azure, Google Cloud, OpenShift, Pivotal Cloud Foundry)
  • Local admin accounts on workstations
  • Application credentials
  • Secrets used by DevOps tools
  • Service accounts
  • Robotic process automations
• Plans to integrate the following tools with CyberArk within the next 18 months:
  • Authentication (DUO or OKTA, RSA)
  • The cloud (Amazon Web Services, Microsoft Azure, Google Cloud Platform)
  • Robotic process automation (BluePrism, UI path)
  • SIEM (Splunk, Fortinet, LogRhythm)
  • Vulnerability management (Qualys, Rapid7, Tenable)

Results

The surveyed company achieved the following results with CyberArk:

• Reports that since adopting CyberArk to manage their privileged accounts and credentials, they are now much more secure.
• Reports that since adopting CyberArk to secure their privileged accounts and credentials, the time and cost of audit reporting has reduced a lot.
• Reports that with CyberArk, the time required to manage and maintain privileged account and credential security has reduced dramatically.