CyberArk Secure Cloud Access can be improved as there is initial complexity and it is somewhat expensive. I would elaborate that the learning curve needs to be very explainable or very easy because it is somewhat tough, so they need to work on this particular learning path as well. I chose an eight because, as I explained, it is somewhat expensive, and the documentation part needs to be very easy; as of now, it is very complex. The initial complexity is present, and policy setup and integrations need proper planning.
In my perspective, I do not see much that could still be improved about CyberArk Secure Cloud Access. Depending on what is used to do the integration, looking at the requester's posture could be beneficial. In the future for CyberArk Secure Cloud Access, I would like to see tokenization improved, where every connection gets a new token. Not in the sense of a connection token but more a certificate that encrypts the data and gets deleted.
CyberArk Secure Cloud Access provides a solid foundation overall, but the UI/UX might be challenging for less tech-savvy individuals. Something user-friendly that improves the interface and the initial setup process would enhance the experience. The technical documentation requires a high level of understanding about how CyberArk works, and this could be improved.
The customization of CyberArk Secure Cloud Access could be improved because I found scenarios where I could not provide the correct configuration due to insufficient options available. I understand the approach that keeping it simple makes it easier to deploy in general, but additional customization capabilities would be beneficial. Real-time monitoring with CyberArk Secure Cloud Access is missing some features that I believe are on the roadmap, such as AI-generated descriptions of events and summarization of events. These features would be particularly helpful for SOC analysis and are important for SOC members. The audit trail in the past was not very informative and requires improvements. I believe this is the reason why AI enrichment was prioritized in development.
CyberArk Secure Cloud Access involves substantial effort when performing on-premises deployments. The SaaS or cloud version is less time-consuming compared to the on-premises deployment. With on-premises deployment, you must do a great deal, including spinning up the infrastructure itself and adding it to the HSM before integrating or onboarding where you want to control through PAM. This requires significant human resources. The deployment complexity may not be entirely accurate in my assessment because it has been a while since I left the engineering aspect and moved into more managerial roles. Before, when I was using it, too many components were involved in CyberArk Secure Cloud Access deployment. You need to understand every component because the least mistake results in being completely locked out of the system. Having too many components makes the deployment difficult and is not easy to understand. You have to be technically inclined to perform the deployment successfully.
CyberArk Secure Cloud Access has limitations in support for on-premise teams. When issues arise with the VPN portal or the frontend, the admin team must directly engage the vendor, which can be time-consuming. It is important for critical support to respond within fifteen to twenty minutes to minimize business impact.
CyberArk Secure Cloud Access improves security with its dynamic role-based access and efficient management of private keys, minimizing security risks and enhancing user experience in demanding cloud environments.
CyberArk Secure Cloud Access is designed for lightweight deployment, offering high availability and robust security features. Its seamless integration with SIEM enhances user experience, while private key management reduces manual entry dependency. Comprehensive audit trails and...
CyberArk Secure Cloud Access can be improved as there is initial complexity and it is somewhat expensive. I would elaborate that the learning curve needs to be very explainable or very easy because it is somewhat tough, so they need to work on this particular learning path as well. I chose an eight because, as I explained, it is somewhat expensive, and the documentation part needs to be very easy; as of now, it is very complex. The initial complexity is present, and policy setup and integrations need proper planning.
In my perspective, I do not see much that could still be improved about CyberArk Secure Cloud Access. Depending on what is used to do the integration, looking at the requester's posture could be beneficial. In the future for CyberArk Secure Cloud Access, I would like to see tokenization improved, where every connection gets a new token. Not in the sense of a connection token but more a certificate that encrypts the data and gets deleted.
CyberArk Secure Cloud Access provides a solid foundation overall, but the UI/UX might be challenging for less tech-savvy individuals. Something user-friendly that improves the interface and the initial setup process would enhance the experience. The technical documentation requires a high level of understanding about how CyberArk works, and this could be improved.
The customization of CyberArk Secure Cloud Access could be improved because I found scenarios where I could not provide the correct configuration due to insufficient options available. I understand the approach that keeping it simple makes it easier to deploy in general, but additional customization capabilities would be beneficial. Real-time monitoring with CyberArk Secure Cloud Access is missing some features that I believe are on the roadmap, such as AI-generated descriptions of events and summarization of events. These features would be particularly helpful for SOC analysis and are important for SOC members. The audit trail in the past was not very informative and requires improvements. I believe this is the reason why AI enrichment was prioritized in development.
CyberArk Secure Cloud Access involves substantial effort when performing on-premises deployments. The SaaS or cloud version is less time-consuming compared to the on-premises deployment. With on-premises deployment, you must do a great deal, including spinning up the infrastructure itself and adding it to the HSM before integrating or onboarding where you want to control through PAM. This requires significant human resources. The deployment complexity may not be entirely accurate in my assessment because it has been a while since I left the engineering aspect and moved into more managerial roles. Before, when I was using it, too many components were involved in CyberArk Secure Cloud Access deployment. You need to understand every component because the least mistake results in being completely locked out of the system. Having too many components makes the deployment difficult and is not easy to understand. You have to be technically inclined to perform the deployment successfully.
CyberArk Secure Cloud Access has limitations in support for on-premise teams. When issues arise with the VPN portal or the frontend, the admin team must directly engage the vendor, which can be time-consuming. It is important for critical support to respond within fifteen to twenty minutes to minimize business impact.