Upgrading security
This section summarizes the actions that relate to security when you migrate from one release of CICS to another.
| Your current version | Action | Mandatory or optional? |
|---|---|---|
| Reconfigure to use SAML support in the base product | Mandatory, if you are using SAML support | |
| Check security permissions on CICS bundles | Optional, if you use bundles | |
| Review the impact of extensions to command and resource security checks | Mandatory | |
| Review settings for programs that are used as application entry points | Optional | |
| Define new RACF category 1 transactions to the ESM | Mandatory | |
| Adapt applications to changed ESM output from VERIFY PASSWORD | Mandatory |

Reconfigure to use SAML support in the base product
In previous releases, support for SAML was provided by CICS® TS Feature Pack for Security Extensions V1.0. From CICS TS 5.2, this function is incorporated into CICS and the feature pack is not supported.
- Copy your STS configuration file to a new location on z/OS® UNIX to use with the new CICS release.
- Upgrade your java.policy file.
- If you are using a user java.policy file, copy it to a new location on z/OS UNIX to use with the new CICS release.
- Update the following rule to refer to the new CICS root
directory.
where USSHOME is the name and path of the root directory for CICS Transaction Server files on z/OS® UNIX.:// All permissions granted to CICS codesource protection domain grant codeBase "file://USSHOME//-" { permission java.security.AllPermission; };
- Remove the rule that applies to the feature pack
files:
where fp_dir is the Feature Pack installation directory.grant codeBase "file:fp_dir-" { permission java.security.AllPermission; }; - Upgrade your JVM profile. Perform the following additional steps:
- Delete the CLASSPATH_SUFFIX line from your JVM server profile.
- If you are using a user java.policy file, update the java.security.policy property to refer to the new location of this file.
- When no CICS instances are using it, uninstall the feature pack.

Check security permissions on CICS bundles
For resources that are dynamically created by CICS bundles, no additional CICS command security checks and resource security checks take place for those resource types, either when the resources are dynamically created at bundle installation time, or when you manipulate the resources by making changes to the CICS bundle. You need authority only to perform the actions on the CICS bundle, or for bundles that are installed with applications and platforms, to perform the actions on the application or platform with which the CICS bundle was deployed. However, CICS command security and resource security for the individual resource types do apply when you inquire on the dynamically created resources, or if you manipulate the dynamically- created resources directly.
If you used CICS bundles in earlier CICS releases, check the security permissions that you gave to users for those bundles. Depending on how you set up security for CICS bundles, users with authority to act on individual CICS bundles might now be able to act on new or existing resources that are dynamically created as part of the installation of a bundle. Ensure that the levels of authority for BUNDLE resources are still appropriate.

Review the impact of extensions to command and resource security checks
Command security applies if CMDSEC(YES) is specified for the CICS region. Resource security applies if RESSEC(YES) is specified for the CICS region. Releases of CICS extend the resource types, their resource identifiers, and associated commands that are subject to command security checking and resource security checking. Check the resources and commands that are changed.
Review settings for programs that are used as application entry points
If you use program security by setting XPPT=YES, review the security settings for any programs that you declare as application entry points. If you apply security measures to individual PROGRAM resources, for applications that are deployed on platforms, secure the programs that are declared as application entry points, but do not secure other programs in the applications.
The security settings that you specify for a program that is part of an application deployed on a platform apply to both public and private programs, and do not take into account the version of the application. Programs that are declared as an application entry point must have a unique PROGRAM resource name in your environment. However, if you secure programs that run at a lower level in the application, programs with the same names might be running in different applications, which can lead to unforeseen consequences. In this situation, a user might have permission to access a program that is declared as an application entry point, but not have permission to access a program that runs at a lower level in the application because the security settings from another instance of the program name are in effect. Consider the security measures that you apply to a program that is declared as an application entry point program, as applying to the whole application.
Define new RACF category 1 transactions to the ESM
Category 1 transactions include some CICS internal system transactions. You must define these transactions to your external security manager, and authorize the CICS region user ID to use them, so that CICS can initialize successfully when it is running with security enabled (SEC=YES). For a list of CICS transactions that are category 1, see Category 1 transactions.
Adapt applications to changed ESM output from VERIFY PASSWORD
This action applies to CICS TS Version 3 and 4.1, to Version 4.2 only if you have not applied APAR PI21865 and to Version 5 only if you have not applied APAR PI21866.
When you issue the EXEC CICS VERIFY PASSWORD command, CICS enforces the revoked status of a user ID or a user's group connection. The method that CICS uses to verify the password is more efficient, but you might notice changes to the output that is produced when verification takes place. CICS attempts to verify a password by using a RACROUTE REQUEST=EXTRACT request to the external security manager. If the password cannot be verified by using this method, CICS uses a RACROUTE REQUEST=VERIFYX request. Before CICS Transaction Server for z/OS, Version 3 Release 1, CICS always used the RACROUTE REQUEST=VERIFYX request, which is more expensive.
- ESMRESP and ESMREASON codes are not supplied by the external security manager for the new method of verifying a password by using a RACROUTE REQUEST=EXTRACT call. These codes are produced only if CICS needs to use the RACROUTE REQUEST=VERIFYX call. Your application programs must always check the EIBRESP and EIBRESP2 values that are returned by the EXEC CICS VERIFY PASSWORD command and not rely on the ESMRESP and ESMREASON codes.
- Message ICH70002I is not produced by the external security manager for the new method of verifying a password. The message is produced only if CICS needs to use the RACROUTE REQUEST=VERIFYX call. The SETR PASSWORD(WARN(nn)) option must also be active in the external security manager for the message to be produced. Your application programs must therefore not rely on receiving this message.