Identity and Access Management (IAM) is a framework of policies, technologies, and controls that governs how organizations verify who users are and what resources they can access. It spans authentication protocols, authorization systems, and the full account lifecycle from provisioning to deprovisioning.
Identity & Access Management
The name really does say it all. Identity, which is who you are, proving that who you are. And then access management, what do you have access to. These tickets do represent some systems — not all systems, but some systems — where, once you prove your identity, you're given certain tokens that you're allowed to log into certain resources from.
But really, what is it? IAM is a framework. It consists of policies, standards, procedures, guidelines, controls, technology, services and protocols. It's really how you implement this idea of identity and access management. Each company is going to have a little bit different view into this and a little different setup into this, but it's the overall picture of how your company and organization approaches identifying people and the access that they have.
Identity can come in lots of different forms. A lot of times we use usernames to identify people, but it could come in the form of a certificate, it could come in the form of biometrics, it could come in the form of some sort of smart card, it could come in as a one-time password — something, when you're trying to log into a system, that you are sent through email or through SMS or through some other means, some sort of code for you to log into that system.
So, anything that will identify who you are, we call that authentication. When you take who you are, your ID, and some sort of verification, then you become authenticated. That is authentication.
There are quite a few authentication protocols that help with this process. PAP, CHAP and EAP are examples of those, and EAP is one of the most prevalent ones that are out there. These are really more associated with point-to-point protocols, although something like EAP gets incorporated with a lot of other types of protocols. So we take this protocol and we incorporate it into other protocols, and so it really gets used a lot.
Then there's Kerberos, TACACS, RADIUS, Diameter and LDAP. These are more protocols that you would use within your network. And then we have SAML, OAuth and OpenID, which are some more recent protocols that we use with web applications.
Once you are authenticated with a system and are allowed onto a system, that doesn't mean that you have access to all the resources of that system. So there's an authorization part that happens to this as well. There's an access management part of this.
So what do you have access to once you're on the system? It could be certain computers that you have access to, it could be certain networks, it could be certain servers, certain data, certain keys, certain types of documents. So, what are you authorized to view once you're on that network, once you're within the system?
Identity and access management is really this holistic view though. It's not just the systems you're logging onto and how you're managing it, but it also takes this broader scope of even how do you manage your accounts.
When somebody starts at your company, you have this provisioning process where they are provisioned an account and they're given access to certain things. Once they are given access to it, there's this maintenance that happens, and you have to do some change management if they change positions. So we sit there and manage those accounts as things change, so that way we make sure that we don't give them access to systems that they don't necessarily need access to at any given time. And then we go through a de-provisioning process when that person leaves. Then we have to terminate the account and bring it down, so we go through this process of decommissioning or de-provisioning resources from that account.
I like to think of IAM, identity and access management, as this big umbrella of how you approach things and how you implement things from a company or organization wide standpoint. So it really has to do with that identity part and what you have access to, but there are parts of it that are not just a technical way of looking at things — there are things like account life cycle and how you provision and de-provision those accounts.
TechKnowSurge builds IT and cybersecurity professionals through hands-on, concept-first training built around real understanding — not memorization. Free interactive tools, structured programs, and 25+ years of real-world experience, all in one place.
Explore free tools and programs →