Limit OS Privileges of Fenced Mode Process (DB2_LIMIT_FENCED_GROUP)

MediumLevel 1Automateddb2

Description

The DB2_LIMIT_FENCED_GROUP registry variable allows restricting the operating system privileges of the fenced mode process (db2fmp) to the privileges assigned to the DB2USERS group. This variable only has effect if extended security is enabled (DB2_EXTSEC) and the Db2 Service Account is not LocalSystem. This registry variable only applies to Db2 Servers running on Windows. Must be ON. Default: The default value of DB2_LIMIT_FENCED_GROUP is OFF. 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=$(db2set -all 2>/dev/null) || exit 1; printf '%s\n' "$out" | awk '/^\[[a-zA-Z]\]/ { l = $0; sub(/^\[[a-zA-Z]\] */, "", l); k = l; sub(/=.*/, "", k); v = l; sub(/^[^=]*=/, "", v); gsub(/[ \t]/, "", v); if (!(k in r)) r[k] = v } END { if (toupper(r["DB2_LIMIT_FENCED_GROUP"]) == "ON") print "compliant"; else print "noncompliant: " "DB2_LIMIT_FENCED_GROUP=" r["DB2_LIMIT_FENCED_GROUP"] }'

Expected output: compliant

How it is fixed

Fix method: Guidance or infrastructure patch

Run the following command to set the DB2_LIMIT_FENCED_GROUP registry variable to ON: db2set DB2_LIMIT_FENCED_GROUP=ON

Properties

Operating systems: Any
Tags: db2databaseregistry
Reference: CIS IBM Db2 12.1 Benchmark v1.0.0 - 3.2.5 Limit OS Privileges of Fenced Mode Process (DB2_LIMIT_FENCED_GROUP)

Check this host

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

shell

tmaegis scan --target db2