Linking KeyControl with CloudControl

If you want to use the BoundaryControl feature for VMs in a Cloud VM Set or you want to link KMIP client VMs to the KMIP objects they create in the KeyControl KMIP server, you need to link KeyControl to one or more HyTrust CloudControl servers. CloudControl can then be used to configure rules and policies for the VMs in the associated Cloud VM Set while the Inventory feature tracks which client VMs go with which KMIP objects.

Figure: KeyControl KMIP Server Objects with the CloudControl Identifier

Each Cloud VM Set in KeyControl can be linked to a specific CloudControl server, allowing you to select the best CloudControl server for the VMs in each Cloud VM Set.

After the BoundaryControl feature has been enabled for a Cloud VM Set, all VMs you register with the set must be authenticated by the selected CloudControl server when they are first registered. After that, individual VMs in the set only need to be re-authenticated when they reboot or when their VMware session ID changes.

If KeyControl cannot communicate with CloudControl when it attempts to re-authenticate a VM, KeyControl tells the Policy Agent on that VM that the heartbeat has failed and it starts a two hour BoundaryControl grace period that is shared by all the VMs in the Cloud VM Set. KeyControl then tries to re-authenticate the VM with CloudControl each time the VM heartbeats during this grace period. If this grace period expires and KeyControl has still not received a response from CloudControl, then KeyControl disables access to all VMs in the Cloud VM Set that require re-authentication. For example, if KeyControl attempts to re-authenticate VM A at 4 p.m., VM B at 4:30 p.m., and VM C at 5:45 p.m., and it does not receive a response from CloudControl by 6 p.m., it immediately revokes access to all three VMs. It does not wait until 7:45 p.m. to revoke access to VM C.

After the BoundaryControl grace period has expired, all disabled VMs must be manually re-authenticted by a KeyControl Cloud Admin.

Note: If the SSL certificate for CloudControl expires or is changed, you need to create a new App Link as described below. Then, for each Cloud VM Set that uses the BoundaryControl feature, you need to change the Boundary Control property so that it points to the new App Link. For details, see Changing Cloud VM Set Properties.

Before You Begin 

  • Make sure you know the hostname or IP address of one or more HyTrust CloudControl servers to which you want to connect.
  • Make sure that the license for CloudControl has the BoundaryControl feature enabled.
  • If you want KeyControl to verify the CloudControl certificate every time it connects to CloudControl, make sure that the SSL certificate installed in CloudControl includes the entire certificate chain, starting from the root CA certificate. When SSL Verify is enabled, KeyControl expects the entire CloudControl certificate chain when it communicates with CloudControl.
  • If you are using CloudControl version 5.1 or later, establishing the connection between KeyControl and CloudControl requires a one-time password generated by a CloudControl user with AppLink Management privileges. This one-time password is valid for 10 minutes after it is generated. Make sure that you can get the password from your CloudControl administrator and enter it into KeyControl within that time.
  • If you are using CloudControl version 5.0 or 4.6, establishing the connection requires the login credentials for a CloudControl account with the ASC_BCAdmin user role.
  • Make sure that VMware Tools is installed on each VM that will be associated with the a BoundaryControl-enabled Cloud VM Set. While any VMware-supported version of the tools will work, we recommend that you keep VMware Tools up to date.

Procedure 

  1. If you are using CloudControl version 5.1 or later, log into CloudControl using an account with AppLink Management privileges and do the following:

    1. Select Configuration > App Links.
    2. On the One Time Code tab in the Select Role for App Link drop-down, select ASC_AppLinkAdmin.
    3. When you are ready to transfer the code to KeyControl, click Submit.
    4. Copy the one-time code displayed in the Code field.
  2. Log into the KeyControl webGUI using an account with Security Admin privileges.

  3. In the top menu bar click Settings.
  4. In the System Settings section, click App Links.
  5. On the App Links page, select Actions > Link HTCC.
  6. In the Create a New Link dialog box, specify the options you want to use.

  7. When you are finished, click Create.
  8. If you specified Yes for SSL Verify, KeyControl verifies the connection information and displays the CloudControl certificate if the connection can be established. Verify that the certificate is correct and that it is linked to the expected server. If is it correct, click Yes.

    If you specified No for SSL Verify, KeyControl verifies the connection information. If the CloudControl host can be contacted, KeyControl creates the App Link and automatically returns to the App Links page.

  9. If desired, repeat this procedure to add a link to another CloudControl server.

What to Do Next 

If you are enabling the BoundaryControl feature for the first time, create one or more Cloud VM Sets with the BoundaryControl feature enabled and then add the desired VMs to one of those sets. For details, see Creating a Cloud VM Set.

If you want to use this App Link for an existing Cloud VM Set that already has the BoundaryControl feature enabled, you can select it from the Boundary Control drop-down list in the Details area for the Cloud VM Set. For details, see Changing Cloud VM Set Properties.