CipherTrust Manager - Hands-On - Overview and Basic Configuration
CipherTrust Manager - Hands-On - Overview and Basic Configuration
Contents
Part 1: Overview
Prerequisites
For this exercise, you will need:
Internet connection
Access to the Thales training platform
Duration
This training course will take approximately 1.5 hours.
Objectives
In this exercise, you will:
Learn how to access CipherTrust Manager (aka: CM) from the Web GUI and CLI tools
Basic Configuration of the CM
In part two, you will learn how to log in to CipherTrust via the Web UI using a browser to perform basic
operations. Log in to CipherTrust using the SSH tool (PuTTY) or with the ksadmin user.
Note: When a new instance of CipherTrust is started for the first time, and the DHCP
service is enabled on the network, CM is automatically assigned an IP address and
basic network configurations.
Network configurations can be set up using the nmcli user.
User admin
Password Thales123!
5. Return to the session option, enter the CipherTrust IP Address and click Open. PuTTY authenticates
to the CM with a key (the key that PuTTY authenticates with, is a private key. The private key is part of
a key pair in which the public key was used to set the CM authentication).
6. Enter the ksadmin user and press Enter. This opens ksadmin cli.
2. In the left pane, select Access Management > Users tab and then click Add User on the right of the
screen.
Password Thales123!
ksctl-win-amd64.exe users
If required, you can choose to reset password in the following window:
5. In the left pane, Click Keys and then on the right of the screen, click Add Key.
Ensure the newly created Test user is selected as the key owner. Click the .
9. Under Groups name, enable Show All Groups ensure that the new Key is
part of the Key Users group.
10. Select the options Exportable and Deleteable, and then click Update at the bottom of the window.
14. Edit the nae port by clicking the three dots on the right of the protocol.
15. Under the Mode field, select No TLS, allow anonymous logins, and then click Update.
Note: During this lab hands-on, you will not use strong authentication. When preforming
a POC or customer production, use strong authentication, it can be selected from the list
below.
3. Click the CLI Guide tab, and on the right of the browser, click CLI to download the kscli tool. Save the
ZIP file on your desktop.
4. Unzip the file, the folder contains files for Windows, Mac and Linux OS’s.
5. Create a folder named ksctl on your desktop, and then copy the ksctl-win-amd64.exe file to the new
folder.
KSCTL_TIMEOUT: 30
3. Try running additional commands to view additional information with the ksctl tool.
For example:
To view the group list, run:
ksctl-win-amd64.exe --configfile config.yaml groups list
In part three, you will learn how to use the API Playground to create a Key.
User admin
Password Thales123!
4. Click Post.
Note: This authenticates you for 300 seconds to make API calls.
4. The Backup is created with the default backup key of the CM, create a new key for backup.
ksctl-win-amd64.exe --configfile config.yaml backupkeys create
1. Export the backup with the same key with which the backup was made. The –id parameter is the backup id
to be copied from the Web UI.
2. To download the backup file and run the following command (the –id parameter is the backup id).
On Windows Server 2019, open CMD and type:
cd C:\Users\administrator\Desktop\ksctl
Note: In this lab hands-on, you have only one main CM. Restore the CM to a new CM.
The key with which the backup is encrypted must be transferred to the appliance where the backup will be
restored. The backup key is required for the restore. To transfer a backup key, it must be downloaded using
the command ksctl.
5. Run the command to export the backup encryption key (ksctl command), open CMD, browse to the ksctl
folder and then run the following command:
ksctl-win-amd64.exe --configfile config.yaml backupkeys download --id a5c6eb19-
e91b-4c52-a08d-678ba1986eda --file sysbkkey.txt
A notification appears stating that a password is required to protect the file.
6. Type the password and click Enter.
7. The sysbkkey.txt is the backup file in which the keys are saved. The sysbkkey.txt file is located in the
folder that contains the ksctl application.
Note: The config.yaml file of the restore server is preconfigured with the CM restore Server
IP, User name and password.
13. Upload the backup to the CM, where it will be restored, open the CMD and type the following command:
cd C:\Users\administrator\Desktop\Training\restore ksctl
14. Click Enter. To upload the restore file and then run the command:
ksctl-win-amd64.exe --configfile config.yaml backup upload --file "backup.txt"
15. Restore the uploaded backup (the id parameter is the backup id).
ksctl-win-amd64.exe --configfile config.yaml backup restore --id "6a9af43f-
6247-481b-8a77-373554ebc16d"
16. Run the restore status command, until Status Completed is displayed.
ksctl-win-amd64.exe --configfile config.yaml backup status
Password Thales123!