Akeyless Zero-Knowledge Secrets Management Platform

The main use case for Akeyless Secrets Management is centralized access control, which is one key aspect that I am looking forward to, but it is still in the gray area. Mostly, we are looking forward to the features of Akeyless Secrets Management, which includes revenue optimization. As Azure Key Vault is a little expensive for us, we are thinking of shifting our infrastructure to some other platform, focusing on risk mitigation, cost reduction, and revenue optimization.

The security system is good, but as we are in the research phase, we need to dive in a little more to answer how Akeyless Secrets Management has positively impacted our organization.

The ideal risk or the ideal KPI that I am looking forward to that Akeyless Secrets Management can solve is identifying the right issues, such as OT boundaries and the standard privilege ratio, which represents the percentage of static hard-coded credentials versus ephemeral just-in-time tokens used at Level 3.5 DMZ. Target outcomes should ideally be 0% static credentials and 100% dynamic token utilization for telemetry extraction. Additionally, I suggest aiming for a reduced meantime to remediate credential exposure, with cost reduction as the main focus.

Akeyless Secrets Management is actually a nice tool because it also integrates zero-knowledge security and it is a JIT access which replaces the standing privileges and hardcoded credentials with identity-based ephemeral secrets generated exclusively at runtime, which is really amazing for us. As we are a global company, it also provides a centralized lifecycle automation, allowing us to orchestrate the creation, rotation, and revocation of both static and dynamic secrets across multiple platforms that we use such as global systems like LN, Fabric, GCP, etc. We can also integrate it with the deployment pipeline.

The best features that Akeyless Secrets Management offers include management boundary security, which is a problem that Akeyless Secrets Management can solve. In terms of different use cases, one is cost reduction, and there is risk elimination and mitigation, particularly in eliminating static credentials at the model perimeter. Another use case involves gateways connecting to Valmet DNA process networks and Valmet industrial network by enforcing JIT ephemeral access tokens, which is one of the best use cases that Akeyless Secrets Management has. We are mostly focusing on the risk mitigation part to integrate Akeyless Secrets Management into Valmet infrastructure.

Currently, we are still in a research phase, and we have not completely used the JIT access token feature, but my research indicates that it can be a great game changer for improving our security at Valmet. JIT access within Valmet security enforces zero-trust boundaries between IT and OT systems by dynamically provisioning least-privileged credentials exclusively for the duration of an authorized telemetry extraction or maintenance task, completely eliminating the attack surface of standard privileges.

Mostly, it is more of automated injection and execution that we are looking forward to. Instantaneous revocation, which occurs upon task completion or lapse of a strict time to live window of 15 minutes, is where the secret platform automatically destroys the token and revokes access to the Valmet endpoint. I see that as a great example for integration with Valmet.

Akeyless Secrets Management can be improved by focusing on strategic areas of product enhancements to elevate it from a robust operational tool to a frictionless enterprise standard product. Development must prioritize maturity in release governance, user interface intuitiveness, and developer documentation. Addressing these areas will directly reduce friction and accelerate enterprise-wide adoption.

More documentation should be included in the governance and quality assurance aspects because properly organized documents create a significant impact on the product.

Akeyless Secrets Management could improve its zero-knowledge cryptography capabilities, as the documentation is still lacking. The use of distributed fragments cryptography can be enhanced by splitting encryption key fragments between Valmet's local gateways and Akeyless Secrets Management cloud. This would ensure that the cloud providers maintain mathematically inaccessible telemetry to third parties, presenting a significant improvement in zero-knowledge cryptography.

I have been using Akeyless Secrets Management for a couple of weeks.

In my experience, Akeyless Secrets Management is stable so far, and I have not found any hard points that I could say are negative. Definitely, it is a great tool.

As a global organization, Akeyless Secrets Management needs to gain trust. Currently, we are still in a testing phase, and I cannot comment directly on scalability, but Akeyless Secrets Management needs to perform well in this regard.

I have not interacted with Akeyless Secrets Management's customer support yet, as it has been an early phase and still in research, so I do not have experience to share.

Due to cost considerations, we are switching from Azure to Akeyless Secrets Management, but it is still in the gray area.

We are using a private cloud, as we are a direct gold partner with Microsoft. We have the VDL architecture performed, and we are integrating Akeyless Secrets Management with our VDL, following a hybrid SaaS architecture, which is in a cloud control plane, along with some on-premises API gateways.

It is very early to determine a return on investment as we are in the testing phase, but I believe we will see benefits.

Regarding pricing, setup cost, and licensing for Akeyless Secrets Management, if the product is excellent, cost usually is not a problem. Most of the time, if the product is nice, the cost can be optimized. I would say it is in a good format and is not much for the service that Akeyless Secrets Management is actually providing.

Before choosing Akeyless Secrets Management, we evaluated other options, including Azure Key Vault, which we have been using. Akeyless Secrets Management is the second option we are working on while looking into other players as well.

Akeyless Secrets Management has strong capabilities in risk management and revenue optimization, and it is a great tool worth considering. Currently, the adoption is in the early stage, and there are other players in the key field of secrets management systems such as Azure Key Vault and AWS. Therefore, Akeyless Secrets Management still needs to build trust, but I am looking forward to its growth.

Regarding Akeyless Secrets Management's AI capabilities, it is stable right now and is working on a zero-knowledge sharing infrastructure and model.

Currently, we have not used it on our Valmet data yet, so it is still in the gray area. However, I have read that it is performing better for other users, and once we test it out, I can provide more feedback.

Currently, we are using Microsoft Fabric as our cloud provider.

If you are looking into using Akeyless Secrets Management, I would suggest focusing on their zero-engagement cryptography tool and cost optimization. I would rate Akeyless Secrets Management a six out of ten.

Akeyless Secrets Management is used to store secrets such as database credentials and TransUnion certificates for the production environment. For example, a team stores PostgreSQL usernames and passwords in Akeyless instead of in application.properties. A Spring Boot application authenticates to Akeyless at startup, retrieves the credentials at runtime, and uses them to connect to the database. Regarding certificates, a team stores TLS certificates and private keys securely in Akeyless. Application services retrieve them when needed, and administrators can rotate certificates centrally instead of manually replacing them on every server.

Akeyless Secrets Management has positively impacted our organization because it has improved security through simpler credential rotation policies. Passwords, API keys, and certificates can be updated centrally without manually changing every application. This has resulted in better access control through role-based permissions and enhanced auditability.

Specific outcomes include the reduction in secret rotation time from hours to minutes after automating rotation. Fewer secrets are now stored in source code or configuration repositories after migration to centralized secret management, which is very important for our company. Manual effort has been reduced significantly because of this. New applications' secrets are managed centrally now. Incident response is very fast because speed is everything in this context.

Akeyless Secrets Management offers centralized secret management that stores API keys, passwords, certificates, and SSH keys. It provides dynamic and rotated secrets, role-based access control that lets administrators define who or what can access specific secrets, and a zero-knowledge architecture that uses distributed fragments cryptography design. It also offers support for services like Kubernetes.

The feature I rely on the most in my daily work is centralized secret management, as it is often considered the core capability because it reduces the need to store credentials across multiple applications. Role-based access control is also very valuable and important in larger organizations, and because our organization is growing, it is very helpful. Dynamic secret storing is very valuable to me, and Kubernetes support is essential for our operations.

Akeyless Secrets Management could be improved in several areas. The initial setup was quite difficult for me. The documentation and tutorials must include end-to-end examples for Kubernetes and CI/CD integrations in general. The UI/UX can be enhanced, and they should offer clear pricing and feature comparisons between different service tiers.

Onboarding and documentation should be clearer for first-time users. Integration examples for different tools, such as integrating Kubernetes and CI/CD pipelines in general, can be improved.

I have been using Akeyless Secrets Management for quite some time now in my company.

Akeyless Secrets Management is very stable.

Akeyless Secrets Management supports thousands of applications, users, and secrets, which demonstrates that it is highly scalable. It provides support for multi-cloud and hybrid deployments as well.

I do not think we have used customer support for Akeyless Secrets Management, as if used by anyone, it will be the higher authorities in our company. I have not had a single issue with Akeyless Secrets Management.

As far as I can remember regarding Akeyless Secrets Management, I do not think we were using anything else before, though it may have been Google Secret Manager before we changed it.

There were other options that the company was looking forward to considering, such as AWS Secrets Manager. We were using Google Secret Manager as far as I can remember a couple of years back, but we chose Akeyless Secrets Management instead.

Common metrics regarding return on investment with Akeyless Secrets Management include time saved because of its secret rotation policies. Operational effort has been reduced as it automated credential management. I have hardly seen any security incidents, and overall it has been very beneficial.

The advice that I would personally give regarding Akeyless Secrets Management is that before adopting any secrets management platform, you should define what your security and compliance requirements are. Identify your cloud environments and the DevOps tools that you are integrating with. Evaluate ease of deployment, pricing, rotation policies, access controls, logging, integrations for Kubernetes, and scalability. My overall rating for this product is eight out of ten.