Summary of intercommunication security levels
Table 1 shows bind-time, transaction, resource, and command security, and how CICS® enforces these levels of security under the LU6.1, LU6.2, IPIC, and MRO protocols. It also shows how the two levels of authorization (user and link) are involved at the three security levels.
For guidance on choosing between these environments, see Intercommunication methods.
Table 1 shows a summary of intercommunication
security.
| Security level | Security checks | LU type 6.1 | LU type 6.2 | IPIC | MRO |
|---|---|---|---|---|---|
| Bind-time security (when BIND is received) | Should the BIND request be accepted? | No check | Session key from RACF® | SSL Client Certificate from partner | DFHAPPL profiles in RACF FACILITY class |
| Bind-time security (when BIND is sent) | Is the remote system the correct one? | No check | Session key from RACF | SSL Client Certificate to partner | DFHAPPL profiles in RACF FACILITY class |
| Link security | Does the link have authority to attach the transaction? | Link authority is established just after the session is bound, by signon of the user ID specified in the SECURITYNAME attribute of the CONNECTION definition or the USERID attribute of the SESSIONS definition. | Link authority is established just after the connection is established, by signon of a user ID determined according to the IPCONN LINKAUTH attribute. | Link authority is established just after the session is bound, by signon of the user ID specified in the USERID attribute of the SESSIONS definition. | |
| Transaction security | Does the remote user have authority to access this system? | No check | The authority of the remote user is established at signon time | ||
| Transaction security | Does the remote user have authority to attach the transaction? | Link authority | The authority of the remote user is established at this attach request (or possibly at an earlier attach request from the same user) by sign-on | ||
| Resource, command, and surrogate security | Does the session have the authority to access other resources that the transaction uses? | Link authority is established just after the session is bound, by signon of the user ID specified in the SECURITYNAME attribute of the CONNECTION definition or the USERID attribute of the SESSIONS definition. | Link authority is established just after the connection is established, by signon of a user ID determined according to the IPCONN LINKAUTH attribute. | Link authority is established just after the session is bound, by signon of the user ID specified in the USERID attribute of the SESSIONS definition. | |
| Resource, command, and surrogate security | Does the remote user have authority to access other resources that the transaction uses? | Link authority | The authority of the remote user is established at this attach request (or possibly at an earlier attach request from the same user) by sign-on | ||
Note: Remember to define profiles for your resources and users to
RACF, as described for single systems in RACF facilities.