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

More documents

Recommendations

Info

OpenEdition MVS / UNIX System Services SupportStep 2—Assign a GID (groupid) to the GROUP acids you created in Step 1.(Every group must have a GID number assigned to it.) A GID can be any numberfrom 0 to 2,147,483,647. Define a GID of 1 for the OMVSGRP group and a GID of2 for the TTY group by issuing the following TSS command:TSS ADD(OMVSGRP) GID(1)TSS ADD(TTY) GID(2)Step 3—You can now create the acid to be used for the OMVS started task.TSS CREATE(OMVSKERN) TYPE(USER) NAME('OMVS STC ACID') PASS(password,0)DEPT(dept) FACILITY(STC,APPC)FACILITY(APPC) is not required with OS/390 V2R4 and above.Step 4—Assign the acid to UNIX System Services MVS in the STC record.TSS ADD(STC) PROCNAME(OMVS) ACID(OMVSKERN)This example shows an acid created for OMVS as a started task.Step 5—Assign a UID to the STC acid created in Step 3. You must define theUNIX System Services MVS kernel started task acid as a superuser by assigningit a UID of 0.TSS ADD(OMVSKERN) UID(0)In accordance with UNIX System Services MVS requirements, giving an acid aUID of zero automatically designates her as a superuser.Step 6—Assign a default group to the STC acid.TSS ADD(OMVSKERN) DFLTGRP(OMVSGRP)Step 7—Assign the OMVSGRP and TTY groups to the OMVS acid by issuing thefollowing TSS commands:TSS ADD(OMVSKERN) GROUP(OMVSGRP)TSS ADD(OMVSKERN) GROUP(TTY)Step 8—Create the BPXROOT acid. The BPXPRMxx parameter SUPERUSER(xxxxxxx) identifies the userid to be used when a user issues 'SU' to change theirUID to 0. SU uses the function setuid() to accomplish this task. If theSUPERUSER(xxxxxxx) parameter is not specified in BPXPRMxx the useriddefaults to BPXROOT. This acid must be defined with a UID(0) and must nothave BPX.DAEMON authorization. Create this acid by issuing these commands:TSS CREATE(BPXROOT) TYPE(USER) NAME('BPXROOT ACID')PASS(password,0)DEPT(OMVSDEPT) FACILITY(APPC)TSS ADD(BPXROOT) GROUP(OMVSGRP) DFLTGRP(OMVSGRP) UID(0)FACILITY(APPC) is not required with OS/390 V2R4 and above.Step 9—Refresh the UID and GID tables.The following command will refresh these tables.TSS MODIFY(OMVSTABS)1–14 Cookbook
OpenEdition MVS / UNIX System Services SupportNow that the UNIX System Services kernel acid has been defined to eTrustCA-Top Secret, you can start USS by issuing the standard operator command forstarted tasks. Starting with OS/390 V1R3, the OMVS kernel is part of BCP. Thestandard MVS start and stop commands no longer apply.Defining Other OMVS Started Task ACIDsDefine acids for other OMVS started tasks by issuing the following commands:TSS CRE(INETD) TYPE(USER) NAME('OMVS INETD STC')DEPT(dept) FAC(STC) PASSWORD(password,0)TSS ADD(INETD) UID(0) GROUP(OMVSGRP) DFLTGRP(OMVSGRP)HOME(/) OMVSPGM(/bin/sh)TSS CRE(RMFGAT) TYPE(USER) NAME('OMVS RMFGAT')DEPT(dept) FAC(STC) PASSWORD(password,0)TSS ADD(RMFGAT) UID(0) GROUP(OMVSGRP) DFLTGRP(OMVSGRP)HOME(/) OMVSPGM(/bin/sh)TSS ADD(STC) PROCNAME(INETD) ACID(INETD)TSS ADD(STC) PROCNAME(RMFGAT) ACID(RMFGAT)TSS ADD(STC) PROCNAME(BPXOINIT) ACID(OMVSKERN)TSS ADD(STC) PROCNAME(BPXAS) ACID(OMVSKERN)TSO ISHELL SupportThe eTrust CA-Top Secret TSSOPMAT file contains a replacement member forthe IBM REXX exec BPXWIRAC. Copy TSSOPMAT(BPXWIRAC) to a partitioneddata set compatible with your TSO SYSEXEC data sets. Assure that this file isconcatenated ahead of the IBM supplied SYSEXEC data sets. Failure to do thisresults in a S0C1 ABEND when entering the ISHELL.How to Create the Superuser Administrator ACIDThe UNIX System Services Shell and Utilities installation process createsdirectories in the Hierarchical File System (HFS). To perform the installationsteps, the user must have superuser authority.A superuser is a special User acid under UNIX System Services. The superuser isa trusted acid who can maintain the UNIX System Services system andadminister security in the HFS. It is important to note that assigning superuserauthority to an acid doesn't give the user any authority within eTrust CA-TopSecret, only authority in UNIX System Services. A superuser's UID has a value ofzero.Use caution when assigning acids the superuser authority. A superuser passes allsecurity checks, meaning the superuser can access any UNIX file in the filesystem.Implementing eTrust CA-Top Secret in a z/OS or OS/390 Environment 1–15
Page 1 and 2: eTrust CA-Top Secret ® Securityfo
Page 3: Technical UpdatesMay 2003The follow
Page 6 and 7: Superuser Granularity .............
Page 8 and 9: WLM (Workload Management)..........
Page 11 and 12: Chapter1Implementing eTrust CA-TopS
Page 13 and 14: z/OS and OS/390 CompatibilityThe li
Page 15 and 16: z/OS and OS/390 Release-Specific Se
Page 17 and 18: OpenEdition MVS / UNIX System Servi
Page 23: OpenEdition MVS / UNIX System Servi
Page 31 and 32: Tracing UNIX System Services (OMVS)
Page 39 and 40: Using TCP/IPFILE AUDIT OPTIONS—Th
Page 41 and 42: Using TCP/IPwheresysname is the nam
Page 43 and 44: Using FTPHow to Secure FTPFTP runs
Page 45 and 46: Using TELNETTerminal Source Restric
Page 47 and 48: WebSphere Application Server for z/
Page 57 and 58: Lotus Domino Go Webserver/* PERMITT
Page 59 and 60: Lotus Domino Go WebserverTo disable
Page 61 and 62: Lotus Notes and Novell Directory Se
Page 63 and 64: Digital Certificate SupportGeneral
Page 65 and 66: Digital Certificate SupportFOR|UNTI
Page 67 and 68: Digital Certificate SupportDCDSN(re
Page 69 and 70: Digital Certificate SupportNote: In
Page 71 and 72: Digital Certificate SupportYou can
Page 73 and 74: Digital Certificate SupportCase #2.
Page 75 and 76:
Digital Certificate SupportImportan
Page 77 and 78:
Digital Certificate SupportAdding a
Page 79 and 80:
Digital Certificate SupportReconnec
Page 81 and 82:
Digital Certificate SupportTSS LIST
Page 83 and 84:
Certificate Name Filtering SupportT
Page 85 and 86:
Certificate Name Filtering SupportI
Page 87 and 88:
Certificate Name Filtering SupportD
Page 89 and 90:
Certificate Name Filtering SupportL
Page 91 and 92:
KerberosKerberosetrust CA-Top Secre
Page 93 and 94:
KerberosThe command syntax for this
Page 95 and 96:
KerberosThe following command creat
Page 97 and 98:
Mapping of Foreign EnvironmentsMapp
Page 99 and 100:
Mapping of Foreign EnvironmentsMapp
Page 101 and 102:
Distributed File Server SMB SUPPORT
Page 103 and 104:
NFS (Network File System)The first
Page 105 and 106:
z/OS and OS/390 Security Server Sup
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Chapter2Controlling Access to theHi
Page 113 and 114:
Controlling HFS Using the Native UN
Page 115 and 116:
Controlling HFS Using CA SAF HFS Se
Page 117 and 118:
Securing HFS FunctionsKeywordALLCON
Page 119 and 120:
Securing HFS FunctionsFile Function
Page 121 and 122:
Implementing CA SAF HFS SecurityImp
Page 123 and 124:
HFSSEC Control Option+12—The addr
Page 125 and 126:
HFSSEC Control OptionDiagnosticsThe
Page 127 and 128:
HFSSEC Control OptionUNIX CMDCHMOD(
Page 129 and 130:
HFSSEC Control OptionTSSSUTIL EQUIV
Page 131 and 132:
HFSSEC Control OptionUNIX CMDS ACCE
Page 133 and 134:
HFSSEC Control OptionExample 1// JO
Page 135 and 136:
HFSSEC Control OptionExample 2// JO
Page 137 and 138:
MessagesMessagesCAS2301EEVENT PROCE
Page 139 and 140:
MessagesCAS2306Wxxxxxxxxxxxxxxx EVE
Page 141:
MessagesCAS2319ITRACEID=aaaaaaaa US
Page 144 and 145:
The SYSPLEX XES FunctionThere are t
Page 146 and 147:
eTrust CA-Top Secret and the SYSPLE
Page 148 and 149:
Defining the Sysplex to eTrust CA-T
Page 150 and 151:
Managing the Coupling FacilityWhen
Page 152 and 153:
Defining SYSTEM LOGGER to eTrust CA
Page 154 and 155:
IMVSECUR/*=========================
Page 156 and 157:
IMVSECUR/*=========================
Page 158 and 159:
IMVSECURFeature RACF eTrust CA-Top
Page 160 and 161:
PERMITIn eTrust CA-Top Secret, all
Page 163 and 164:
Indexcomponent names for z/OS and O
Page 165 and 166:
OpenEdition MVS supportACIDs needed
show all

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

Create successful ePaper yourself

Delete template?

Save as template?