Section 23.9. NTFS Permissions: Protecting Your Stuff: All Versions

23.9. NTFS Permissions: Protecting Your Stuff: All Versions

There's one final aspect of user accounts that's worth mentioning: NTFS permissions , a technology that's a core part of Vista's security system. Using this feature, you can specify exactly which co-workers are allowed to open which files and folders on your machine. In fact, you can also specify how much access each person has. You can dictate , for example, that Gomez and Morticia aren't allowed to open your Fourth-Quarter Projections spreadsheet at all, that Fred and Ginger can open it but not make changes, and George and Gracie can both open it and make changes.

Your colleagues will encounter the permissions you've set up like this in two different situations: when tapping into your machine from across the network, or when sitting down at it and logging in using their own names and passwords. In either case, the NTFS permissions you set up protect your files and folders equally well.

Tip: In Chapter 26, you can read about a very similar form of access privileges called share permissions . There's a big difference between share permissions and the NTFS permissions described here, though: share permissions keep people out of your stuff only when they try to access your PC from over the network .Actually, there are other differences, too. NTFS permissions offer more gradations of access, for example. And using NTFS permissions, you can declare individual files not just foldersaccessible or inaccessible to specific co-workers. See page 695 for details.

Using NTFS permissions is most decidedly a power-user technique because of the added complexity it introduces. Entire books have been written on the topic of NTFS permissions alone.

You've been warned .

23.9.1. Setting Up NTFS Permissions

To change the permissions for an NTFS file or folder, you open its Properties dialog box by right-clicking its icon, and then choosing Properties from the shortcut menu. Click the Security tab (Figure 23-15).

Figure 23-15. The Security tab of an NTFS folder's Properties dialog box. If you have any aspirations to be a Windows power user, get used to this dialog box. You're going to see it a lot, because almost every icon on a Windows systemfiles, folders, disks, printershas a Security tab like this one .

23.9.1.1. Step 1: Specify the person

The top of the Security tab lists the people and groups that have been granted or denied permissions to the selected file or folder. When you click a name in the list, the Permissions box at the bottom of the dialog box shows you how much access that person or group has.

The first step in assigning permissions, then, is to click Edit. You see an editable version of the dialog box shown in Figure 23-15.

If the person or group isn't listed, click the Add button to display the Select Users or Groups dialog box, where you can type them in (Figure 23-16).

Figure 23-16. Type the names of the people or groups in the "Enter the object names to select" box at the bottom, trying not to feel depersonalized by Microsoft's reference to you as an "object." If you're adding more than one name, separate them with semicolons. Because remembering exact spellings can be iffy, click Check Names to confirm that these are indeed legitimate account holders. Finally, click OK to insert them into the list on the Security tab .

Tip: Instead of typing in names one at a time, as shown in Figure 23-16, you can also choose them from a list, which lets you avoid spelling mistakes and having to guess at the variations. To do so, click the Advanced button to display an expanded version of the dialog box, and then click Find Now to search for all of the accounts and groups on the computer. Finally, in the resulting list, click the names of the people and groups you want to add (Ctrl-click to select more than one at once). Click OK to add them to the previous dialog box, and click OK again to add the selected users and groups to the Security tab.If you've used Windows 2000, you might wonder why this process is so much more convoluted in Vista than it was in Windows 2000. The answer is: good question!

23.9.1.2. Step 2: Specify the permissions

Once you've added the users and groups you need to the list on the Security tab, you can highlight each one and set permissions for it. You do that by turning on the Allow or Deny checkboxes at the bottom half of the dialog box.

The different degrees of freedom break down as follows (they're listed here from least to most control, even though that's not how they're listed in the dialog box):

List folder contents , available only for folders, means that the selected individuals can see (but not necessarily open) the files and folders inside. That may sound obviousbut believe it or not, if you don't turn on this option, the affected people won't even be able to see what's in this folder. The folder will just appear empty.
Read lets people examine the contents of the file or folder, but not make changes. (They can also examine the permissions settings of these files and foldersthe ones that you're setting up right now.)

Read & execute is a lot like Read, except that it also lets people run any programs they find inside the affected folder. When applied to a folder, furthermore, this permission adds the ability to traverse folders. (Traversing means directly opening inner folders even when you're not allowed to open the outer folder. You might get to an inner folder by double-clicking a shortcut icon, for example, or by typing the folder's path into the Address bar of a window.)

INFREQUENTLY ASKED QUESTION
Allow vs. Deny

Why do I see both Allow and Deny checkboxes in the Permissions dialog box? Isn't not allowing permission the same as denying it?

In this case, no. "Deny" permissions always take precedence over "Allow" permissions.

For example, if somebody has been granted access to a file or folder because he's a member of a group, you can explicitly revoke his permission by using the Deny checkboxes for his account. You've just overridden the group permission, just for him, leaving the rest of the group's permissions intact.

You can also use the Deny checkboxes to override permissions granted by inheritance from a parent folder. For example, you can grant somebody access to the C: drive by sharing it and assigning her Allow permissions to it, but then prevent her from accessing the C:\Program Files folder by sharing that and denying her permission.

Write is like Read, but adds the freedom to make and save changes to the file. When applied to a folder, this permission means that people can create new files and folders inside it.
Modify includes all of the abilities of the Write and Read & Execute levels, plus the ability to delete the file or folder.
Full Control confers complete power over the file or folder. The selected person or group can do anything they like with it, including trashing it or its contents, changing its permissions, taking ownership of it (away from you, if they like), and so on.

Of course, turning on Allow grants that level of freedom to the specified user or group, and turning it off takes away that freedom. (For details on the Deny checkbox, see the box on the facing page.)

Note: If you're not careful, it's entirely possible to "orphan" a file or folder (or even your entire drive) by revoking everyone's permission to it, even your own, making it completely inaccessible by anyone . That's why, before you get too deeply into working with NTFS permissions, you might consider creating an extra user account on your system and granting it Full Control for all of your drives , just in case something goes wrong.

23.9.2. Groups and Permissions

Once you understand the concept of permissions, and you've enjoyed a thorough shudder contemplating the complexity of a network administrator's job (six levels of permissions x thousands of files x thousands of employees = way too many permutations ), one other mystery of Windows will fully snap into focus: the purpose of groups , introduced on page 683.

On those pages, you can read about groups as canned categories, complete with predefined powers over the PC, into which you can put different individuals to save yourself the time of adjusting their permissions and privileges individually. As it turns out, each of the ready-made Vista groups also comes with predefined permissions over the files and folders on your hard drive.

Here, for example, is how the system grants permissions to your Windows folder for the Users and Administrators groups:

	Users	Administrators
Full control		X
Modify		X
Read & execute	X	X
List folder contents	X	X
Read	X	X
Write		X

If you belong to the Users group, you have the List Folder Contents permission, which means that you can see what's in the Windows folder; the Read permission, which means that you can open up anything you find inside; and the Read & Execute permission, which means that you can run programs in that folder (which is essential for Windows Vista itself to run). But people in the Users group aren't allowed to change or delete anything in the Windows folder, or to put anything else inside. Windows Vista is protecting itself against the mischievous and clueless.

Members of the Administrators group have all of those abilities and morethey also have Modify and Write permissions, which let them add new files and folders to the Windows folder (so that, for example, they can install a new software program on the machine).

23.9.3. When Permissions Collide

If you successfully absorbed all this information about permissions, one thing should be clear: people in the Administrators group ought to be able to change or delete any file in your Windows folder. After all, they have the Modify permission, which ought to give them that power.

In fact, they can move or delete anything in any folder in the Windows folder, because the first cardinal rule of NTFS permissions is this:

23.9.3.1. NTFS permissions travel downstream, from outer folders to inner ones

In other words, if you have the Modify and Write permissions to a folder, then you ought to have the same permissions for every file and folder inside it.

But in Windows XP, there was something called the Power Users group. It's been turned off in Vista, but for the sake of illustration, let's say you're part of it. You'd find that you can't, in fact, delete any files or folders in the Windows folder. That's because each of them comes with Modify and Write permissions turned off for Power Users, even though the folder that encloses them has those permissions turned on.

Why would Microsoft go to this trouble? Because it wanted to prevent people in this group from inadvertently changing or deleting important Windows filesand yet it wanted these people to be able to put new files into the Windows folder, so they can install new programs.

This is a perfect example of the second cardinal rule of NTFS permissions:

23.9.3.2. NTFS permissions that have been explicitly applied to a file or folder always override inherited permissions

Here's another example: Suppose your sister, the technical whiz of the household, has given you Read, Write, Modify, Read & Execute, and List Folder Contents permissions to her own Documents folder. Now you can read, change, or delete every file there. But she can still protect an individual document or folder inside her Documents folderthe BirthdayPartyPlans.doc file, for exampleby denying you all permissions to it. You'll be able to open anything else in there, but not that file.

Believe it or not, NTFS permissions get even more complicated, thanks to the third cardinal rule:

23.9.3.3. Permissions accumulate as you burrow downward through subfolders

Now suppose your sister has given you the Read and List Folder Contents permissions to her Documents foldera "look, but don't touch" policy. Thanks to the first cardinal rule, you automatically get the same permissions to every file and folder inside Documents.

Suppose one of these inner folders is called Grocery Lists. If she grants you the Modify and Write permissions to the Grocery Lists folder so you can add items to the shopping list, you end up having Read, Modify, and Write permissions for every file in that folder. Those files have accumulated permissionsthey got the Read permission from Documents, and the Modify and Write permissions from the Grocery Lists folder.

Because these layers of inherited permissions can get dizzyingly complex, Microsoft has prepared for you a little cheat sheet, a dialog box that tells you the bottom line, the net resultthe effective permissions. To see it, follow these steps:

Click the Advanced button on the Security tab .

The Advanced Security Settings dialog box appears.
Click the Effective Permissions tab; click Select .

Now you see the same Select User or Group dialog box you saw earlier when you were creating permissions.

Click the user or group whose effective permissions you want to see, and then click OK .

You now see checkmarks next to the permissions that are in effect, taking into account folder-permission inheritance and all other factors, for the user or group of that particular file or folder (Figure 23-17).

Figure 23-17. The Effective Permissions tab for an NTFS folder. Note that you can't turn these checkboxes on or off; this is a read-only screen that tells you what permissions the selected user or group has for the file or folder. You can't modify the permissions here. You can't tell from this display how these effective permissions have been calculated, either (that is, where the permissions have been inherited from) .