What happens when IAM is not aligned with PAM?
When identities originate within a domain or network, mapping privileges initially to a user and/or role is usually standard and easy to perform. However, as the perimeter expands and new Operating Systems (OSes), applications, and infrastructures are introduced, the problem becomes much more complicated. Identities take on many forms, there’s the traditional human identity, which is associated with users. Non-Human identities can take forms such as services, systems, SSH keys, API keys, IoT devices, and many more.
The challenge is mapping an identity that accesses endpoints, servers, applications that span across traditional data centers, cloud infrastructures, and SaaS-based solutions
Typically, organizations will implement controls that govern both user and service account identities as a fundamental practice. However, where the challenge exists is mapping an identity that accesses endpoints, servers, and applications that span across traditional data centers, cloud infrastructures, and SaaS-based solutions.
Single Sign-On (SSO) has made this challenge a lot easier, but implementing SSO only addresses part of the problem. SSO is traditionally associated with human identity. SSO does not provide any form of privilege management after authentication and authorization.
Role-based access controls govern what the user can do once access is granted. Also, what happens when the identity isn’t associated with a human?
Endpoints, servers, and applications now use services to access other systems and use different types of identities to authenticate. These non-human identities must be governed and audited the same way human identities are. This requires demonstrating that machine identities are also part of your Privileged Access Management program to be compliant.