Entrust KeyControl

Entrust KeyControl is a proprietary KMS which KES supports using for storing secrets.

Prerequisites

This procedure was written and tested against Entrust KeyControl v10.1. The provided instructions may work against other KeyControl versions. This procedure assumes you have prior experience with Entrust products and have followed their documentation, best practices, and other published materials in deploying the KeyControl service.

For instructions to set up an Entrust KeyControl cluster, refer to the Entrust documentation:

• Entrust KeyControl on AWS
• Entrust KeyControl on-premises

Set up Entrust KeyControl

Before setting up the KES Server, complete the following sections in KeyControl to add a new Vault, a Box, and one or more Users.

Create a new Vault

Log in to your KeyControl cluster with a user that has root-level permissions (for example, secroot) and create a new PASM vault.

Make entries similar to the following:

• Type: PASM

• Name: minio

• Description: Optional additional information for the vault, or leave blank.

• Admin Name: User name to to manage the vault.

  Note: This user has complete access to the Vault.

• Admin Email: Email address for the vault administrator

  Note: KeyControl sends a one-time password to this email address to access the vault. You need this password in the next step.

Make other required entries as per KeyControl or your own guidelines. You can set the Name and Description to be more specific to your AIStor deployment or according to your own guidelines.

Access the new Vault

1. Access the Vault URL.

   This URL should be in the email with the one-time password. You can also find the URL from the Vault tab in KeyControl.

2. Use the admin user name and the one-time password sent by email to access the Vault.

Create a new Box

KeyControl stores secrets in a Box inside the Vault. Add a Box to store your secrets.

Follow the prompts and make entries similar to the following:

• Name: A descriptive name for the box, such as the AIStor Tenant name.
• Description: Optional additional information about the secrets in the box.
• Secret Expiration: leave blank.
• Secret Checkout Duration: leave blank.
• Secret Rotation Duration: leave blank.

Make other required entries as per KeyControl or your own guidelines.

Attach the ‘Vault User’ role policy

KeyControl uses Role-Based Access Control. Add a policy with the Vault User role and attach the policy to the user account used by KES.

Follow the prompts and make entries similar to the following:

• Name: KES Service.
• Description: Optional longer description for the policy.
• Role: Vault User Role.
• Users: The KeyControl account KES uses to access keys.
• Box: Select the box you added in the previous step from the dropdown.
• Secrets: All Secrets.

Make other required entries as per KeyControl or your own guidelines.

KES Server Setup

After creating a new vault, box inside the vault, and the user access policy in KeyControl, you can set up the KES server.

Generate KES server private key & certificate

Generate a TLS private key and certificate for your KES server. If you already have either a TLS certificate you want to use for your KES server or a working KES server, you can skip this step.

The following command generates a new TLS private key (private.key) and a self-signed X.509 certificate (public.crt) issued for the IP 127.0.0.1 and DNS name localhost.

kes identity new --key private.key --cert public.crt --ip "127.0.0.1" --dns localhost

The output resembles the following:

Your API key:

   kes:v1:APvbt/zbiewXNB+EwciOT+I21peq0odFYCwkJX8mMCxM

This is the only time it is shown. Keep it secret and secure!

Your Identity:

   1d1f89ad528a3bbb8fd64252d443c993f5a4d679b074d5bad49785e02ec38199

The identity is not a secret. It can be shared. Any peer
needs this identity in order to verify your API key.

The generated TLS private key is stored at: private.key
The generated TLS certificate is stored at: public.crt

The identity can be computed again via:

    kes identity of kes:v1:APvbt/zbiewXNB+EwciOT+I21peq0odFYCwkJX8mMCxM
    kes identity of public.crt

Generate a new API key

The client application requires credentials in order to access the KES server. The following command generates a new API key.

kes identity new

The resulting key resembles:

Your API key:

   kes:v1:AOlQZJRMYZeOioGk0ubYBMSFt1w6Hh1QZl3zG4PQxK/g

This is the only time it is shown. Keep it secret and secure!

Your Identity:

   eb559798a2fbcc3efbf036bed11108116e63f293324abdfe7574249ef5e56b36

The identity is not a secret. It can be shared. Any peer
needs this identity in order to verify your API key.

The identity can be computed again via:

    kes identity of kes:v1:AOlQZJRMYZeOioGk0ubYBMSFt1w6Hh1QZl3zG4PQxK/g

Configure the KES Server

Create the KES server configuration file: config.yml. Make sure that the identity in the policy section matches your API key identity.

address: 0.0.0.0:7373 # Listen on all network interfaces on port 7373

admin:
  identity: disabled  # We disable the admin identity since we don't need it in this guide 
   
tls:
  key: private.key    # The KES server TLS private key
  cert: public.crt    # The KES server TLS certificate
   
policy:
  my-app: 
    allow:
    - /v1/key/create/my-key*
    - /v1/key/generate/my-key*
    - /v1/key/decrypt/my-key*
    identities:
    - eb559798a2fbcc3efbf036bed11108116e63f293324abdfe7574249ef5e56b36 # Use the identity of your API key
   
keystore:
     entrust:
       keycontrol:
         endpoint: "https://keycontrol.my-org.com"    # Use your KeyControl instance endpoint.
         vault_id: ""                                 # The Vault ID - e.g: "e30497c1-bff7-4e81-beb7-fb35c4b7410c".
         box_id:   ""                                 # The Box name or ID - e.g: "tenant-1".
         credentials:
           username: ""                               # KeyControl username - e.g: "kes-tenant-1@my-org.com".
           password: ""                               # Password of KeyControl user

Start the KES Server

Use the YAML file you created to start a KES server instance.

kes server --config config.yml --auth off

sudo setcap cap_ipc_lock=+ep $(readlink -f $(which kes))

kes server --config config.yml --auth off --mlock

KES CLI Access

1. Set the MINIO_KES_SERVER Endpoint.

   The following environment variable specifies the server the KES CLI should talk to:

   export MINIO_KES_SERVER=https://127.0.0.1:7373

2. Define the Client Credentials.

   The following environment variable sets the access credentials the client uses to talk to a KES server. Use the API key you generated in Generate a new API key. Its identity is the one you placed in the policy, so the CLI authenticates as that policy’s client:

   export MINIO_KES_API_KEY='kes:v1:AOlQZJRMYZeOioGk0ubYBMSFt1w6Hh1QZl3zG4PQxK/g'

3. Test the Configuration.

   Perform any API operation allowed by the policy defined in the KES server configuration file.

   For example, create a key:

   kes key create my-key-1

   Use the key to generate a new data encryption key:

   $ kes key dek my-key-1
   {
     plaintext : UGgcVBgyQYwxKzve7UJNV5x8aTiPJFoR+s828reNjh0=
     ciphertext: eyJhZWFkIjoiQUVTLTI1Ni1HQ00tSE1BQy1TSEEtMjU2IiwiaWQiOiIxMTc1ZjJjNDMyMjNjNjNmNjY1MDk5ZDExNmU3Yzc4NCIsIml2IjoiVHBtbHpWTDh5a2t4VVREV1RSTU5Tdz09Iiwibm9uY2UiOiJkeGl0R3A3bFB6S21rTE5HIiwiYnl0ZXMiOiJaaWdobEZrTUFuVVBWSG0wZDhSYUNBY3pnRWRsQzJqWFhCK1YxaWl2MXdnYjhBRytuTWx0Y3BGK0RtV1VoNkZaIn0=
   }

Using KES with a AIStor Server

AIStor Server requires KES to enable server-side data encryption.

See the KES for AIStor instruction guide for additional steps needed to use your new KES Server with a AIStor Server.

Configuration References

The following section describes the Key Encryption Service (KES) configuration settings to use Entrust KeyControl as the root KMS to store external keys, such as the keys used for Server-Side Encryption on a AIStor Server.

address: 0.0.0.0:7373
root: ${ROOT_IDENTITY}

tls:
  key: kes-server.key
  cert: kes-server.cert

api:
  /v1/ready:
    skip_auth: false
    timeout:   15s

policy:
  minio-server:
    allow:
    - /v1/key/create/*
    - /v1/key/generate/*
    - /v1/key/decrypt/*
    - /v1/key/bulk/decrypt
    - /v1/key/list/*
    - /v1/status
    - /v1/metrics
    - /v1/log/audit
    - /v1/log/error
    deny:
    - /v1/key/generate/my-app-internal*
    - /v1/key/decrypt/my-app-internal*
    identities:
    - ${MINIO_IDENTITY}

  my-app:
    allow:
    - /v1/key/create/my-app*
    - /v1/key/generate/my-app*
    - /v1/key/decrypt/my-app*
    deny:
    - /v1/key/generate/my-app-internal*
    - /v1/key/decrypt/my-app-internal*
    identities:
    - df7281ca3fed4ef7d06297eb7cb9d590a4edc863b4425f4762bb2afaebfd3258
    - c0ecd5962eaf937422268b80a93dde4786dc9783fb2480ddea0f3e5fe471a731

keys:
  - name: "minio-encryption-key-alpha"
  - name: "minio-encryption-key-baker"
  - name: "minio-encryption-key-charlie"

cache:
  expiry:
    any: 5m0s
    unused: 20s
    offline: 0s

log:

  # Log error events to STDERR. Valid values are "on" or "off". 
  # Default is "on".
  error: on

  # Log audit events to STDOUT. Valid values are "on" and "off". 
  # Default is "off".
  audit: off

keystore:
  entrust:
    # https://www.entrust.com/digital-security/key-management/keycontrol
    keycontrol:
      endpoint: "" 
      vault_id: "" 
      box_id:   "" 
      credentials:
        username: ""  
        password: ""  
      tls:
        ca: ""

References

• Server API Doc
• Go SDK Doc
• Entrust KeyControl Documentation