StrongDM can be improved in many ways. For example, the access approval workflow could be faster. We face a challenge where we sometimes need temporary access to production but have to wait for an administrator to grant permission. This could be improved and streamlined. If they could provide a just-in-time access approval workflow with integrations to Slack or Microsoft Teams, that would greatly help, especially during production incidents. A faster approval workflow would be beneficial. Additionally, for large environments with many servers, features such as smart automations and resource tagging would be helpful and save time. One more feature I would like to add is more built-in operational dashboards. Although StrongDM has some dashboards, if they added more comprehensive dashboards, it would be easier to see who has access to what.
Solution Delivery Advisor at a tech vendor with 10,001+ employees
Real User
Top 20
Jul 14, 2026
I think StrongDM could improve by focusing more on network device management by allowing the addition of PAM for network devices, managing legacy network equipment, or helping to initiate enterprise onboarding where a lot of complex environments and initial setup are required. I think that would be a good area for StrongDM to work on. Apart from that, integration with SIEM and SOAR tools, regarding the logs generated by any privileged user account in these SIEM or SOAR tools, and how to ensure these logs are encrypted, are areas that if StrongDM focuses on, will help it gain advantage over other products in the market right now because they do not have it. Another area for improvement is the client-side footprint. If StrongDM can provide an installation for user workstations in strict or heavily lockdown environments, maintaining and deploying these desktop clients across thousands of machines can pose a logistical challenge for IT teams. If StrongDM can work on that area as well, it will be a great product.
Associate Software Engineer at a computer software company with 201-500 employees
Real User
Top 5
Jun 16, 2026
I would not say ease of use and integration are features to criticize because ease of use is something taken on by the user, so it is actually considerable. Integration, however, is something which admins configure with StrongDM, and in that area, it can be improved. Sometimes, if there is an architecture or infrastructure that is more complex, it would take extra time for integrations. I think something can be improved in AI, such as using AI for certain functions within StrongDM. Enhancing features with AI can help StrongDM grow significantly in its domain. I would say that reports can now be generated from the data StrongDM stores. For instance, if one user accessed a database or Kubernetes cluster a long time ago and is not using it now, applying intelligence to that data can better inform the admin. The system could indicate that a particular user has accessed that resource in the past but is not using it currently. Better addressing least privilege access by removing unnecessary access would be valuable. Those AI capabilities that provide insights to admins regarding access could be very helpful. I have already mentioned that AI capabilities can be improved, and the remaining aspects such as recording queries, sessions, and SSH keys are already being managed well by StrongDM. I believe AI capabilities could be enhanced, and I would also suggest improvement in reporting and dashboard generation with the data available in StrongDM.
I believe StrongDM can improve its initial setup and onboarding experience for larger enterprise environments like Scania, where we have a lot of processes. Integrating different teams, access policies, and existing identity workflows requires substantial planning. Additionally, I think the dashboard customization and reporting could be more flexible for operational teams, though new teams find it manageable. Once the platform is fully integrated, it provides significant value. Apart from the onboarding experience, I would also mention that the templates for enterprise onboarding and policy setup could benefit from innovative thinking tailored to organizations managing large AWS and Kubernetes workloads. Enhanced customization in dashboards and reporting would further ease operations and provide better insights.
Senior Network Security Engineer at EMAK For Computer Manufacturing (ECM)
Real User
Top 5
Apr 16, 2026
In StrongDM, I think the installation was hard, and they want to be more flexible in the initial setup. I think they want to add more features like traditional PAM. It is difficult to find documentation or materials to review how it works, and there is less product material available in the market.
Iam Engineer at a manufacturing company with 10,001+ employees
Real User
Top 20
Feb 23, 2026
StrongDM regularly requires patches and maintenance, but I think that's a good question for the PAM architects in our organization. If you guys could offer only a cloud-native solution, you would likely cater to different organizations. That could grow the product more.
Senior Data Engineer at a non-profit with 1,001-5,000 employees
Real User
Top 10
Oct 29, 2024
It would be beneficial to have better control and alignment between frequent updates and improved communication regarding possible negative effects on existing customer bases. Also, documentation sometimes lags behind the new features which can be a problem.
Senior Devops Engineer at a transportation company with 51-200 employees
Real User
Top 10
Aug 16, 2024
We started to use it as a client-side or split tunnel VPN. We are unable to overwrite the endpoints and direct traffic that way, but that's a technical limitation, and I understand why it's there.
StrongDM streamlines secure, password-less access, reducing attack surfaces with its zero trust approach. It integrates smoothly with existing systems supporting IP whitelisting and excels in managing runtime features while offering comprehensive audit logging and seamless resource access.StrongDM provides organizations with enhanced security through features like password rotation and efficient management of access to resources such as EC2 instances, Kubernetes clusters, and databases. Its...
StrongDM can be improved in many ways. For example, the access approval workflow could be faster. We face a challenge where we sometimes need temporary access to production but have to wait for an administrator to grant permission. This could be improved and streamlined. If they could provide a just-in-time access approval workflow with integrations to Slack or Microsoft Teams, that would greatly help, especially during production incidents. A faster approval workflow would be beneficial. Additionally, for large environments with many servers, features such as smart automations and resource tagging would be helpful and save time. One more feature I would like to add is more built-in operational dashboards. Although StrongDM has some dashboards, if they added more comprehensive dashboards, it would be easier to see who has access to what.
I think StrongDM could improve by focusing more on network device management by allowing the addition of PAM for network devices, managing legacy network equipment, or helping to initiate enterprise onboarding where a lot of complex environments and initial setup are required. I think that would be a good area for StrongDM to work on. Apart from that, integration with SIEM and SOAR tools, regarding the logs generated by any privileged user account in these SIEM or SOAR tools, and how to ensure these logs are encrypted, are areas that if StrongDM focuses on, will help it gain advantage over other products in the market right now because they do not have it. Another area for improvement is the client-side footprint. If StrongDM can provide an installation for user workstations in strict or heavily lockdown environments, maintaining and deploying these desktop clients across thousands of machines can pose a logistical challenge for IT teams. If StrongDM can work on that area as well, it will be a great product.
I would not say ease of use and integration are features to criticize because ease of use is something taken on by the user, so it is actually considerable. Integration, however, is something which admins configure with StrongDM, and in that area, it can be improved. Sometimes, if there is an architecture or infrastructure that is more complex, it would take extra time for integrations. I think something can be improved in AI, such as using AI for certain functions within StrongDM. Enhancing features with AI can help StrongDM grow significantly in its domain. I would say that reports can now be generated from the data StrongDM stores. For instance, if one user accessed a database or Kubernetes cluster a long time ago and is not using it now, applying intelligence to that data can better inform the admin. The system could indicate that a particular user has accessed that resource in the past but is not using it currently. Better addressing least privilege access by removing unnecessary access would be valuable. Those AI capabilities that provide insights to admins regarding access could be very helpful. I have already mentioned that AI capabilities can be improved, and the remaining aspects such as recording queries, sessions, and SSH keys are already being managed well by StrongDM. I believe AI capabilities could be enhanced, and I would also suggest improvement in reporting and dashboard generation with the data available in StrongDM.
I believe StrongDM can improve its initial setup and onboarding experience for larger enterprise environments like Scania, where we have a lot of processes. Integrating different teams, access policies, and existing identity workflows requires substantial planning. Additionally, I think the dashboard customization and reporting could be more flexible for operational teams, though new teams find it manageable. Once the platform is fully integrated, it provides significant value. Apart from the onboarding experience, I would also mention that the templates for enterprise onboarding and policy setup could benefit from innovative thinking tailored to organizations managing large AWS and Kubernetes workloads. Enhanced customization in dashboards and reporting would further ease operations and provide better insights.
In StrongDM, I think the installation was hard, and they want to be more flexible in the initial setup. I think they want to add more features like traditional PAM. It is difficult to find documentation or materials to review how it works, and there is less product material available in the market.
StrongDM regularly requires patches and maintenance, but I think that's a good question for the PAM architects in our organization. If you guys could offer only a cloud-native solution, you would likely cater to different organizations. That could grow the product more.
It would be beneficial to have better control and alignment between frequent updates and improved communication regarding possible negative effects on existing customer bases. Also, documentation sometimes lags behind the new features which can be a problem.
We started to use it as a client-side or split tunnel VPN. We are unable to overwrite the endpoints and direct traffic that way, but that's a technical limitation, and I understand why it's there.