Akeyless Secrets Management

My main use case for Akeyless Secrets Management  is using the static and dynamic secrets functionality. Rather than using static keys within cloud platforms such as AWS  or GCP, we use Akeyless Secrets Management  to generate short-lived access credentials to then authenticate to cloud environments.

We also use Akeyless Secrets Management when integrating with third-party tools. When an integration needs to occur between one of our public clouds and a third-party vendor, you would sometimes have to put in a static key on the third-party tool's side. Rather than using a JSON key created directly on a cloud platform, we create it via Akeyless Secrets Management and then enable automatic rotation and upload that onto the third-party tool provider website. This applies to both code-based and UI-based use cases.

I appreciate that Akeyless Secrets Management offers the ability for secrets to be automatically rotated. When interacting with it via code, Akeyless Secrets Management automatically rotates secrets to increase security. Additionally, I understand that Akeyless Secrets Management does not store the entire secret in one string on their side. The secret is split across different servers, which is extremely secure.

The rotation of secrets aspect of Akeyless Secrets Management is excellent. It allows for much higher security and there is a great reduction in potential exploits or attacks to our infrastructure because it is very difficult to get compromised credentials when they rotate so regularly. Akeyless Secrets Management splitting secrets in terms of their storage also means that even if an attacker were to infiltrate Akeyless Secrets Management's infrastructure, it would be extremely difficult if not impossible to get the full credentials. This security is excellent for us and also for our customers.

Using Akeyless Secrets Management has greatly increased our security posture, which is excellent and definitely reduces the risk of potential attacks or exploits. From a security-specific perspective, this is excellent when looking at things like data security. It has improved our data security posture. In terms of financial governance, if we were to be exploited in cloud environments, costs can very quickly ramp up. Using Akeyless Secrets Management actually saves potential costs as well.

I do not believe there are any improvements needed for Akeyless Secrets Management. It works excellently for what it aims to do. The UI on Akeyless Secrets Management is also very easy to use, which is important because engineers across a business would use this. It is not just one team that uses it; everyone would use it. Akeyless Secrets Management achieves its aims perfectly.

I have been using Akeyless Secrets Management for two years.

Akeyless Secrets Management was not purchased through the AWS Marketplace . It was purchased directly with the vendor, but it interacts with AWS  because it links with the AWS cloud.

I would recommend others to use Akeyless Secrets Management. It is a brilliant security platform. It is very easy to use. It does exactly what it says it should. I would highly recommend people to use it.

I would say the risk reduction of the compromise of long-lived static credentials is over fifty percent, which is excellent because if every static credential is created through Akeyless Secrets Management, it greatly reduces the risk. Arguably it would be somewhere between fifty to ninety-nine percent.

I have given this product a rating of ten out of ten.