Database Manager Configuration Parameter: TRUST_CLNTAUTH

HighLevel 1Automateddb2

Description

This database manager configuration parameter is only active when the authentication parameter is set to CLIENT which is not a recommended setting as discussed in the [authentication parameter section](#specify-a-secure-authentication- type-authentication). If the parameter is set to CLIENT, the user ID and password are not needed, but if they are provided, authentication will occur at the ... Passes when the effective connection authentication (SRVCON_AUTH, or AUTHENTICATION when SRVCON_AUTH is NOT_SPECIFIED) is not CLIENT; otherwise TRUST_CLNTAUTH must be SERVER. Run as the instance owner (or with sqllib/db2profile sourced) so the db2 CLP reads this instance's configuration.

How it is checked

Audit method: Shell command

shell

out=$(db2 get dbm cfg 2>/dev/null) || exit 1; printf '%s\n' "$out" | awk '{ if (match($0, /\([A-Z0-9_]+\) *=/)) { k = substr($0, RSTART + 1, RLENGTH); sub(/\).*/, "", k); v = $0; sub(/^[^=]*=/, "", v); gsub(/[ \t]/, "", v); c[k] = v } } END { if (((c["SRVCON_AUTH"] == "NOT_SPECIFIED" || c["SRVCON_AUTH"] == "") ? c["AUTHENTICATION"] : c["SRVCON_AUTH"]) != "CLIENT" || c["TRUST_CLNTAUTH"] == "SERVER") print "compliant"; else print "noncompliant: " "SRVCON_AUTH=" c["SRVCON_AUTH"] " AUTHENTICATION=" c["AUTHENTICATION"] " TRUST_CLNTAUTH=" c["TRUST_CLNTAUTH"] }'

Expected output: compliant

How it is fixed

Fix method: Guidance or infrastructure patch

1. Attach to the Db2 instance. db2 => attach to <db2instance> 2. Run the following command: db2 => update database manager configuration parameter using trust_clntauth SERVER 3. Restart the Db2 instance. db2 => db2stop db2 => db2start

Properties

Operating systems: Any
Tags: db2databaseauthentication
Reference: CIS IBM Db2 12.1 Benchmark v1.0.0 - 5.5 Database Manager Configuration Parameter: TRUST_CLNTAUTH

Check this host

Run this on a machine you are allowed to audit. The scan is read-only.

shell

tmaegis scan --target db2