Configuration Best Practices › Exit Considerations

Exit Considerations

We recommend that you periodically review each exit to recertify its applicability and usefulness. If the exit provides a function that CA Top Secret for z/OS now provides, you can migrate from that exit point to the native product functionality.

Business Value:

As CA Top Secret for z/OS has evolved, we have added exit functionality to the base product, typically using new options, security records, privileges, and so on. Because CA Top Secret Option for DB2 leverages the CA Top Secret for z/OS security controls, any exits specified in the base product can affect the access decision CA Top Secret for z/OS returns to any DB2 access authorization request; therefore, examine CA Top Secret for z/OS exits line-by-line to identify specifically the role of each exit.

Additional Considerations:

We also suggest that you consider the following:

• Carefully control CA Top Secret for z/OS exit code and the libraries that hold the source and executable code, and implement strict change controls to help ensure that all changes are properly tracked and audited.
• Implement strict security and change management controls to help ensure that only properly certified changes are allowed to occur.

The CA Auditor freezer function can automatically monitor these critical data sets.