Ensure File System Level encryption is enabled

Como é verificado

Método de auditoria: Comando shell

command -v lslpp >/dev/null 2>&1 || exit 1; r=compliant; for p in clic.rte.includes clic.rte.kernext clic.rte.lib clic.rte.pkcs11; do lslpp -L $p >/dev/null 2>&1 || r="$p not installed"; done; echo "$r"

Saída esperada

compliant

Como é corrigido

Método de correção: Orientação ou patch de infraestrutura

There are two pre-requisite requirements for EFS, it requires RBAC and the installation of the CLiC cryptographic fileset. The fileset is located on the expansion pack, shipped with the AIX media. Place the CLiC software into a convenient location, such as /tmp and install via: /usr/lib/instl/sm_inst installp_cmd -a -Q -d /tmp -f clic.rte -c -N -g -X -G -Y NOTE: If the software is not located in /tmp, reflect the actual location in the command above. Load the CLiC kernel extension: /usr/lib/methods/loadkclic As the EFS administrator, create the initial keystore. This is typically the root user: efsenable -a An EFS enabled filesystem can be created with the following command: chfs -v jfs2 -g <vg_name> -m <filesystem> -a size=<size> -a efs=yes To enable EFS for an existing filesystem: chfs -a efs=yes <filesystem> To encrypt a file, load your keystore via: efskeymgr -o ksh Then encrypt via: efsmgr -c AES_192_ECB -e <filename> To decrypt: efsmgr -d <filename> Further details regarding planning and implementation of EFS can be found within the IBM AIX 7.1 Infocentre: https://www.ibm.com/docs/en/aix/7.1?topic=system-efs-encrypted-file NOTE: The ... (see CIS section 4.4.2.1)

Verificar este host

Execute isto em uma máquina que você tenha permissão para auditar. A varredura é somente leitura.

tmaegis scan --target aix --level 2