12.07.2015 Views

eTrust CA-Top Secret Security for z/OS and OS ... - SupportConnect

eTrust CA-Top Secret Security for z/OS and OS ... - SupportConnect

eTrust CA-Top Secret Security for z/OS and OS ... - SupportConnect

SHOW MORE
SHOW LESS
  • No tags were found...

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Chapter2Controlling Access to theHierarchical File SystemThere are two methods a site can use to secure the Hierarchical File System(HFS).■■The first process is internal to UNIX System Services <strong>and</strong> is based on theUNIX model of security.The second process is external security <strong>and</strong> uses st<strong>and</strong>ard <strong>eTrust</strong> <strong>CA</strong>-<strong>Top</strong><strong>Secret</strong> security authorizations to secure HFS.Note: These methods are mutually exclusive, you must select one.Controlling HFS Using the Native UNIX <strong>Security</strong> ModelThe Hierarchical File System (HFS) is a tree-structured file system consisting ofdirectories <strong>and</strong> files. It resembles the D<strong>OS</strong> file system, although the slash (/) isused instead of the backslash (\).Each file <strong>and</strong> directory is assigned an owning UID <strong>and</strong> an owning GID. Theassignment is defined <strong>and</strong> saved in the file system, not in the external securityproduct.Three categories of users can access each directory <strong>and</strong> file in the HFS:■■■File ownerGroup that owns the fileAll other users defined to UNIX System ServicesDifferent access levels can be set <strong>for</strong> any of these three categories. For example,permissions can be defined so that the file owner gets READ <strong>and</strong> WRITE access,a member of the file's group gets only READ access, <strong>and</strong> all other users haveneither READ nor WRITE access to the file.Controlling Access to the Hierarchical File System 2–1

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

Saved successfully!

Ooh no, something went wrong!