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.

OpenEdition MVS / UNIX System Services SupportThe following example shows how to define user OMVSUSR as a superuser.Since HOME <strong>and</strong> OMVSPGM aren't explicitly specified, the defaults are taken<strong>for</strong> these fields.TSS ADD(OMVSUSR) UID(0)This example shows how to define user OMVSU2 as a regular user. The HOME<strong>and</strong> PROGRAM keywords are also used.TSS ADD(OMVSU2) UID(199) HOME(/u/omvsu2) OMVSPGM(/bin/sh)SUPERUSER—A superuser passes all UNIX System Services security checks<strong>and</strong>, there<strong>for</strong>e, can access all UNIX files. An acid can become a superuser in oneof two ways:■or■Have a UID(0)Use the SU (switch user) comm<strong>and</strong> if resource IBMFAC(BPX.SUPERUSER)has been permitted to that user.Other than the required started task acids, the only acids requiring a UID(0) arethe system programmers responsible <strong>for</strong> installing USS. All other acids shouldhave a non-zero UID <strong>and</strong> be permitted the necessary authorities in the classIBMFAC plus file permissions. The <strong>eTrust</strong> <strong>CA</strong>-<strong>Top</strong> <strong>Secret</strong> resource class IBMFACis equivalent to the IBM FACILITY class.How to Define UNIX System Services GroupsUNIX System Services security is based on user <strong>and</strong> group ownership of files<strong>and</strong> processes. <strong>eTrust</strong> <strong>CA</strong>-<strong>Top</strong> <strong>Secret</strong> uses the DFLTGRP <strong>and</strong> GROUP fields ofthe acid record to assign the user to a UNIX System Services group.<strong>eTrust</strong> <strong>CA</strong>-<strong>Top</strong> <strong>Secret</strong> requires that the UID be unique <strong>for</strong> each acid (except UID0) <strong>and</strong> that the GID is unique <strong>for</strong> each group acid. (Only UID 0 can be assigned tomore than one acid.)The GROUP type acid defines UNIX System Services groups to <strong>eTrust</strong> <strong>CA</strong>-<strong>Top</strong><strong>Secret</strong>. The GROUP type acid contains the OMVS segment, which consists of onefield: the GID keyword.GID is a numeric field that accepts values from zero to 2,147,483,647. This valuemust be unique to maintain control over a particular group. You can assign up to256 groups to a user, using the GROUP field.The following example shows how to create an OMVS GROUP acid <strong>for</strong> a groupcalled OMVSGRP <strong>and</strong> assign it a GID of 1.TSS CREATE(OMVSGRP) TYPE(GROUP) NAME(‘OMVSGROUP’) DEPT(OMVSDEPT)TSS ADD(OMVSGRP) GID(1)At least one OMVS group acid must exist prior to implementation.Implementing <strong>eTrust</strong> <strong>CA</strong>-<strong>Top</strong> <strong>Secret</strong> in a z/<strong>OS</strong> or <strong>OS</strong>/390 Environment 1–9

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

Saved successfully!

Ooh no, something went wrong!