Subfolder Folder Permissions - Everyone Group

I have a folder (Folder B) that I am trying to ensure is restricted to authorised employees only.  I’ve been given a screenshot of the folders ACL which shows only a handful of individually listed employees.  I am not on this list but I am able to access the folder.

Looking at the ACL for the folder above (Folder A) this contains the ‘Everyone’ group with Read and Modify permissions for this folder and subfolders.

Can I just confirm that because the Everyone group has permissions listed in Folder A including subfolders, it can fully access Folder B despite it not being explicitly listed in the ACL for Folder B?

If this is the case how can I determine how many user accounts are within the Everyone group, just so I can put this into perspective for management? i.e. Folder B containing sensitive data can potentially be accessed by 8000 employees because of the permission granted to the Everyone Group in Folder A?  Also is there a way to determine if anonymous users are part of the Everyone group?  I’ve read that at around 2008 this was removed from the group but I would like to clarify this.
Who is Participating?
Alex GreenConnect With a Mentor 3rd Line Server SupportCommented:

Go to security, advanced, change permissions and remove inheritable permissions, copy the existing security and then remove what you want.
Lee W, MVPConnect With a Mentor Technology and Business Process AdvisorCommented:
The everyone group is a special group and literally means EVERYONE.

Understanding Group Accounts

Furthermore, whoever set this up:
"I’ve been given a screenshot of the folders ACL which shows only a handful of individually listed employees."

Doesn't understand security.  With RARE exception, NEVER assign users individually to a resource.  Create a group and assign that group.  IDEALLY, the group will be named something logical for what the resource is, but even if it were Group625 it would be better than assigning INDIVIDUALS to the resource.

Indeed, with the exception of user home directories, even when a resource only has ONE user, that one user should be part of a one user group and assigned that way.  Consider that when you need to add or remove users to the resource, you now have to reset permissions on everything when assigning by user.  Depending on the number of files, this can take a while.  Whereas if you assign permissions to a group, you can add and remove users in near an instant and at worst, they only need to log off and back on again to gain access.

The Logon process gets a list of group memberships which doesn't update until the next logon.  So put a user in the "Accounting" group while they are logged on and they won't have access to Accounting until they log off and log on again.
jdc1944Author Commented:
Many thanks for your input.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.