Files on Windows Server are only as secure as their permissions. Thus, it is essential to know that Windows Server 2008 R2 does not give the Everyone group full control over NTFS-level and share-level. Additionally, important system files and directories are secured to prevent unauthorized access. This is a definite improvement over previous versions of Windows Server, but a solid understanding of file-level security is still important to fully ensure the security of files on Windows Server.
Understanding NT File System (NTFS) Security
Windows Server 2008 R2 ships with the latest revision of NTFS (NT File System). Each object which is referenced in NTFS, including files and folders, is marked by an ACE (access control entry) that physically limits the users that can access a resource. NTFS permissions use this concept to control the read, write, and other access type permissions on files. File servers should avail of NTFS-level permissions, and all directories should have their file-level permissions examined to ascertain if there are holes in the NTFS permission set. Modifying NTFS permissions in Windows Server 2008 R2 is a simple process; simply follow the below steps:
- Right-click the file or folder to which the security will be applied, and select Properties.
- Click the Security tab.
- Click Advanced.
- Click Change Permissions .
- Uncheck Include Inheritable Permissions from This Object’s Parent .
- When prompted about the use of parent permissions click Remove.
- When in the Advanced dialog box, click Add to grant access to the users and/or groups who require access to the files or folders.
- Check Replace All Child Object Permissions with Inheritable Permissions from This Object checkbox. Click OK.
- When prompted regarding replacing security on child objects, hit Yes to replace the child object security.
- Click OK, and finally click OK again to close Properties.
Share-Level Security Versus NTFS Security
Previous versions of Windows Server security used share-level permissions that were independently set. Continues…