In order to maintain proper access controls, it’s crucial to understand what every entity on
an access control list (ACL) represents, including the implicit identities that are built into a Windows environment.
There are a lot of built-in accounts with obscure names and vague descriptions, so it can be confusing. One question I often get is: “What is the difference between the
Everyone group and
The Bottom Line
Authenticated Users encompasses all users who have logged in with a username and password.
Everyone encompasses all users who have logged in with a password as well as built-in, non-password protected accounts such as
A Bit More Detail
If the above descriptions were a tad oversimplified for you, here is some more detail.
The Authenticated Users group includes all users whose identities were authenticated when they logged on. This includes local user accounts as well as all domain user accounts from trusted domains.
Everyone group includes all members of the
Authenticated Users group as well as the built-in Guest account, and several other built-in security accounts like
SERVICE, LOCAL_SERVICE, NETWORK_SERVICE, and others.
Guest account is a built-in account on a Windows system that is disabled by default. If enabled, it allows anyone to login without a password.
Contrary to popular belief, anyone who is logged in anonymously—that is, they did not authenticate—will NOT be included in the
Everyone group. This used to be the case, but was changed as of Windows 2003 and Windows XP (SP2).
When it comes to permissions, one critical question we need to be able to answer is: which humans have access to a particular resource?
Most of the time when you’re inspecting permissions on a given resource in Windows you’re not dealing with humans (this is actually a best practice); rather, you’re dealing with groups, some of which are built-in implicit identities with ambiguous names. As a result, we often have to do quite a bit of digging to get what we need.
With Varonis DatAdvantage, you’re only ever one click away from seeing which humans have access to a given resource. So when your CEO says, “Who has access to ‘Trade Secrets.doc’?” you can respond with a meaningful, actionable answer instead of going on a scavenger hunt.