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 />

directories contained in that directory. If restrictions on a subdirectory are<br />

required, as in the above example, this cannot be achieved by means of share<br />

permissions but only with the aid of the NTFS permissions (see S 4.53<br />

Restrictive allocation of access rights to files and directories under Windows<br />

NT).<br />

When a directory located on an NTFS data medium is shared, in addition to<br />

the share permission the NTFS permissions also apply to that directory and to<br />

the files and subdirectories that it contains. In each case, the most restrictive<br />

permission is the one that applies. If, for example, a user possesses the "Read"<br />

share permission for the shared directory, but on the other hand only the<br />

"Display" NTFS permission for the same directory, his access right is<br />

restricted to "Display". Using the NTFS permission it is therefore also<br />

possible to assign access rights individually to files and subdirectories (for<br />

more details see also S 4.53).<br />

Share permissions obtained by belonging to groups are cumulative; this means<br />

that if a user is a member of various groups to which different share<br />

permissions have been granted in relation to a particular directory, the<br />

furthest-ranging permission applies for that user. <strong>The</strong>re is an exception to this<br />

rule, however: the "No Access" share permission is dominant over all other<br />

share permissions.<br />

Example: Let us assume that D:\RESULTS is shared. User Smith is a member<br />

of group A and of group B. Group A is assigned "Read" permission and group<br />

B "Full Access" permission to the above shared directory. In this case the<br />

"Full Access" permission is the decisive permission for user Smith. If user<br />

Smith is now also made a member of group C, for which the "No Access"<br />

share permission has been assigned for the shared directory D:\RESULTS,<br />

user Smith is denied access to this directory via the network. If this is not the<br />

desired effect, all the administrator can do is check which groups have been<br />

assigned the "No Access" share permission to the resource and find out to<br />

which of these groups the user concerned belongs. <strong>The</strong> user must then be<br />

removed from the relevant group.<br />

Furthermore, it should be noted that Windows NT always shares the root<br />

directories of all disks together with the Windows directory %SystemRoot%<br />

(generally C:\WINNT) for administrative accesses. <strong>The</strong> access rights to these<br />

special releases cannot be changed and are restricted to the user group<br />

"Administrators". <strong>The</strong>se releases are not directly visible, as they have release<br />

names along the lines of "Disk name$", thus for example "C$" or the name<br />

"ADMIN$".<br />

As a result there is a danger that<br />

- someone can try out the administrator user name and password, or<br />

- an administrator can secretly access users’ computers at any time.<br />

If this feature for facilitating workstation management is required, a decision<br />

must be made as to whether administrators should use the same password for<br />

all workstations under their jurisdiction. A single password is easier to<br />

remember but, if detected, would allow intruders to access all workstations.<br />

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

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

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

Saved successfully!

Ooh no, something went wrong!