Managing inbound TCP/IP-based connection requests
DRDA connections that use TCP/IP have fewer security controls than do connections that use SNA protocols. When planning to control inbound TCP/IP connection requests, you must decide whether you want the requests to have authentication information, such as RACF® passwords, RACF PassTickets, and Kerberos tickets, passed along with authorization IDs.
About this task
Attention: To protect
your authentication information, use the z/OS® Communications Server IP Application Transparent
Transport Layer Security (AT-TLS) to secure your network connections.
To complement the use of AT-TLS, set the TCPALVER subsystem parameter
of installation panel DSNTIP5 to SERVER_ENCRYPT. Setting this parameter
to SERVER_ENCRYPT provides the strongest level of security. Connections
are accepted only if user credentials are provided to authenticate
the user ID, and strong encryption is used to protect the user ID
and credentials.
Procedure
To manage inbound TCP/IP-based connection requests:

