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
HFSSEC Control OptionThe exit can use this exit function to make any specific modifications to the pathname beyond that already performed by CA SAF HFS security processing.TroubleshootingThe following section discusses troubleshooting solutions.ReportingReporting is done through the existing eTrust CA-Top Secret resource report,TSSUTIL. When the AUDIT attribute is on the user’s acid or specificpermissions, audit records can also appear on the report if they are requested inthe report criteria. The report will show the translated name of the HFS file usedfor validation. TSSUTIL should be reviewed when researching validationproblems.In addition, the online real-time monitor TSSTRACK can also be used to monitorHFS file security related events.OPTIONS(32)Control option, OPTIONS(32), provides support for USS event logging to the AuditTracking File.To take advantage of this feature, the LONG option must be specified inTSSUTIL. This will ensure that the full 256-character resource name can bedisplayed. Logging will only take place for the acids that have the AUDIT orTRACE attributes assigned.A new RDT class called USSLOG is introduced with this new USSLOG feature.This will allow TSSUTIL to select USSLOG records with the RESCLASS(USSLOG) option and to report the access level for the USS event. All of therecords are displayed as a resource type of USSLOG.The resource name field will display the USS function, i.e., INIT_USP and forsome types of USS events, i.e., CHECK_ACCESS, the path name and file namebeing assessed. (In the example of the TSSUTIL report below, you can see howthe records are displayed)The TSSOERPT can still be used to get additional detailed information about theUSS event, such as UID, GID or group name. Otherwise TSSUTIL will nowcontain the event information such as: User ID’s, Modes, Function, Path Names,File Names, Return Code, Facility, etc. (See the example below to see how thetypical record are displayed). As part of CASAF, USS events are being logged toSMF as well.2–14 Cookbook
HFSSEC Control OptionDiagnosticsThe CA SAF HFS security interface can be traced by using the SECTRACEcommand. A trace of internal functions of CA SAF HFS security is enabledthrough use of the SECTRACE TYPE=HFS keyword. The trace output can berequested by technical support. The syntax is:SecTrace SET,TYPE=HFSThe following keywords are meaningful when TYPE=HFS is specified:ID=JOBname=USERid=ENable|DISableACTION=MATCHLIM=DEST=CONSOLE|JOBLOG|SYSLOGCONSid=MSGid|NOMSGidOther keywords are ignored. If DEST is not specified, the default isDEST=SYSLOG.The SAF validation calls invoked by CA SAF HFS security can also be traced.These SAF calls are the file and function validations that are passed to eTrustCA-Top Secret. Enable this tracing by first issuing the SECTRACE SETcommand detailed below, followed by a reply to the prompt:ST SET,ID=id,TYPE=SAFP,DEST=dest,ENDR nn,REQSTOR=SAFHFSEC,ENDTSSUTIL/SAF Reference TablesAt OS/390 Release 2.8 and above, results from running a TSSUTIL and a SAFSECTRACE are different when the HFSSEC control option is set to ON or OFF.The tables should be used as a reference when you are evaluating the results ofthese utilities.Controlling Access to the Hierarchical File System 2–15
- 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: z/OS and OS/390 Security Server Sup
- Page 109 and 110: 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: HFSSEC Control Option+12—The addr
- 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
HFSSEC Control OptionDiagnosticsThe <strong>CA</strong> SAF HFS security interface can be traced by using the SECTRACEcomm<strong>and</strong>. A trace of internal functions of <strong>CA</strong> SAF HFS security is enabledthrough use of the SECTRACE TYPE=HFS keyword. The trace output can berequested by technical support. The syntax is:SecTrace SET,TYPE=HFSThe following keywords are meaningful when TYPE=HFS is specified:ID=JOBname=USERid=ENable|DISableACTION=MATCHLIM=DEST=CONSOLE|JOBLOG|SYSLOGCONSid=MSGid|NOMSGidOther keywords are ignored. If DEST is not specified, the default isDEST=SYSLOG.The SAF validation calls invoked by <strong>CA</strong> SAF HFS security can also be traced.These SAF calls are the file <strong>and</strong> function validations that are passed to <strong>eTrust</strong><strong>CA</strong>-<strong>Top</strong> <strong>Secret</strong>. Enable this tracing by first issuing the SECTRACE SETcomm<strong>and</strong> detailed below, followed by a reply to the prompt:ST SET,ID=id,TYPE=SAFP,DEST=dest,ENDR nn,REQSTOR=SAFHFSEC,ENDTSSUTIL/SAF Reference TablesAt <strong>OS</strong>/390 Release 2.8 <strong>and</strong> above, results from running a TSSUTIL <strong>and</strong> a SAFSECTRACE are different when the HFSSEC control option is set to ON or OFF.The tables should be used as a reference when you are evaluating the results ofthese utilities.Controlling Access to the Hierarchical File System 2–15