Turn Off ALLOW_KEY_INSERT_WITHOUT_KEYSTORE_BACKUP

How it is checked

Audit method: Manual review

This recommendation cannot be checked automatically. A scan lists it with these instructions when you pass --include-manual.

Check that ekeystore.cfg file that's being used has the setting turned OFF. ALLOW_KEY_INSERT_WITHOUT_KEYSTORE_BACKUP=false

How it is fixed

Fix method: Guidance or infrastructure patch

$ cat ekeystore.cfg VERSION=1 PRODUCT_NAME=Luna ALLOW_KEY_INSERT_WITHOUT_KEYSTORE_BACKUP=false LIBRARY=/usr/safenet/lunaclient/luna6.1/lib/libCryptoki2_64.so SLOT_LABEL=DB2Partition NEW_OBJECT_TYPE=PRIVATE KEYSTORE_STASH=/home/db2inst1/sqllib/security/pkcs11.sth For maximum security, turn the setting off and create the keys outside of Db2. This way you will also be able to manage the labeling scheme across the Db2 instances and prevent name collision between different databases.