Akeyless Secrets Management

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.

My main use case for Akeyless Secrets Management  is to manage the credentials that we use in our application and make them available from the Kubernetes  pods, and also whenever we need to run the application locally, we can grab them and update them as needed.

A specific example of how I use Akeyless Secrets Management  in my day-to-day work is that we store secrets such as database passwords. When we need to connect to a database, we need the secret to be stored somewhere secure. We store them in Akeyless Secrets Management, and we run a sidecar container that can inject those secrets into the pod that we are running on the environment, which is an Azure  Kubernetes  pod.

This is the primary use case for Akeyless Secrets Management.

Akeyless Secrets Management offers really nice access controls where we can provide access to somebody who can update and somebody who can just view. That way, we can have proper control on the access and what anybody can do. In our scenario, we usually have access to only the leads to update the secrets, and the junior developers that want to grab them can do so using just the view-only permissions.

The access control feature has made things easier for my team and organization as it helped get the junior developers up to speed by having the right access and just having them view rather than be able to update. In that way, we can manage effectively, and nobody would update the secret without lead permissions. They would also probably use them in the right way. We have an audit feature as well that tracks who updated what.

Akeyless Secrets Management has positively impacted my organization as it helped store our secrets in a right way, in a proper controlled way where you can view, update, and at the same time, it helps in updating the passwords very effectively in the cloud running environment.

I do not have any features that I can think of for improvement. Akeyless Secrets Management is pretty great, and I would suggest it to anybody who is in the tech world and needing to manage the secrets effectively.

I have been using Akeyless Secrets Management for about four years now.

Since using Akeyless Secrets Management, I can share that it definitely improved compliance where we used to save those passwords in a different way, such as in Jenkins  credentials or somewhere in SharePoint , and we had some of the secrets saved within the GitHub  repository, which is basically out of compliance. We now effectively manage them using Akeyless Secrets Management, and we have also achieved compliance.

Akeyless Secrets Management is pretty secured with the single sign-on capability that it has. It is seamlessly integrated with any identity management system. I have no insight regarding AI capabilities of Akeyless Secrets Management.

My advice to others looking into using Akeyless Secrets Management is to best utilize the capabilities that it has, which is pretty useful. Make  sure to have the right access controls for all the team members and ensure to give the timeline that it can update to your own pod by running it as a sidecar container. I rate this product a 10 out of 10.