asked on
shares and risks
If you have a share on say a SQL server that is exposed to the everyone or domain users group, but doesnt contain any sensitive/important data - is there any risk? Our admin says not - I wasnt sure aside from the confidentiality angle, if theres any other risks with sharing a directory to the whole network - or what mischevious acts someone could get up to if they spotted it? data security is the biggest concern usually in this type of finding, but as theres no sensitive data on there - I cant see any real issue?
Microsoft Server OSWindows Server 2003Windows Server 2008
Last Comment
Dirk Mare
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
both share and NTFS access to everyone. Only read and execute permissions.
Like I said everyone will be able to Open and Read any document that gets saved.
If user are aware of this and it is what they want it shouldn't be a problem.
I would recommend creating folders for the users that are requesting this and set permission according to that.
Then HR has Full access to their folder and not to the finance department folder.
If user are aware of this and it is what they want it shouldn't be a problem.
I would recommend creating folders for the users that are requesting this and set permission according to that.
Then HR has Full access to their folder and not to the finance department folder.
ASKER
But apart from access to files they should have access to (which as per the question isnt a concern as its meaningless irrelevant data) - there are no other risks to the server in the case of an everyone share.
No - giving everyone full control on the folders and files lets them do everything with those files and folders - including create and delete - but that does not give them any other permissions - so they can't create and delete users for example.
Sql servers normally dont have a lot of storage so if its large files and files that get access it a lot it could cause performance issues or it will fill up the drives with data
ASKER
do shares not typically have restrictions? i.e. can you have 5 shares for one drive, and put a quote on how much until that share is "full", or could you potentially use 99% of the drives storage just by filling one share - as non of them are subject to quotas, i.e. all come out of the same storage chunk.
It depends how the quotas are setup but yes you can have storage quitas setup for the shares