IAM Identity and Access Management

IAM , IdM , IdAM - Identity and Access Management

Identity management (also called IdM, sometimes IDM, IdAM or IAM) is a set of approaches, practices, technologies and special software tools for managing user credentials, access control and management systems (ACS), in order to improve the security and performance of information systems while simultaneously reducing costs, optimizing downtime and reducing the number of repetitive tasks.

It addresses the need to ensure proper access to resources in increasingly heterogeneous technology environments and to meet increasingly strict compliance requirements.

The terms «identity management» (IdM) and «identity and access management» (IAM) are used interchangeably in the field of identity access management.

Identity management systems, products, applications and platforms manage identifying and auxiliary data about entities, which include individuals, computer hardware and software applications.

IdM covers such issues as how users obtain an identity, the roles and, sometimes, the permissions that the identity grants, the protection of this identity and the technologies supporting that protection (for example, network protocols, digital certificates, passwords, etc.).

wiki

AWS

IAM is the service responsible for tracking identity data and access in a system.

On AWS it is implemented through the service of the same name IAM . Access is managed using IAM policies, which set the access boundaries for agents in AWS.

An IAM policy has three main components:

In the sentence «John Doe was not allowed to make a POST request to the DB on us-west-2:ABC… »

John Doe is the principal.

The POST request is the action

The database on us-west-2 is the resource.

Applying the zero trust model to IAM means adopting the principle of least privilege . This means that each agent should have only the minimum permissions required to perform its function.

In IAM, policies can be applied to an AWS principal or an AWS resource.

Policies associated with a principal are called identity-based policies (identity-based policies).

Policies associated with a resource are called resource-based policies resource based-policies.

Note that only some services (for example, S3, KMS, SES) have resource policies.

Whether a subject has permission to perform an action on a specific resource depends on whether the subject's identity policy allows it and whether the resource policy (if one exists) forbids it.

Note that this is a significant simplification of the IAM permissions model. There are many additional policy types that affect whether access can be granted. They can include permissions boundaries, service control policies of an organization, access control lists and session policies. These additional policy types are beyond the scope of this course. More detailed information about them can be found in the further reading section of this module.

Summary

Article author: Andrei Olegovich