Written by: Mio Kanzaki(Security Analyst (AI))Reviewed by: 千葉圭介Updated
IAM is the mechanism that decides who may do what in the cloud. The name is short for Identity and Access Management, read letter by letter. The NIST glossary defines the related identity management as, in enterprise IT, setting and managing the roles and access permissions of individual users.
How does IAM work?
A building entry card makes it easy to picture. You give employees, contractors, and cleaners each their own card, and decide per person which floors and rooms they may enter. The mechanism that decides whom to hand cards to and how far they can enter, and then reviews it, is IAM.
In the cloud, the holders of cards are not only people. A system also needs permission to act when it calls another system. If the rights a person or a machine holds are too wide, the effect of misuse is large. If they are too narrow, work stops.
The basic shown in CISA's material is to keep the range of access one account holds to the minimum that person needs. It also touches on the procedure of finding over-broad accounts and misconfigurations in a permission audit. It says it is worth considering using a dedicated mechanism for managing cloud permissions and keeping least privilege.
CWE-269 defines as a problem the state in which permissions are not assigned, changed, tracked, and checked correctly. As a result, operations wider than the proper range become possible. The countermeasures are least privilege and separation, in which permission is granted only when several conditions come together.
By type of service, NIST's SP 800-210 sets out the thinking separately for IaaS, PaaS, and SaaS. It also explains that the focus of access control differs by type.
Problems caused by permissions that have grown too wide are set out in IAM over-privilege. What is visible from outside your site can be checked with the free URL check.
Why does IAM matter?
Once someone gets into a cloud admin screen, they can reach site settings and data. What decides the size of damage then is how wide that account's permissions are. In an operation where everyone has administrator rights, one person's leaked password puts the whole at risk.
Even small companies sometimes hand admin screen permissions to a production firm or a contractor. When the person in charge changes or the contract ends, the work of removing the permissions is part of operation. Delete accounts that are not used each time you take stock. To go over your own permissions, contact us.
The idea of keeping permissions narrow also ties into countermeasures against broken access control and privilege escalation. Handling of keys to the admin screen is gathered in secrets management.
Related terms
- Broken access control: a flaw that lets people see data they must not see
- Privilege escalation: an attack that gains higher permissions than intended
- Secrets management: the operation of putting passwords and keys in a dedicated safe to protect them
- Cloud misconfiguration: a state in which wrong public-range or permission settings become a hole
Frequently asked questions
What is the idea of least privilege?
It is the idea of giving only the permissions the work needs. CISA's material asks that the range of access one account holds be kept to the minimum that person needs. CWE-269 also lists following least privilege when granting permissions among its countermeasures.
Isn't it convenient to give everyone administrator rights?
It is convenient, but the damage spreads more easily. If permissions are wider than intended, a hijacked account can do more. CWE-269 explains that if permissions are assigned wrongly, a wider range than intended can be operated.
Next step
Try making a list of who can enter your cloud admin screen and with which permissions. The idea in IAM over-privilege helps in reviewing over-wide permissions. The free URL check shows only what is visible from outside, and for sorting out permissions, contact us.
Frequently asked questions
What is the idea of least privilege?
It is the idea of giving only the permissions the work needs. CISA's material asks that the range of access one account holds be kept to the minimum that person needs. CWE-269 also lists following least privilege when granting permissions among its countermeasures.
Isn't it convenient to give everyone administrator rights?
It is convenient, but the damage spreads more easily. If permissions are wider than intended, a hijacked account can do more. CWE-269 explains that if permissions are assigned wrongly, a wider range than intended can be operated.