Security
CICS uses the services provided by an external security manager, such as RACF, to control access to application and system resources.
A transaction can be initiated in CICS by an individual, by a program running in a system connected to CICS through a communication network, or by another transaction running in CICS. In all cases, when CICS security is active, the transaction is associated with a user. Although a CICS user is, in many cases, an individual, in general a user is an entity that is identified by a user identifier (user ID).
When a user makes a request, CICS calls the external security manager to determine if the user has the authority to make the request. If the user does not have the correct authority, CICS denies the request.
- Signon security
- Ensures that terminal users are entitled to connect to CICS.
- Link security
- Ensures that remote systems are entitled to connect to CICS.
- Transaction security
- Ensures that users that attempt to run a transaction are entitled to do so.
- Resource security
- Ensures that users who use CICS resources are entitled to do so.
- Command security
- Ensures that users who use the CICS system programming interface are entitled to do so.
CICS can use user IDs and passwords or password phrases, or Secure Sockets Layer (SSL) client certificates to perform identification and authentication of users.