Secure Permissions for the Secondary Archive Log Location (LOGARCHMETH2)

Cómo se verifica

Método de auditoría: Comando de shell

db="${DB2DBDFT:?set DB2DBDFT to the database to audit}"; out=$(db2 get db cfg for "$db" 2>/dev/null) || exit 1; p=$(printf '%s\n' "$out" | sed -n 's/.*(LOGARCHMETH2) *= *//p' | sed 's/[[:space:]]*$//'); case "$p" in DISK:*) p=${p#DISK:} ;; *) echo compliant; exit 0 ;; esac; [ -n "$p" ] || { echo compliant; exit 0; }; [ -e "$p" ] || { echo "noncompliant: $p does not exist"; exit 0; }; w=$(find "$p" -prune \( -perm -020 -o -perm -002 \) -print); [ -z "$w" ] && echo compliant || echo "noncompliant: $p is group/world writable"

Salida esperada

compliant

Cómo se corrige

Método de corrección: Guía o parche de infraestructura

For Windows and Linux: 1. Attach to the Db2 instance. 2. Run the following command to change the secondary archive log directory, if necessary: db2 => update database configuration using logarchmeth2 <valid directory> Additional steps for Windows (assuming that the logarchmeth2 parameter includes DISK): 1. Connect to the Db2 host 2. Right-click on the secondary archive log directory 3. Choose Properties 4. Select the Security tab 5. Grant all Db2 administrator accounts the Full Control authority 6. Grant all other accounts read and execute privileges only (revoke all other privileges) Additional steps for Linux (assuming that the logarchmeth2 parameter includes DISK): 1. Connect to the Db2 host 2. Change to the secondary archive log directory 3. Change the permissions for the directory $ chmod -R 755

Verificar este host

Ejecute esto en un equipo que tenga permiso para auditar. El escaneo es de solo lectura.

tmaegis scan --target db2