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

More documents

Recommendations

Info

Digital Certificate Support■URI—Specifies the universal resource identifier.For example: www.ca.comNotes:– When you specify multiple parameters to ALTNAME, you must includeone single quote at the beginning and end of parameter list.For example: ALTNAME('IP=201.100.10.9 EMAIL=my.email@test.net')– Multiple parameters are separated with a space (see example above).ICSF—If ICSF is specified and the IBM ICSF feature is enabled, the private key isstored in the ICSF data facility.An example for the ICSF attribute follows:TSS GENCERT(USER01) DIGICERT(DIGI0001) ICSFKEYSIZE—Specifies the size of the private key in decimal bits. The maximumkey size is determined by United States of America export regulations and iscontrolled by non eTrust CA-Top Secret code in z/OS and OS/390. Currently,the standard sizes for keys are:■■■512—low-strength key768—medium-strength key1024—high-strength key (Default)Examples for the KEYSIZE command follow:TSS ADD(USER01) DIGICERT(DIGI0001) DCDSN(USER01.CERTIF.001) KEYSIZE(512)TSS ADD(USER01) DIGICERT(DIGI0001) DCDSN(USER01.CERTIF.001) KEYSIZE(768)TSS ADD(USER01) DIGICERT(DIGI0001) DCDSN(USER01.CERTIF.001) KEYSIZE(1024)KEYUSAGE—Specifies key attribute information, including the appropriatevalues for the KeyUsage certificate extension, of which one or more of the valuesmight be coded. For certificate authority certificates (CERTAUTH) the default isCERTSIGN and is always set. There is no default for certificates that are notcertificate-authority certificates. Valid values for KEYUSAGE include thefollowing:■■■■HANDSHAKE - Facilitates identification and key exchange during securityhandshakes, such as SSL, which set the digital signature and keyencipherment indicators.DATAENCRYPT - Encrypts data, which sets the data enciphermentindicator.DOCSIGN - Specifies a legally-binding signature, which set thenon-repudiation indicator.CERTSIGN - Specifies a signature for the other digital certificates and CRLs,which sets the keyCertSign an cRLSign indicators.1–58 Cookbook
Digital Certificate SupportNote: Include single quotes if specifying more than one value with KEYUSAGE.For example:KEYUSAGE('HANDSHAKE DATAENCRYPT')LABLCERT—Specifies an optional and case-sensitive label to be associated withthe certificate being added to the user. Up to 32 characters can be specified forthe label name. Spaces are allowed if you use single quotes. This label is used asa handle instead of the serial number and issuer's distinguished name, and mustbe unique for the individual user. If a label is not specified, the label field willdefault to the value specified within the DIGICERT keyword.NADATE/NATIME—The optional NADATE and NATIME keywords specifythe effective dates and times to not be used in the digital certificate. TheNADATE specifies the “not after” date after which a digital certificate cannot beused. The NATIME specifies the “not after” time after which the certificatecannot be used. The certificate is deactivated after this date and time.An example for the NADATE/NATIME command follows:TSS GENCERT(user1) DIGICERT(cert0001) DCDSN(user1.cert.data)NADATE(09/01/03) NATIME(00:00:01)Date and time fields are optional, except if time is specified, date is required. IfNADATE is omitted, the default is one year from the date the certificate isgenerated.NBDATE/NBTIME— The optional NBDATE and NBTIME keywords specifythe effective dates and times to be used in the digital certificate. The NBDATEspecifies the “not before” date which a digital certificate can be used. TheNBTIME specifies the “not before” time which the certificate can be used. Thecertificate is activated at the specified date and time.An example for the NBDATE/NBTIME command follows:TSS GENCERT(user1) DIGICERT(cert0001) DCDSN(user1.cert.data)NBDATE(09/01/02) NBTIME(08:00:01)Date and time fields are optional, except if time is specified, date is required.SIGNWITH—Specifies the certificate with a private key that is signing thecertificate. If not specified, the default is to sign the certificate with a private keyof the certificate that is being generated. This creates a self-signed certificate. IfSIGNWITH is specified, it must refer to a certificate that has a private keyassociated with it. If no private key is associated with the certificate, aninformational message is generated and processing stops. If DCDSN is specifiedon the GENCERT command, the SIGNWITH keyword is required.Self-signed certificates are always trusted, while all other certificates are createdwith the trust status of the certificate specified in the SIGNWITH keyword. If thecertificate specified in the SIGNWITH keyword is not trusted, an informationalmessage is issued, but the certificate is still generated.Implementing eTrust CA-Top Secret in a z/OS or OS/390 Environment 1–59
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 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: Digital Certificate SupportDCDSN(re
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 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?