12.07.2015 Views

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

SHOW MORE
SHOW LESS
  • No tags were found...

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

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

z/<strong>OS</strong> <strong>and</strong> <strong>OS</strong>/390 <strong>Security</strong> Server SupportSetting up the z/<strong>OS</strong> or <strong>OS</strong>/390 LDAP Server with <strong>eTrust</strong> <strong>CA</strong>-<strong>Top</strong> <strong>Secret</strong> involvesthe following steps:1. Create a group definition <strong>for</strong> use with the LDAP Server:TSS CREATE (LDAPGRP) TYPE(GROUP) NAME(‘LDAP Group’) DEPT(OMVSDEPT)TSS ADD(LDAPGRP) GID(nn)Any unused GID number is allowed.2. Define the LDAP Server startup address space identifier:TSS CREATE(LDAPSRV) TYPE(USER) NAME(‘LDAP Startup ID’)DEPT(OMVSDEPT) FACILITY(STC,BATCH) PASS(password,0)TSS ADD(LDAPSRV) GROUP(LDAPGRP) DFLTGRP(LDAPGRP)HOME(/) OMVSPGM(/bin/sh) UID(0)TSS ADD(STC) PROCNAME(LDAPSRV) ACID(LDAPSRV)TSS MODIFY(OMVSTABS)3. The acid <strong>for</strong> the LDAP server started task requires access to the followingIBMFAC resources:TSS ADD(anydept) IBMFAC(BPX.)TSS PERMIT(LDAPSRV) IBMFAC(BPX.DAEMON)TSS PERMIT(LDAPSRV) IBMFAC(BPX.SERVER)ACCESS(READ)ACCESS(UPDATE)DB2 <strong>Security</strong> ExitIn response to the fact that native DB2 only provides internal security, thesecurity server now provides sample code <strong>for</strong> a DB2 security exit. <strong>eTrust</strong> <strong>CA</strong>-<strong>Top</strong><strong>Secret</strong> has offered <strong>for</strong> a number of years the ability to secure DB2 using <strong>eTrust</strong><strong>CA</strong>-<strong>Top</strong> <strong>Secret</strong> <strong>for</strong> DB2. See the <strong>eTrust</strong> <strong>CA</strong>-<strong>Top</strong> <strong>Secret</strong> <strong>for</strong> DB2 ImplementationGuide <strong>for</strong> additional in<strong>for</strong>mation.Integrated Cryptographic ServicesIBM has delivered as a hardware offering, a high powered cryptographiccoprocessor which allows z/<strong>OS</strong> or <strong>OS</strong>/390 applications to exploit cryptography.The z/<strong>OS</strong> or <strong>OS</strong>/390 <strong>Security</strong> Server provides API’s to invoke thesecryptographic services (ICSF) rather than use software algorithms to per<strong>for</strong>m thesame functions. In addition, various functions involved with the management ofkeys are provided in this service. These services combine to provide a site withthe ability to manage public keys.<strong>eTrust</strong> <strong>CA</strong>-<strong>Top</strong> <strong>Secret</strong> provides the following resource classes to allow ICSF to besecured <strong>and</strong> audited.CSFKEYS—This class is used to secure encryption keys. The value, which isowned <strong>and</strong> permitted, is the key label. The key label is in the CKDS or PKDSwhen a key is defined.Implementing <strong>eTrust</strong> <strong>CA</strong>-<strong>Top</strong> <strong>Secret</strong> in a z/<strong>OS</strong> or <strong>OS</strong>/390 Environment 1–99

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

Saved successfully!

Ooh no, something went wrong!