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

More documents

Recommendations

Info

WebSphere Application Server for z/OS AND OS/390Finally, in a distributed network, how do you ensure that messages being passedare confidential and have not been tampered? How do you ensure that clients arewho they claim to be? How do you map network identities to z/OS or OS/390identities? These issues are addressed by the following support in WebSphere forz/OS:■■■The use of SSL and digital certificatesKerberosDistributed Computing Environment (DCE)Network security is not required for your initial installation and customization ofWebSphere for z/OS. This information is provided to introduce you toWebSphere for z/OS security and allow you to make early planning decisionsabout system security. The following topics describe how WebSphere for z/OSsupports security. The descriptions are organized under the following subtopics:■■Authorization CheckingUser Identification, Authentication and Network SecurityAuthorization CheckingEach control region, server region, and client must have its own MVS user ID(more about user identification and authentication later). When a request flowsfrom a client to the server or from a server to a server, WebSphere for z/OSpasses the user identity (client or server) with the request. Thus each request isperformed on behalf of the user identity and the system checks to see if the useridentity has the authority to make such a request.ControlAccess control lists in LDAPCBIND classDATASET classDCEUUIDS and IBMFACclassesDSNR classEJBROLE classIBMFACAuthorizationControlled access to WebSphere for z/OSnaming and interface repository dataAccess to a serverAccess to data setsMapping DCE credentials to Top Secret userIdsAccess to DB2Access to methods in enterprise beansSSL key rings, certificates and mappings(IRR.DIGTCERT.GENCERT) &(IRR.DIGTCERT.LIST) &(IRR.DIGTCERT.LISTRING)1–38 Cookbook
WebSphere Application Server for z/OS AND OS/390ControlIBMFAC class(IMSXCF.OTMACI)IBMFAC Class(IRR.RUSERMAP)File permissionsGRANTs (DB2)LOGSTRM classOPERCMDS classPTKTDATA classSERVER classSOMDOBJS classSTCSURROGAT class (*.DFHEXCI)AuthorizationAccess to OTMA for IMS accessKerberos credentialsAccess to HFS filesDB2 access to plans and databaseAccess to log streamsStart and stop servers by DaemonPassticket enabling in the Sysplex (Thisrelates to the session keys in the NDT in TopSecret)Access to control region by a server regionAccess to methods in CORBA objectsAssociate procname and userid in the STCtableAccess to EXCI for CICS accessServer Authorization CheckingTo control access to WebSphere for z/OS resources, give greater authority tocontrol regions and less authority to server regions.Level of Trust and Authority for RegionsRegionControl regionServer regionLevel of trust and access authorityContains WebSphere for z/OS system code.Trusted, deals with multiple users. Greaterauthorization. Runs APF-authorized.Contains application code. Untrusted. Otherthan having authorization to get work and toattach to data stores, should rununauthorized.Implementing eTrust CA-Top Secret in a z/OS or OS/390 Environment 1–39
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: WebSphere Application Server for z/
Page 51 and 52: 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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?