19.12.2012 Views

IT Baseline Protection Manual - The Information Warfare Site

IT Baseline Protection Manual - The Information Warfare Site

IT Baseline Protection Manual - The Information Warfare Site

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Safeguard Catalogue - Organisation Remarks<br />

____________________________________________________________________ .........................................<br />

groups on Windows NT workstations and member servers have the right to<br />

share directories and to manage share permissions.<br />

<strong>The</strong> following share permissions are available under Windows NT: "No<br />

Access", "Read", "Change" and "Full Access". <strong>The</strong> actions which the various<br />

share permissions allow are shown in the table below:<br />

No<br />

access<br />

Read<br />

Display subdirectories and file names X<br />

Display file contents and file<br />

attributes<br />

X<br />

Run program X<br />

Switch to a subdirectory X<br />

Create subdirectories and add files X<br />

Modify file attributes X<br />

Delete subdirectories and files X<br />

Change access rights (only relevant<br />

for directories that are located on<br />

NTFS data media)<br />

Transfer ownership (only relevant for<br />

directories that are located on NTFS<br />

data media)<br />

____________________________________________________________________ .........................................<br />

<strong>IT</strong>-<strong>Baseline</strong> <strong>Protection</strong> <strong>Manual</strong>: Oktober 2000<br />

Change Full<br />

access<br />

X X<br />

X X<br />

X X<br />

X X<br />

Shares can only be defined for directories, however, not for files. Share<br />

permissions apply only to accesses made via the network, i.e. they are of no<br />

significance to users who are allowed to work locally on the computer on<br />

which a directory has been shared. Also, share permissions apply only in a<br />

standardised form for all files and subdirectories in a shared directory.<br />

Although it is also possible to share a subdirectory within a shared directory<br />

and in so doing also to set different share permissions, this is a new share and<br />

brings with it the following consequences: when a user is linked to the shared<br />

directory, the share permissions specified for that directory apply to that user<br />

with respect to all files and subdirectories. This is not changed in any way<br />

even if a subdirectory is shared separately. If the user is linked directly to the<br />

subdirectory, however, the share permissions set for the subdirectory apply.<br />

Example: Let us assume the following directory structure:<br />

D:\DEPARTMENT\SECTION. One share is set up with the DEPARTMENT<br />

directory with "Full Access" authorisation and another share with the<br />

SECTION subdirectory with "Read" authorisation. If the user is now<br />

connected to the D:\DEPARTMENT directory, he can read, write to and delete<br />

(among other things) files in that directory but also files in the<br />

D:\DEPARTMENT\SECTION subdirectory. However, if the user sets up a<br />

direct link to the D:\DEPARTMENT\SECTION directory, he can only read the<br />

X<br />

X<br />

X<br />

X<br />

X

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!