eTrust CA-Top Secret Security for z/OS and OS ... - SupportConnect
Share Embed Flag
Download ePaper

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

supportconnectw.ca.com
from supportconnectw.ca.com More from this publisher
12.07.2015 Views

WLM (Workload Management)OS/390 NFS NSM (Network Status Monitor)TSS CREATE(MVSNSM) NAME('NFS NSM') DEPT(dept)TYPE(USER) PASS(password,0) FAC(STC)TSS ADD(MVSNSM) NODSNCHK **or per all required data sets**TSS ADD(MVSNSM) UID(0) GROUP(OMVSGRP) DFLTGRP(OMVSGRP)TSS PER(MVSNSM) DSN( per all required data sets )TSS ADD(MVSNSM) SOURCE(INTRDR)Add Procedures to STC acidTSS ADD(STC) PROCN(MVSNFS) ACID(MVSNFS)TSS ADD(STC) PROCN(MVSLOCKD) ACID(MVSNLM)TSS ADD(STC) PROCN(MVSSTATD) ACID(MVSNSM)TSS ADD(STC) PROCN(MVSNFSC) ACID(MVSNFSC)WLM (Workload Management)The WLM ISPF application is protected by a SAF call. Access to the WLM ISPFapplication is controlled through the definition of a facility class in eTrustCA-Top Secret. READ or UPDATE access to the entire WLM service definition isthe only option available through the eTrust CA-Top Secret facility accessauthorization. READ access allows users access to all functions except installingand activating a service definition or policy.Specify an access of NONE for the facility resource. Also, limit the number ofusers authorized to read and update the WLM application to those who maintainthe WLM policy, to performance personnel, or to both. Review the requirementfor operations to have access to install a service definition versus activating anexisting policy.To authorize the facility for WLM, execute the following eTrust CA-Top Secretcommands:TSS ADD(deptacid) IBMFAC(MVSADMIN)—Skip this command if already ownedTSS PER(aicd) IBMFAC(MVSADMIN.WLM.POLICY) ACC(READ)orTSS PER(acid) IBMFAC(MVSADMIN.WLM.POLICY) ACC(UPDATE)z/OS and OS/390 Security Server SupportIBM markets the Security Server as a separate offering, along with z/OS andOS/390. This offering is a bundling of RACF with a number of other products.All of these products perform some security (SAF) function. Those that interfacewith RACF, do so through standard security calls, supported by eTrust CA-TopSecret. None are truly dependent on RACF to function. The followingcomponents make up the Security Server.1–94 Cookbook

z/OS and OS/390 Security Server SupportRACFAlthough delivered as part of the Security Server, RACF must be independentlyactivated, and is not required to run the other Security Server components. RACFis IBM’s SAF compliant security system. It is mainly concerned with system entryvalidation and resource permission. It provides no subsystem specific extensionsto secure such things as partitioned data sets, CICS and IMS. Typically, in RACFphilosophy, these sorts of extensions are available as user maintained exit points.Its reporting and administration capabilities are limited, typically these functionsmust be supplemented by buying additional third party products.To disable RACF, update the appropriate IFAPRDxx member and change the STATEfield to:STATE(DISABLED)Then re-IPL the system to make the change take effect.For example, if you ordered RACF as part of the security server for z/OS and OS/390,and you want to disable the security server, update the IFAPRDxx entry to look like this:PRODUCT OWNER('IBM CORP')NAME('z/OS and OS/390')FEATURENAME('Security Server')ID(5647-A01)VERSION(*)RELEASE(*)MOD(*)STATE(DISABLED)If you ordered RACF as part of the security server for z/OS and OS/390, and want todisable the RACF component of the security server but continue to use the DCEcomponent of the security server, update the IFAPRDxx entries to look like this:PRODUCT OWNER('IBM CORP')NAME('z/OS and OS/390')FEATURENAME('Security Server')ID(5647-A01)VERSION(*)RELEASE(*)MOD(*)STATE(ENABLED)PRODUCT OWNER('IBM CORP')NAME('z/OS and OS/390')FEATURENAME('RACF')ID(5647-A01)VERSION(*)RELEASE(*)MOD(*)STATE(DISABLED)Implementing eTrust CA-Top Secret in a z/OS or OS/390 Environment 1–95

WLM (Workload Management)<strong>OS</strong>/390 NFS NSM (Network Status Monitor)TSS CREATE(MVSNSM) NAME('NFS NSM') DEPT(dept)TYPE(USER) PASS(password,0) FAC(STC)TSS ADD(MVSNSM) NODSNCHK **or per all required data sets**TSS ADD(MVSNSM) UID(0) GROUP(OMVSGRP) DFLTGRP(OMVSGRP)TSS PER(MVSNSM) DSN( per all required data sets )TSS ADD(MVSNSM) SOURCE(INTRDR)Add Procedures to STC acidTSS ADD(STC) PROCN(MVSNFS) ACID(MVSNFS)TSS ADD(STC) PROCN(MVSLOCKD) ACID(MVSNLM)TSS ADD(STC) PROCN(MVSSTATD) ACID(MVSNSM)TSS ADD(STC) PROCN(MVSNFSC) ACID(MVSNFSC)WLM (Workload Management)The WLM ISPF application is protected by a SAF call. Access to the WLM ISPFapplication is controlled through the definition of a facility class in <strong>eTrust</strong><strong>CA</strong>-<strong>Top</strong> <strong>Secret</strong>. READ or UPDATE access to the entire WLM service definition isthe only option available through the <strong>eTrust</strong> <strong>CA</strong>-<strong>Top</strong> <strong>Secret</strong> facility accessauthorization. READ access allows users access to all functions except installing<strong>and</strong> activating a service definition or policy.Specify an access of NONE <strong>for</strong> the facility resource. Also, limit the number ofusers authorized to read <strong>and</strong> update the WLM application to those who maintainthe WLM policy, to per<strong>for</strong>mance personnel, or to both. Review the requirement<strong>for</strong> operations to have access to install a service definition versus activating anexisting policy.To authorize the facility <strong>for</strong> WLM, execute the following <strong>eTrust</strong> <strong>CA</strong>-<strong>Top</strong> <strong>Secret</strong>comm<strong>and</strong>s:TSS ADD(deptacid) IBMFAC(MVSADMIN)—Skip this comm<strong>and</strong> if already ownedTSS PER(aicd) IBMFAC(MVSADMIN.WLM.POLICY) ACC(READ)orTSS PER(acid) IBMFAC(MVSADMIN.WLM.POLICY) ACC(UPDATE)z/<strong>OS</strong> <strong>and</strong> <strong>OS</strong>/390 <strong>Security</strong> Server SupportIBM markets the <strong>Security</strong> Server as a separate offering, along with z/<strong>OS</strong> <strong>and</strong><strong>OS</strong>/390. This offering is a bundling of RACF with a number of other products.All of these products per<strong>for</strong>m some security (SAF) function. Those that interfacewith RACF, do so through st<strong>and</strong>ard security calls, supported by <strong>eTrust</strong> <strong>CA</strong>-<strong>Top</strong><strong>Secret</strong>. None are truly dependent on RACF to function. The followingcomponents make up the <strong>Security</strong> Server.1–94 Cookbook

logo

products

Resources

Company

Terms of service
Privacy policy
Cookie policy
Cookie settings
Imprint
Change language
Made with love in Switzerland
© 2024 Yumpu.com all rights reserved

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

Saved successfully!

Ooh no, something went wrong!