What is our primary use case?
Our use case is that our organization had a lot of certificates that were unnoticed. Users used to request the certificate and install it, but when there was a change of resources or anything, they were unaware of where the certificate resides or when it expires. We had a lot of situations where the certificate had expired, the application went down, or users used to get the nasty warning saying the certificate had expired. Another case was where a certificate had expired, or it was installed on multiple endpoints, but the users were unaware of it. They replaced the certificate at one endpoint and forwarded it over to another endpoint, which eventually caused an issue because of the handshake error. These were the main driving factors for us to explore CLM options.
How has it helped my organization?
Certificate Manager has reduced the certificate expiration outages to almost nil. Just to give an analysis, before 2022, we had a lot of major incidents due to expired certificates. Since 2022, we have had almost zero major incidents wherein we saw a financial impact or business disruption due to an expired certificate. We have set up alerts 60 days in advance, so that gives sufficient time for the technical owners, the product owners, and the application teams to renew the certificate ahead of time.
What is most valuable?
The notification stands out as one of the best features. You can customize the emails, and as a retail organization, it was important for us to brand the emails. We wanted our users to give a look and feel of the organization and also adhere to the organization brand guidelines. So, customization of emails was one of the good features. The main core aspect is the certificate tracking. Certificate Manager does this effectively, and its ease of use makes a difference.
When it comes to automation, Certificate Manager has a lot of out-of-the-box connectors, be it for the F5 load balancer, the NetScaler load balancer, for Windows, or for Linux machines. You can even automate the certificate, push the certificate from scratch from Certificate Manager.
The reporting feature is another aspect that many users love. We can schedule the reports and get them in either PDF or Excel spreadsheet formats when we want to share with the leadership. We can generate the PDF format and share it with the users.
The navigation is pretty good, with a sleek UI and a good dashboard that allows customization of the home page.
Another important feature that stands in favor of Certificate Manager is the customizability. When a user requests a certificate, we want them to input some additional details. The creation of custom fields was very flexible in Certificate Manager when we compared it with other products. We can define a number of fields and even specify input types, such as alphanumeric strings, numeric values, drop-down selections, and input validation.
What needs improvement?
Even though it allows for email editing, until version 23.1, you had to log on to the server, and the console itself used to take a lot of time. That has changed from the last release onwards.
When you're defining the flow, there are some areas that can probably cause confusion to the users. If you want to rename the default field, you cannot rename it, which caused a lot of confusion during the initial days until everyone got settled in. Allowing the renaming or updating of the default field is something Certificate Manager can improve on.
Certificate Manager has both the on-prem and the cloud versions, but the on-prem version is far more mature than the cloud version, which lacks a lot of features that the on-prem version offers, at least when we did the POC and evaluated the product. The maturity of the cloud version needs improvement.
Additionally, when considering the on-prem version, there is a minor glitch in the system. When an administrator makes changes, they have flexibility regarding the approval flow. When dealing with a certificate that requires approval from several different teams, there is a minor glitch in the system where the name of the approver does not appear. This is a bug that we are currently addressing.
Additionally, there is room for improvement in key management. Changing the default account name is not a straightforward process; it can be quite tedious. This is an area where improvements could be made.
If there is a particular workflow that we want to tweak, right now, we can achieve it only via a PowerShell script. It would be great if they could also support a small Python script or anything to expand their scripting or adaptable workflow code base. Even though we can call another script from a PowerShell script, if someone doesn't have knowledge of PowerShell, that would be challenging.
For how long have I used the solution?
It's been more than three years since we've been using the solution.
What do I think about the stability of the solution?
The stability is pretty stable. For one of their bugs, there are a few workarounds; I would probably give it a nine in terms of stability. This is only for the on-prem version as I do not have great exposure to the cloud version.
What do I think about the scalability of the solution?
It is definitely scalable. I would give scalability a nine, with one point off because of the lengthy time taken to install the product.
It was for an enterprise-wide solution, so more than 15,000 work with Certificate Manager.
How are customer service and support?
Certificate Manager was recently acquired by CyberArk, so it's a different situation right now. When Certificate Manager was solely Certificate Manager, I felt the support was pretty good. However, after the completion of the acquisition by CyberArk, I feel there has been a drastic downtime in the support professionals' response. If it were somewhere around nine earlier, I would probably bring it down to six right now.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
No. We didn't have a different solution previously.
How was the initial setup?
It was more or less a Windows next-next-next installer. It isn't a complex installation. Any IT security professional would be aware of all the dependent components, including the database, the bare minimum bare metal requirements, and everything else.
The installation process is a bit lengthy. Though it's simple, it involves a lot of modules that get installed. It took almost four hours for the entire installation and for the upgrade, which is almost a mimic of installation. It again depends on the number of servers you're doing it for. If you're doing it for one server, it will easily take 30 to 45 minutes, assuming you have a good connection.
It does require some maintenance, but it's not every month you need to patch it and update it. There is flexibility around it, but it does require some sort of management.
What about the implementation team?
Implementation was done by in-house team.
What was our ROI?
We evaluated Keyfactor and Certificate Manager, and even though Certificate Manager was priced far higher than Keyfactor, one of the main reasons for choosing Certificate Manager was the ROI we saw. Keyfactor doesn't offer any reporting. Certificate Manager reduced the number of resources for the reporting structure. We had six to seven people dedicated to reporting. We were able to give them better tasks instead of just reporting, so Certificate Manager's reporting capability adds great value to the ROI, along with the dashboard and automation.
Teams used to spend a lot of time just requesting and renewing the certificate, updating it at all endpoints. In Certificate Manager, you can do it with one click. Once you have defined the entire skeleton of where the certificate resides and what it does, you can just click the push button, and the certificate will be installed and bind the complete IIS binding by Certificate Manager. From our perspective, this makes it a good bet.
What's my experience with pricing, setup cost, and licensing?
Which other solutions did I evaluate?
We did a PoC with various vendors available in the market, such as Appviewx, Keyfactor, Certificate Manager, and finally narrowed it down to Certificate Manager because it suited our needs. It was able to give a better dashboard of how many certificates we have and what the installation points are. That's why we went ahead with it.
What other advice do I have?
I would recommend Certificate Manager, but it also depends on the organization's needs. I would recommend Certificate Manager to other users if they're looking for an on-prem solution. If they're looking for a cloud-based solution, I wouldn't recommend Certificate Manager, given that they have a long road ahead of them for maturity.
I would rate it an eight out of ten, given all the benefits, gaps, and overall maintenance.
Which deployment model are you using for this solution?
On-premises