ISO 27001 Explained_ 9.2 User Access Management

EDUCATION - NATURE - SOCIETY
6 followers
2 Video Views·May 24, 2025
Comments are disabled for this video.
Hi, my name is Christian Hyatt. I'm the Managing Director for 360, and this is our ISO 27001
Explained Series where we cover all 114 controls in the ISO 27001 Framework.
Today we're going to cover all 9.2 around user access management.
This is one of the more complicated control objectives, so we're going to spend a lot of time
covering on every control, what those controls mean, and then the typical evidence
and things that you might have to do to satisfy specifications.
So on my screen today, on the left-hand side, you'll see that I have the ISO 27001 Standard up.
This is an overview of the 114 controls, and on the right-hand side, I have the ISO 27002 Standard up
that has the detailed implementation guidance for every control in the Framework.
I also have a lot of examples that we'll walk through, that way you'll know exactly what you
might want to provide an auditor and how you might want to satisfy this control for building your own program.
Control Objective 9.2, User Access Management, has six controls.
Like I said earlier, these are fairly complex controls, and there's many layers to each of these controls.
So we'll cover each one of them so that you know what you're doing.
The first control is 9.2.1. It is around user registration and deregistration.
If you watched our previous ISO video around onboarding and onboarding,
this is a continuation of that control.
So when you're thinking about user registration and deregistration, this is how you provision users' access,
and then when they leave the company, how you deprovision access.
So this is going to manifest itself in a couple of ways.
One way is probably an onboarding and offboarding checklist.
So when an employee comes onboard, you provide standard access,
and then when that employee leaves the company, you deprovision that access.
So some of the artifacts that you're going to provide an auditor might include,
I'll show it here on my screen, an employee onboarding checklist and an employee offboarding checklist,
and that might be informing the e-mail, hiring a manager for the checklist to involve their access,
or an offboarding checklist whenever it leaves the company.
You might consider ways to automate some of the speed provisioning.
So, for example, if you're using Active Directory, maybe when they're removed from the HR system,
their accounts are already disabled.
Maybe there's automation around removal of access from SAS applications,
or if you have an identity and access management tool,
you might be able to remove that access in a more systematic way,
or you might be going account by account, removing access one by one.
But that's what this control is about.
It's all about removal and provisioning of access.
Now if we move on to Control 9.2, this is around user access provisioning.
So, again, this is just how do you go about provisioning access.
And the key to that is there needs to be some logic around assigning individuals
only the access that they need to do their job.
So, for example, if you're assigning administrative access,
only a certain group of individuals are going to get access to that.
If you're providing e-mail access, maybe everybody in the company gets access to that.
So the way this manifests itself in the form of an audit artifact is the auditor is going to
kind of spot check some of your systems and want to confirm with you that those access,
the individuals who have access are appropriate based on your judgment,
that no terminated users will have access, or that, for example,
an administrative access is not overly broad.
So this is somewhat judgment based, but you want to have some kind of documentation,
maybe it's a policy or maybe it's kind of a role diagram describing who should have access
to what and what's considered appropriate for your organization.
Control 9.2.3 is management of privileged access rights.
I want to talk about this one a bit because privileged access really translates to something
like administrative access.
And when I'm thinking through administrative access, there's a lot of systems to consider.
So the most logical place to start, if you're thinking about this in terms of layers,
as I talked about in Control 9.1, is what about your network layer?
So if you're using Active Directory, administrative access can be your administrator's group,
system administrators, network administrators, domain administrators,
anything that is considered administrator, how do you access that?
And then if you move down, you can think about database administrators
or maybe system administrators or who has, like in the engineering team,
who has access to source code orchestration tools, who has access to source code,
administrative access to that stuff.
So you're thinking about every layer when it comes to privileged access management, network,
databases, applications, SaaS applications, key business applications,
like your HR system, your accounting system.
Think about all those layers and what does appropriate privileged access look like at each layer
and how do you want to manage that?
Then we get down to Control 9.2.4, which is around management of secret authentication information.
So this is a very difficult control because anything about secrets management,
that could be cryptographic keys, it could be service accounts,
shared user accounts, things like that.
So there's going to be many solutions that you might want to deploy to manage secrets.
Some of the common ones is implementing something like LastPass or Password1,
which is a password management tool to keep all of your organization's administrative accounts.
So, for example, if you have a shared social media account
or if you have a generic administrative account for administering certain systems,
that might all need to go into LastPass.
Or if you have certain individuals in the business,
like your head of IT who holds the keys to the kingdom,
maybe you want to store some of those privileged account credentials in LastPass.
That way if that person leaves the company or something happens
and you have to get access to those key accounts, you have a place to go do that and manage those.
Another thing to think about when you think about management of secret authentication
is management of cryptographic keys.
So some systems, the way that you grant authentication is through a cryptographic key.
Not necessarily a credential.
This is common in engineering to have SSH keys or something similar.
So different tools like AWS has something called KMS, Key Management System.
There's a tool called Dykotic if you want to manage cryptographic keys and secrets management.
So depending on what layer you're looking at,
whether it's a typical username and password that's privileged
or it's a cryptographic key or something else,
there might be different solutions that you want to consider to manage those.
So that would be part of your risk assessment
and kind of your solution selection to manage secrets.
The next control is around 9.2.5, which is the review of user access rights.
So once you've kind of figured out a strategy to manage privileged access,
to manage different systems, manage secrets,
you're going to want to periodically review those accounts
to make sure that no one was inadvertently granted access
or that maybe a terminated user doesn't still have access.
So your approach here will be to inventory all of your key systems
and decide on what frequency that you want to perform the user access review.
User access reviews are typically performed quarterly,
but sometimes they're performed semi-annually.
I think quarterly is the best practice.
And you want to have a process to, one,
generate a list of all the users that have access to a given system.
Two, provide that listing to someone who knows whether someone should have access or not
and have a process that if they identify someone that is not appropriate,
that that is resolved timely.
So an easy example might be you have the accounting department
who has knowledge of who should have access to the accounting system, for example.
But IT might be the one who generated the user access list.
So you'd want to generate that user access list,
provide it to the head of accounting.
The head of accounting will review the user access list
to make sure that there's no users that should be removed
and report that back to IT where IT can then carry out that review by removing users
or updating the list or what have you.
And you'll want to do that for all of your key systems.
So really the first step is deciding what systems you want to review
and which systems are your key systems
and then doing that periodic user access review on those key systems.
Some systems you might review less frequently than others.
So if it's a moderately important system,
maybe you only do that twice a year.
But if it's a mission-critical system
where you can't tolerate any misprovisioning of access,
maybe you want to do that quarterly or even monthly.
So you'll have some decisions to make there,
and you'll want to put a procedure together
to describe how you want to manage user access reviews.
And then the last control in this section is Control 9.2.6,
which is the removal or adjustment of access rights.
And, again, that's going to be removing access when a person no longer needs access.
That could be because they're terminated.
That could be because they've changed jobs.
That could be because maybe you've just granted them temporary access
to carry out their job for a week or so.
So whatever that process is, whether it's submitting a ticket,
whether it's an email kind of thing,
you want to have a formal process
where you're telling people how to adjust rights
and on what frequency they should be adjusting access rights.
So those are the six controls in user access management.
As you can see, there's a lot to it.
There's a lot of solutions that you're going to have to decide through.
You're going to have to write a policy.
You're going to have to decide which systems you care about,
how you want to manage secrets,
how you want to manage administrative access.
You're going to have to come up with a user access review process
and then a user provisioning and deprovisioning process,
all in these six controls.
So this tends to be one of the most effort-intensive control objectives
in the whole framework,
but also one of the highest risk and one of the most important.
So I hope you found this video helpful.
If you liked this series, you can continue watching it,
where we cover all 114 controls.
You can also check us out at risk360.com
to get any questions on how to build out an ISO 27001 program.
Thanks for watching.
