Everybody in this video we're going to be going over managing users and groups.
Now what I've done is I've pre-built a relatively common flow.
Now this can be dramatic dramatically different between organizations.
However in this particular case we're just going to hit over a basic overview of what something might
look like.
So we have our our enterprise RIGHT HERE SO RIGHT TEAM nation.
Now in this case we've got our group separated.
We've got H.R. security in NJ.
So if we take a look at a chart we can see the remember we have four members here and security.
We've also got four different members and we have four different members.
Perfect.
Now what we have here after this is location.
So we have Mountain View and London.
So we go ahead and open each one of these.
You can see that we have a cha security and H.R. security NJ in each location.
So we can see an H.R. in Mountain View we have Brenda and Taylor.
And then in London we have succession correct.
Now it's common to separate things out by org.
So an org is like security org engineering org H.R. and it's also common to separate it based on location.
Now in some places they might group the users together by org but not by location and just tag the at
the location attribute or the address attribute.
On the user to match that particular office location which is completely fine just giving you a common
structure of how it might look like.
Now I know we've never we didn't create any groups yet right.
So if we go into our groups we've got a new group I kind of want to go over this pretty quickly.
So we want to make a admins group.
Right or a sysadmins group.
Now the pre 2000 Windows 2000 name we can just let it pre fill in this particular case we're going to
use a security group type and we're going to have a global we're going to be.
I'm not going to talk about these specifically.
Go ahead and take a quick google search on the difference between the scope and the type.
So we create this group.
We see it here.
It has nobody.
So it's not a member of anythings.
But let's say we have someone from the security team so Brad is a sysadmin.
So if we get right click on Brad.
We click Add to group.
We can do this admin and that's it.
So now if we look into Brad there and he's a member of Security Group sysadmins and the domain users
however sysadmins might need domain admin access.
So let's say you can even add to a group you can add a group to a group new domain admins.
So now anybody in this group.
So Brad is also a domain admin.
Now this is something useful to understand because with users with tools like bloodhound they can look
for these type of ties.
So it can know that hey I'm logged in as an administrator on this local machine that's connected to
an A.D. and this user Brad is logged in and I can steal his token because he's part of the user part
of the group security or sysadmins which is part of the domain admins group.
So now you have a full path to do to domain admin just by compromising a single non domain admin user.
And this can even go even further such as you know maybe Brad wasn't part of the sysadmin group or let's
say we were looking at.
Let's see.
John So we're looking at John.
We saw John was logged in locally we grabbed his hashes but he also can log into let's say server X
and server X happens to have Brad logged in at the same time.
So if you log in as John he is you should already be an admin on that machine.
So now you gain the token for Brad and then you use Brad to escalate all the way to domain admin.
So this is stuff that bloodhound will help you find very useful piece of tooling.
So definitely take a look at that.
If you have a little bit we're going to be we are going to have a whole video dedicated to just that
specific tool.
It's very powerful.
It's very useful so this has been pretty much it for the users and groups play around with they create
your own structure see what see what looks good and see what doesn't.
If you have any issues shoot it over to the Facebook group.