Re: Default NTFS permissions too liberal on newly created volumes
- From: "Steven L Umbach" <n9rou@xxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sun, 22 Jan 2006 21:24:01 -0600
I can't answer for Microsoft though maybe such decisions were made at a time
when the scales tipped more toward functionality then security and it was up
to users and admins to configure permissions for their needs from there but
it sounds like your users had excessive share permissions. If they only had
read share permissions they would not have been able to create folders. The
Windows 2003 Server Security Guide and the Threats and Countermeasures Guide
are free for those who want to learn how to lock down their operating
systems from baseline with guidance on legacy, enterprise, and high security
scenarios. They are available at the links below. --- Steve
http://www.microsoft.com/technet/security/default.mspx
http://www.microsoft.com/technet/security/prodtech/windowsserver2003/w2003hg/sgch00.mspx
"Mike M" <nospam@xxxxxxxxxx> wrote in message
news:OxMXcj8HGHA.140@xxxxxxxxxxxxxxxxxxxxxxx
> Windows 2003 SP1 server here...
>
> I created a folder called "public" under the z:\ drive, shared it as
> "public", and verified that all users in my department had read-only
> permissions via a certain group. All seemed well until I saw legit data
> folders popping up in this shared folder that was allegedly read-only save
> for the admins. The user was able to create folders and files in the
> public share that was supposed to be read-only!!!
>
> Well...
>
> It seems to me that configuring a secondary volume, named as Drive Z:,
> brings liberal permissions to the root of the drive for the USERS group.
> Drilling down into the advanced security settings window shows 3 separate
> entries for the local-server\USERS group:
>
> --Read & Execute, This folder, subfolders and files
> --Create Folders/Append Data, This folder and subfolders
> --Create Files / Write Data, Subfolders only
>
> I looked at the other servers that we've built and all have the same
> all-too-liberal permission settings for the USERS group. It seems to me
> that USERS can do everything but delete files by default.
>
> Why is Microsoft allowing the USERS group such liberal permissions by
> default? It was a no-brainer to remove the EVERYONE group to tighten
> things up, but this issue seems to make things more difficult to lock-down
> security on file servers. Am I missing something???
>
>
> TIA,
> Mike
>
>
>
.
- References:
- Prev by Date: Default NTFS permissions too liberal on newly created volumes
- Next by Date: DoS
- Previous by thread: Default NTFS permissions too liberal on newly created volumes
- Next by thread: Re: Default NTFS permissions too liberal on newly created volumes
- Index(es):
Relevant Pages
|