The DevOps movement has taken organizations by storm. The move to build automation, and continuous integration and deployment, allows companies to be more agile, but security must still be paramount.
Today, developers leverage automation tools, use configuration/infrastructure as code and deploy solutions via orchestration frameworks instead of traditional IT infrastructure. This speed, flexibility and agility is great, but all of this DevOps innovation requires that this critical IP to remain carefully guarded.
DevOps secrets have different characteristics than privileged accounts. Treating them with the same old PAM approach doesn’t work. It prevents developers from using their favorite DevOps tools, and causes friction, and can result in vulnerabilities and compliance issues.