Security mechanisms for Db2 for z/OS as a server

As a server, Db2 for z/OS can accept either SNA or DRDA authentication mechanisms. Make sure to use network security, such as client certificate authentication, SSL connections that use AT-TLS, or IPSec, to secure DRDA authentication mechanisms over a network that is not secure.

Db2 authenticates remote users from the security tokens that are obtained from the SNA ATTACH (FMH-5) or from the DRDA security commands that are described by each of the protocols. See Security mechanisms for DRDA and SNA for more information about using DRDA encryption.

Db2 for z/OS accepts connection requests from remote clients that use an AES or DES encryption algorithm to protect user IDs and passwords over a TCP/IP network. Specifically, Db2 supports the following authentication methods:

  • User ID only (already verified at the requester)
  • User ID and password
  • User ID and PassTicket
  • Kerberos tickets
  • Unencrypted user ID and encrypted password
  • Encrypted user ID and encrypted password
  • User ID, password, and new password

Db2 for z/OS as a server also supports the following authentication mechanisms if the z/OS Integrated Cryptographic Service Facility is installed and active:

  • Encrypted user ID and encrypted security-sensitive data
  • Encrypted user ID, encrypted password, and encrypted security-sensitive data
  • Encrypted user ID, encrypted password, encrypted new password, and encrypted security-sensitive data

Start of changeSecurity-sensitive data is any input or output data. Examples are rows that are retrieved from a remote server, rows that are sent to the remote server, and SQL statement text.End of change