Source: devops.com
Using PAM to Support the ‘Sec’ in DevSecOpsCategory: Security, automation
Home » Blogs » DevSecOps » Using PAM to Support the ‘Sec’ in DevSecOps By Tony Goulding on October 22, 20201 CommentDespite its reputation as slow and complex, PAM can be included in the DevOps pipeline effectively
Instead, developers introduce API calls in their code to access a vault programmatically and to check out the password.
This can quickly amount to hundreds, if not thousands, of additional accounts, increasing administrative overhead and increasing the attack surface.
Thus, by using a Delegated Machine Credential, the number of service accounts is reduced to practically zero, closing thousands of potential vulnerabilities.
Instead, developers introduce API calls in their code to access a vault programmatically and to check out the password.
This can quickly amount to hundreds, if not thousands, of additional accounts, increasing administrative overhead and increasing the attack surface.
Thus, by using a Delegated Machine Credential, the number of service accounts is reduced to practically zero, closing thousands of potential vulnerabilities.
Related Articles
Community Partners
DevOps Careers