I'm working with on-premises solutions. Back in the time there were no other options. I use multi-factor authentication with Idira Identity. I sell it, I deploy it, so it's something that is really important in the strategy of Idira Identity platform from top to bottom where the MFA part is at the bottom. Every day users should use it every day, and it should be developed in the future. The password vault, the origin of CyberArk 25 years ago, is still used for some specific use cases. It's still required by privileged access. This is something that customers use, and in my region, I think it's still the most used part of Idira Identity, of CyberArk.
It's not being purchased through AWS, but we're using CyberArk Identity as a SaaS solution. I think it's running on AWS, but we bought it directly from CyberArk.
We are using CyberArk Identity for user provisioning, and we have integrated multiple applications, most of them being SAML-based authentication ones. We are also provisioning users to target applications and using CyberArk Identity as an authentication method for two-factor authentication. I have worked on multiple projects where we have integrated external IdPs with CyberArk Identity. We have also implemented AD integration to get users from Active Directory to CyberArk Identity. We are using the reporting functionality and role-based access control. We have created several roles for one client where I was working. It was an all-suite ISPS model that CyberArk has where CyberArk Identity, Privileged Cloud, and all those applications were present. In this case, we were using roles from CyberArk Identity to grant users access to their respective safes in the Privileged Cloud.
My use case for CyberArk Identity involves multiple reasons: for identity to gain access to the clients' environments, to provision on-demand access, and to provide services via the Access Manager.
Essentially, our use case for CyberArk Identity involves automating customer interactions and engagement, as well as onboarding new clients. Being in retail and marketing, CyberArk Identity has made it easier to onboard new customers online, making the process much faster and efficient. Interaction with customers has improved greatly through CyberArk Identity software through automation of most of our processes, thus freeing our time to concentrate on other key strategic activities of the company.
CyberArk Identity is mainly used for accessing servers, partition management, and rotating passwords, especially in sensitive sectors such as banking and to protect patient data. It's crucial for complying with regulations and ensuring that administrative tasks such as encryption key management are streamlined.
I work with Direct Identity. I was studying CyberArk, and I have used it a few times. Then I switched to a new project. I have some experience with CyberArk Identity.
CyberArk Identity's main use case is protecting privileged accounts. Although they've expanded into identity and access management, most of their business comes from privilege account management.
Security Consultant at a financial services firm with 10,001+ employees
Real User
Feb 1, 2024
For CyberArk Identity, a typical scenario involves using it with a federation, like Active Directory or Azure AD, to manage user identities. Since CyberArk Identity is a SaaS offering (not installable on-premise), identity connectors bridge the gap between the customer's directory (Azure AD or Active Directory) and CyberArk Identity. These connectors essentially synchronize the two systems. For example, disabling an account in the customer's directory (either Azure AD or Active Directory) automatically disables the corresponding account in CyberArk Identity if the identity connector is present. However, if you manage accounts manually within CyberArk Identity, you don't necessarily need a connector. This specific connector is called the CyberArk Identity Connector. We can manage user access and permissions through CyberArk Identity. To fully manage it, we need a connector and whatever changes we want to make to user access or entitlements, if we do it in the CyberArk Identity end, the same will reflect in the customer's AD (Active Directory) also if you have the Identity Connector. We use CyberArk Identity for multiple applications, like, for a single sign-on across multiple applications. Some customers use it for managing server privileges through the SaaS version. In this case, CyberArk Identity facilitates the connection by federating the customer's Active Directory or Azure AD with the CyberArk SaaS environment. However, they only utilize a few features of CyberArk Identity, not its full potential.
Obrela Group of Companies IT Manager & Security Integration Manager at Obrela
Real User
Nov 23, 2023
We use CyberArk Identity to handle the identity of an Active Directory, to handle Linux and other systems, and for API configurations that can handle even database accesses and third-party IDB accesses.
CyberArk offers multiple products, including PAN, LRO for vendor remote access, and Identity. Some clients in the entertainment and tourism industry prefer using CyberArk Identity on the cloud as a Software as a Service (SaaS) solution. Their teams are typically small and prefer not to manage the infrastructure. They opt for this approach because they want to avoid investing significant time and money in larger products like SailPoint. However, it's important to note that such clients are relatively rare, with perhaps just one or two out of every hundred.
Information Security Engineer - Pre-sales at a tech services company with 11-50 employees
Real User
May 12, 2023
We are using CyberArk Identity to consolidate all the applications and demo tenants that we have in the same panel and to apply features, such as MFA and single sign-on.
Pre-sales engineer at a computer software company with 201-500 employees
Real User
Mar 9, 2023
Customers primarily use the solution for multi-factor authentication and single sign on. It's good for source authentication. I do not use it personally.
I use CyberArk Identity for filling out demonstration environments for clients that have it installed on their premise or they're using the cloud version. I just create it for a proof of value demonstration.
Hyperautomation Architect at a insurance company with 10,001+ employees
Real User
Dec 16, 2021
We integrate the CyberArk components with the UiPath Orchestrator tool to manage all the passwords for our bots. We put all our automations on a VM, which runs the script. That's what we call a "bot," but we need service accounts to manage all these. We have customers with hundreds or thousands of bots, and it's challenging for us to manage the credentials for those service accounts. We use CyberArk to rotate the passwords 30 to 60 days, depending on the customer requirement. CyberArk gives us that functionality. We have a credential vault where all the passwords are stored, and we can rotate them by connecting UiPath to CyberArk. We store the credentials for those bots in the vault, and CyberArk rotates the password, communicates with the orchestrator, and gives back the username and password. UiPath Orchestrator is the central control tower, if you will. It accesses those VMs using those passwords and runs the automation.
Executive Director at Consulting and Enterprise Integrations S.A. de C.V.
Real User
Nov 6, 2020
We sell as well as use this solution for our IT operations. We are using it for single sign-on. We are a small company, and we have a few users of this solution.
CyberArk Identity is a versatile identity management solution suitable for a wide range of enterprises. It is designed to enhance enterprise security and improve user experience. Its focus on security, compliance, and operational efficiency, combined with positive user feedback, makes it a strong contender in the identity management space.
CyberArk Identity offers a robust suite of features to manage user identities and access privileges. It focuses on securing access to...
I'm working with on-premises solutions. Back in the time there were no other options. I use multi-factor authentication with Idira Identity. I sell it, I deploy it, so it's something that is really important in the strategy of Idira Identity platform from top to bottom where the MFA part is at the bottom. Every day users should use it every day, and it should be developed in the future. The password vault, the origin of CyberArk 25 years ago, is still used for some specific use cases. It's still required by privileged access. This is something that customers use, and in my region, I think it's still the most used part of Idira Identity, of CyberArk.
It's not being purchased through AWS, but we're using CyberArk Identity as a SaaS solution. I think it's running on AWS, but we bought it directly from CyberArk.
We are using CyberArk Identity for user provisioning, and we have integrated multiple applications, most of them being SAML-based authentication ones. We are also provisioning users to target applications and using CyberArk Identity as an authentication method for two-factor authentication. I have worked on multiple projects where we have integrated external IdPs with CyberArk Identity. We have also implemented AD integration to get users from Active Directory to CyberArk Identity. We are using the reporting functionality and role-based access control. We have created several roles for one client where I was working. It was an all-suite ISPS model that CyberArk has where CyberArk Identity, Privileged Cloud, and all those applications were present. In this case, we were using roles from CyberArk Identity to grant users access to their respective safes in the Privileged Cloud.
My use case for CyberArk Identity involves multiple reasons: for identity to gain access to the clients' environments, to provision on-demand access, and to provide services via the Access Manager.
Essentially, our use case for CyberArk Identity involves automating customer interactions and engagement, as well as onboarding new clients. Being in retail and marketing, CyberArk Identity has made it easier to onboard new customers online, making the process much faster and efficient. Interaction with customers has improved greatly through CyberArk Identity software through automation of most of our processes, thus freeing our time to concentrate on other key strategic activities of the company.
CyberArk Identity is mainly used for accessing servers, partition management, and rotating passwords, especially in sensitive sectors such as banking and to protect patient data. It's crucial for complying with regulations and ensuring that administrative tasks such as encryption key management are streamlined.
I work with Direct Identity. I was studying CyberArk, and I have used it a few times. Then I switched to a new project. I have some experience with CyberArk Identity.
I use the solution in my company for its vaults.
CyberArk Identity's main use case is protecting privileged accounts. Although they've expanded into identity and access management, most of their business comes from privilege account management.
For CyberArk Identity, a typical scenario involves using it with a federation, like Active Directory or Azure AD, to manage user identities. Since CyberArk Identity is a SaaS offering (not installable on-premise), identity connectors bridge the gap between the customer's directory (Azure AD or Active Directory) and CyberArk Identity. These connectors essentially synchronize the two systems. For example, disabling an account in the customer's directory (either Azure AD or Active Directory) automatically disables the corresponding account in CyberArk Identity if the identity connector is present. However, if you manage accounts manually within CyberArk Identity, you don't necessarily need a connector. This specific connector is called the CyberArk Identity Connector. We can manage user access and permissions through CyberArk Identity. To fully manage it, we need a connector and whatever changes we want to make to user access or entitlements, if we do it in the CyberArk Identity end, the same will reflect in the customer's AD (Active Directory) also if you have the Identity Connector. We use CyberArk Identity for multiple applications, like, for a single sign-on across multiple applications. Some customers use it for managing server privileges through the SaaS version. In this case, CyberArk Identity facilitates the connection by federating the customer's Active Directory or Azure AD with the CyberArk SaaS environment. However, they only utilize a few features of CyberArk Identity, not its full potential.
We use CyberArk Identity to handle the identity of an Active Directory, to handle Linux and other systems, and for API configurations that can handle even database accesses and third-party IDB accesses.
CyberArk offers multiple products, including PAN, LRO for vendor remote access, and Identity. Some clients in the entertainment and tourism industry prefer using CyberArk Identity on the cloud as a Software as a Service (SaaS) solution. Their teams are typically small and prefer not to manage the infrastructure. They opt for this approach because they want to avoid investing significant time and money in larger products like SailPoint. However, it's important to note that such clients are relatively rare, with perhaps just one or two out of every hundred.
My company uses CyberArk Identity for password vault, password management, and session management.
We are using CyberArk Identity to consolidate all the applications and demo tenants that we have in the same panel and to apply features, such as MFA and single sign-on.
The tool helps with authentication. It acts as an MFA for any kind of privileged access that occurs in our organization.
Customers primarily use the solution for multi-factor authentication and single sign on. It's good for source authentication. I do not use it personally.
We've used the product for some single sign-on use cases.
I use CyberArk Identity for filling out demonstration environments for clients that have it installed on their premise or they're using the cloud version. I just create it for a proof of value demonstration.
I am using CyberArk Identity for privileged identity management or access management.
We use CyberArk for security purposes.
We integrate the CyberArk components with the UiPath Orchestrator tool to manage all the passwords for our bots. We put all our automations on a VM, which runs the script. That's what we call a "bot," but we need service accounts to manage all these. We have customers with hundreds or thousands of bots, and it's challenging for us to manage the credentials for those service accounts. We use CyberArk to rotate the passwords 30 to 60 days, depending on the customer requirement. CyberArk gives us that functionality. We have a credential vault where all the passwords are stored, and we can rotate them by connecting UiPath to CyberArk. We store the credentials for those bots in the vault, and CyberArk rotates the password, communicates with the orchestrator, and gives back the username and password. UiPath Orchestrator is the central control tower, if you will. It accesses those VMs using those passwords and runs the automation.
We sell as well as use this solution for our IT operations. We are using it for single sign-on. We are a small company, and we have a few users of this solution.
We are still testing this solution, but our main use case is for integrating multiple IDs for the on-premise Active Directory.