Least Privilege Approach

Video Activity
Join over 3 million cybersecurity professionals advancing their career
Sign up with
Required fields are marked with an *

Already have an account? Sign In »

2 hours 27 minutes
Video Transcription
Welcome back, Toe Intermediate 10 point security course, Andi, In this lesson, I'm going to talk about least privilege approach.
And I'm going to explain what the least privilege of concept is. What are the benefits and how to plan? Implement less privilege in your company.
So first thing about these privilege concept is that is used mostly in government organizations, even some, like Military Day ed in the United States and in some other countries. This is this is a regulation says that this privilege,
ah, principal has to be implemented there.
So let's talk about what it actually is.
It is, ah, concept in which restricts ah, right access rights for users, accounts and computing processes to Onley. Those resource is absolutely required to perform routine, legitimate activities. So what is the? The essence of this privilege concept
is that users don't have admitting privileges on their PC's. This is the first and most important one.
The second thing is that users cannot install programs which automatically makes impossible for viruses toe for, for example, for trojans doing getting sold on on your PC because if under your account nothing can get installed,
then you some mulberry also cannot get installed on your PC
and also Brower browsers run with less privilege.
And even if you follow the recommendations of less privileged to the letter if you don't follow it to the letter, if you apply these greetings, you have achieved probably 95% of what, what the least privileges when it comes to endpoints or PC's.
And in that case, you have significantly increased the overall resilience and security off your endpoints.
So what are the benefits?
According to Horizon Um, research, 85% of vulnerabilities on Windows systems could have been avoided by removing and mean rights to user. So this is what I was talking about just before.
If the user doesn't have any rights, they cannot access some settings in the operating system. Then the process is they run like applications and, uh, installations after installations and stuff like that, they cannot be.
They cannot run
on. And in that way you have reduced
essentially the ability off any kind of malicious code to do damage to the B C.
It s essentially reduces the attack surface
it reduces. As I said, malware, infection and propagation,
um, in improves gives you improved operational performance.
And, um,
also, if you want to um,
yeah, if you have to meet some combat regulatory compliance.
If you have ah, least privileged implemented, it's easier to reach the compliance level and to prove it, Ah,
to whatever it authority has to approve that you have this you that you have reached the compliance level required.
So what are the problems with implementation of Lee's privilege? First of all, it's muting the ranks, so users and please might complain about it
because they will suddenly see that they cannot do some things that have been doing before. Most of the things, if least privileges carefully planned are actually not connected to the work they have to do for in company time. It's there
to make their
let's say, work nicer, easier.
But then communication with people is essential to explain to them. Yeah, OK, these things are very nice, but
it's, uh,
it's a security risk. So some some story like OK, guys, if you don't look your house, that's convenient because you don't have to worry if you're locking if you have to carry the keys for it. But then somebody can break in without any problem and take whatever they want.
So or if you have all the alarm system in our house and you don't don't arm it when you leave the house than what's the point of having it. So some kind of analogy explanation would give them at least the idea. Why are you using it?
Then you'll have the resistance resistance from management because
it's called fear off privileges lost or losing privileges. And basically they think that they won't. They might think that they won't be able to do their job effectively because now,
now that they had done don't have some privileges they had before.
And all of these things can be avoided if you have done that. Detailed planning. Because if you allow the applications to work, if you allow the applications that you have specially designed or installed on every user specie
in the company, they can work and they can allow people to do whatever they want
with their whatever they need to do to to do their job okay with their PC's. Then you have essentially removed the ALS issues that come from people not being happy with their privileges reduced.
But the planning has to be very detailed, careful and has to include unfortunately, no, just I t people. But Aled business verticals in the company, they all have to be included. They all have to explain to whoever is planning the least privilege are running the project, how
they do business. So you have to understand not only the
I d processes in the company, but also business processes. Now, if you have these things all on one place and if you have done the detail planning, you have done a great job, and then you can go and implement the least privilege
eso how you do it. First thing you do is you do privilege old it. So you see who has the right to access. What, um, who? What are the people with the administrator passwords?
The second thing is a force toe. Find a way to remove, admin writes in and points. And of course, you have to have them. Procedures like that stop Management's after that will allow users toe, have the software installed without having and then privileges on a PC.
Oh, there are some things connected to a network like removing all rotor than an access rights. The servers enforced separation off little privileges and implement just in time privileges for some things. For example, if some applications of processes need
administrative privileges for short period of time, then you have to implement the system
to allow these things to happen when they when they're needed.
you have tow. Establish a system off expiration of privileged access. Implement one time use credentials again for some situations in which you need more privileged than you usually do. Um,
then again, on the network you have to limit member. She's for super user role to the minimum number of people
that actually need them.
Because you have people, for example, that are in technical support inside the company that they're allowed to have admitting rights because they need to think or something with BC's or servers
shouldn't be happening. At least then you should implement. They're one time use credentials. If they have to do something. Yeah, they logging, they finish what they do and they look out,
allow individual actions should be traceable. This is very important, especially if you need toe. Prove compliance to some regulatory authority,
and you need finally to have ah, regular reports on access to all privileged accounts and you have toe
verify upon these reports. So, for example, you have seen that some manager has logged into their accounts and 3 a.m.
And they were not overseas on the business trip. Oh, or they were, you know, just home. Then you have to check with that person and say, OK, did you actually along at 3 a.m. To your account?
And if they didn't, then you know that at least there was some. At least you have the notion that there was a bridge. Then you have can take actions like changing passwords is for that account or implementing multilevel authentication or checking just what's happening.
No, it was happening
so as the least privileges. Ah, completely separate topic. I'm not going to go into any more details about it. But, uh, I will just ask you one question to check if you have the learned anything. And the question is how many vulnerabilities can be removed
by implementing light least privilege? When you talk about PC's, of course,
is it 58%? Is it 76% or is it 85%?
The correct answer is, if you remember the first slide, it was 85%.
Okay, so in this video, you have learned about what? The least privilege concept. Our approach is,
uh, what are problems when you have or issues that you have when you want to implement that the concept
and then general guidelines on how to implement it. So you have seen that if you want to do it, you have to make sure that all these things are
there and, uh, plan that there have to be financial harder and people resource is in order to do these things
in next lesson, I'm going to talk about process management when it comes to managing endpoints.
Up Next