Chapter 8. Enhancing security with the kernel integrity subsystem

Procedure

1. Prepare your system to enable IMA and EVM:

   1. Add the following kernel command line parameters:

      # grubby --update-kernel=/boot/vmlinuz-$(uname -r) --args="ima_appraise=fix ima_appraise_tcb evm=fix"

      Copy to Clipboard Toggle word wrap

      The command enables IMA and EVM in the fix mode for the current boot entry and allows users to gather and update IMA measurements.

      The ima_appraise_tcb kernel command line parameter ensures that the kernel uses the default Trusted Computing Base (TCB) measurement policy and the appraisal step. The appraisal step forbids access to files whose prior and current measurements do not match.

   2. Reboot for the changes to take effect.

   3. Optionally, verify that the kernel command line includes the new parameters:

      # cat /proc/cmdline
      BOOT_IMAGE=/vmlinuz-3.10.0-1136.el7.x86_64 root=/dev/mapper/rhel-root ro crashkernel=auto spectre_v2=retpoline rd.lvm.lv=rhel/root rd.lvm.lv=rhel/swap rhgb quiet LANG=en_US.UTF-8 ima_appraise=fix ima_appraise_tcb evm=fix

      Copy to Clipboard Toggle word wrap

2. Create and set a public and private keypair for EVM:

   1. Create a new keyring for EVM:

      # evm_kr_id=$(keyctl newring _evm @u)

      Copy to Clipboard Toggle word wrap

      The command creates the _evm keyring and attaches it to the @u system user keyring. Then, the keyring ID of _evm is assigned to the evm_kr_id variable for more convenient handling in the future.

   2. Optionally, view the newly created keyring:

      # keyctl show
      Session Keyring
      1025767139 --alswrv   0     0  keyring: _ses
      548660789 --alswrv   0 65534   \_ keyring: _uid.0
      456142548 --alswrv   0     0       \_ keyring: _evm

      Copy to Clipboard Toggle word wrap

   3. Create a directory for keys:

      # mkdir -p /etc/keys/

      Copy to Clipboard Toggle word wrap

   4. Generate a 1024-bit RSA private key into the /etc/keys/privkey.pem file:

      # openssl genrsa -out /etc/keys/privkey.pem 1024
      Generating RSA private key, 1024 bit long modulus
      .......++++++
      ...++++++
      e is 65537 (0x10001)

      Copy to Clipboard Toggle word wrap

   5. Use the previously created /etc/keys/privkey.pem private key to derive a corresponding RSA public key into the /etc/keys/pubkey.pem file:

      # openssl rsa -pubout -in /etc/keys/privkey.pem -out /etc/keys/pubkey.pem
      writing RSA key

      Copy to Clipboard Toggle word wrap

   6. Import the public key into the dedicated EVM keyring:

      # evmctl import --rsa /etc/keys/pubkey.pem $evm_kr_id
      1054989579

      Copy to Clipboard Toggle word wrap

      The command imports the /etc/keys/pubkey.pem public key into the _evm keyring. The _evm keyring is then attached to the kernel keyring. The key serial number is on the second line of the previous example.

   7. Optionally, view the newly imported key:

      # keyctl show
      Session Keyring
      1025767139 --alswrv   0     0  keyring: _ses
      548660789 --alswrv   0 65534   \_ keyring: _uid.0
      456142548 --alswrv   0     0       \_ keyring: _evm
      1054989579 --alswrv   0     0           \_ user: FA0EF80BF06F80AC

      Copy to Clipboard Toggle word wrap
      Note

      This asymmetric key pair can be used to digitally sign the contents of an extended attribute of a file using the evmctl sign command. The extended attribute is later verified by the kernel.

   8. Create a kernel master key to protect the EVM key:

      # dd if=/dev/urandom bs=1 count=32 2>/dev/null | keyctl padd user kmk-user @u

      Copy to Clipboard Toggle word wrap

      The kernel master key (kmk) is kept entirely in the kernel space memory. The 32-byte long value of the kernel master key kmk is generated from random bytes from the /dev/urandom file and placed in the user (@u) keyring.

3. Create an encrypted EVM key based on the kmk key:

   # keyctl add encrypted evm-key "new user:kmk 64" @u
   351426499

   Copy to Clipboard Toggle word wrap

   The command uses kmk to generate and encrypt a 64-byte user key (named evm-key) and places it in the user (@u) keyring. The key serial number is on the second line of the previous example.

   Important

   It is necessary to name the user key evm-key because that is the name the EVM subsystem expects and works with.

4. Activate EVM:

   # echo 1 > /sys/kernel/security/evm

   Copy to Clipboard Toggle word wrap

5. Verify that EVM has been initialized:

   dmesg | tail -1
   […​] EVM: initialized

   Copy to Clipboard Toggle word wrap

Procedure

1. Create a test file:

   # echo <Test_text> > test_file

   Copy to Clipboard Toggle word wrap

2. Sign the file with the private key:

   # evmctl sign --imahash --key /etc/keys/privkey.pem test_file

   Copy to Clipboard Toggle word wrap

   By creating a hash of the test_file file, IMA verifies that the file remains is uncorrupted. EVM ensures that the IMA hash is genuine by signing the hash content that is stored in the extended attribute of test_file.

3. Optionally, check the extended attributes of the signed file:

   # getfattr -m . -d test_file
   file: test_file
   security.evm=0sAwICztVdCQCAZLtD7qAezGl8nGLgqFZzMzQp7Fm1svUet2Hy7TyI2vtT9/9ZfBTKMK6Mjoyk0VX+DciS85XOCYX6WnV1LF2P/pmPRfputSEq9fVD4SWfKKj2rI7qwpndC1UqRX1BbN3aRUYeoKQdPdl6Cz+cX4d7vS56FJkFhPGlhq/UQbBnd80=
   security.ima=0sAfgqQ5/05X4w/ltZEfbogdI9+KM5
   security.selinux="unconfined_u:object_r:admin_home_t:s0"

   Copy to Clipboard Toggle word wrap

   This example output shows extended attributes related to SELinux and the IMA and EVM hash values. EVM actively adds a security.evm extended attribute and detects any offline tampering to xattrs of other files such as security.ima that are directly related to file content integrity. The value of the security.evm field is in Hash-based Message Authentication Code (HMAC-SHA1), which was generated with the private key.