|
|||||||||||
|
RE: Any way to remove ADMIN$ only?
From: David Vincent <david.vincent(at)mightyoaks.com>
Date: Thu Nov 07 2002 - 11:51:25 EST
http://www.google.ca/search?q=site%3Amicrosoft.com+best+practices&ie=UTF-8&o e=UTF-8&hl=en&meta= ..for a quick jaunt through google. speaking as a graduate of microsoft's mcse program and having read more than my share of their corproate propaganda, let me tell you there was page after page after page, every section had a bit devoted to "best practices". a lot of it was quit good stuff to know (esp. if you were a newbie) like the wisdom of setting up a DMZ on your network. but they also had page after page of best practices for setting up their services (DNS, SMTP, etc.), often you'll find they want you to do it one way and someone like the NSA want you do to it another way for security. eventually the admin has to decide for themselves what they want and what is the best way to get there. that's my $0.02 -d
-----Original Message-----
Could this be elaborated more on the list by others? I do not recall any conversations about the practice of which is the "best practice" or "ideal" method of setting permissions between share level and file level within the past year and a half or so that I've begun monitoring the list. Perhaps its a good time to bring the subject up?
-----Original Message-----
The best practice is in fact to use default (Everyone=Full) share permissions and to set NTFS security on all drives (with inheritance for 2K and newer systems running NTFS 5 or greater). Share permissions should really only be used when absolutely necessary, such as on FAT volumes where ACE's cannot be applied. Conflicts between share and NTFS perms always cause headaches down the road, and NTFS perms secure the files and directories for locally logged on users as well. If you are sharing C and D, of which one is the system drive, how will removing the admin$ share (winnt) make the system any more secure, if the drive it resides on is shared out? NTFS permissions seem like a more comprehensive solution. The presence of any of the administrative shares is a security hole, regardless.
-----Original Message-----
The only problem with using "net share" to create shares is that it applies default permissions to those shares it creates. These include "Everyone=Full"; obviously not an ideal scenario, especially given the default security of Windows drives (Everyone=Full). I've written a script that will create shares that only allow those accounts listed in the local server's administrator's group to have access to the share you choose to create. http://isatools.org/createshare.zip
The burden of proof is not satisfied by a lack of evidence to the contrary..
-----Original Message-----
write a script that will launch each time upon machine bootup that 'unshares' that share. 'net share admin$ /delete'
I don't know of any registry setting that will remove only that share
and
Understand also that anyone with admin privileges to that machine can recreate that share at any time.
At 01:11 PM 11/4/2002 -0500, Palumbo, Dave (Factiva) wrote:
>to accomplish this? If this is documented, please forgive me....but I
This archive was generated by hypermail 2.1.8 : Wed Aug 23 2006 - 14:01:24 EDT |
||||||||||
|
|||||||||||