Secure AD from regular user from querying information?

I've created a standard AD user in my AD environment and discovered that, if I run Powershell with its credentials, or AD explorer, for example, I can query almost anything.
To me that does not seem very secure, and I'm wondering if that's an inherent permission with AD or if I have to manually modify things to prevent it.

So I can open AD explorer and browser all OUs, view groups and their members, etc, all as a Domain User with no extra permissions.

I can run powershell "get-aduser -username -properties * | fl" and get all their AD fields.

Would unchecking allow "Read" permission for Authenticated Users have any adverse effect?
garryshapeAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

David Johnson, CD, MVPOwnerCommented:
if you do that then the user can't login.. the only confidential information that is stored in AD really is the users password and it is not accessible.
0
garryshapeAuthor Commented:
I can just open up Active Directory Users and Computers on a computer that has it installed and browse through it. I'm sure there are ways to prevent access to the software itself, but the fact that permissions exist for a standard user to browse it as well as all properties of AD objects is a bit frightening.

They can view:
Group memberships
Password last set times
Domain Controllers
Custom attributes made that contain sensitive information about users (like pin codes for other authentication systems)

is that the usual setup in AD?

Is setting the Confidential flag on schema attributes the only way to prevent any "Authenticated user" from accessing certain information?
0
David Johnson, CD, MVPOwnerCommented:
removing list objects may be a better idea http://bit.ly/1IKoAHH
confidentiality bit is not all encompassing http://bit.ly/1IKouzK
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Will SzymkowskiSenior Solution ArchitectCommented:
When you have a user on the domain that user does in fact have Read Access to all areas (unless otherwise removed, which i wouldn't recommend).

If you are looking to hide specific attributes from users then you will have to use ADSIEdit and modify the attributes you want to hide. Personally I would not recommend messing around with this.

Take a look at the following link.
http://windowsitpro.com/active-directory/hiding-active-directory-objects-and-attributes

Will.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Active Directory

From novice to tech pro — start learning today.

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.