Implementing LU6.2 security

This topic tells you how to implement security for LU6.2.

Bind-time security with LU6.2
A security check can be applied when a request to establish an APPC session is received from, or sent to, a remote system; that is, when the session is bound. This is called bind-time security (or, in SNA terms, session security), and is part of the CICS® implementation of the LU6.2 architecture.
Link security with LU6.2
Link security further restricts the resources a user can access, depending on the remote system from which they are accessed. The practical effect of link security is to prevent a remote user from attaching a transaction or accessing a resource for which the link userid has no authority.
User security with LU6.2
SNA profiles and attach-time security
Implementation of the LU6.2 attach-time security in CICSTS54.CICS conforms strictly to the architecture.
Transaction, resource, and command security with LU6.2
Transaction routing security with LU6.2
In transaction routing, the authority of a user to access a transaction can be tested in both the TOR and the AOR.
Function shipping security with LU6.2
When CICS receives a function-shipped request, the transaction that is invoked is the mirror transaction.
Distributed program link security with LU6.2
The CICS distributed program link (DPL) facility enables a CICS program (the client program) to call another CICS program (the server program) in a remote CICS region. DPL is used when the SYSID option on the LINK API command, or the REMOTESYSTEM option of the PROGRAM resource definition, specifies a remote CICS region.
Security checking done in AOR with LU6.2
Security checking is different depending on how SECURITYNAME is specified in the AOR and TOR.

Parent topic: Security for intercommunication