Business Processes KMS Admin
"KMS Admin" provides methods for the following tasks:
-
Manage or create HSMs
-
Manage the existing HSM profiles of an HSM
-
-
Manage or create tenants
-
Manage the existing tenant users of a tenant
-
Manage the linked HSMs of a tenant as well as create new links
-
Manage a tenant’s existing HSM profiles as well as create new links with HSM profiles
-
Manage a tenant’s linked issuer certification authorities (CAs) and create new links
-
Manage the CMP configuration used by the KMS server to issue certificates
-
-
View the (certification authorities) (CAs)
-
Manage or add KMS roles
-
Edit the KMS server settings
-
Manage or add admin users
-
Manage or apply for licenses
-
Manage own account (Keycloak etc.)
The necessary identification and authentication towards the KMS Admin application is described in the following process steps:
Process steps | |
---|---|
01 |
Call the URL of the KMS-UI application with the browser, e.g. select the "Sign in" button and sign in using the admin credentials provided to you by a KMS admin (username and password, e.g. in a sealed envelope or encrypted email) (see chapter P-KMS-ADM-01 - KMS-Admin User (create, change, delete)). One possible login strategy is, for example, Keycloak. |
02 |
After a successful login, the start page ("Dashboard") is displayed. The page features various buttons and a navigation menu (sidebar), which is typical for most pages of the KMS-UI web application and the KMS Admin. |
03 |
It is recommended to change the randomly assigned username and initial password to a meaningful name and a new password during the initial login. Furthermore, the personal information (e-mail, last name, first name) should be completed. To do this, proceed as follows (when using Keycloak):
|
04 |
From any page (see step 03), the desired functionality can be selected at any time. The following steps must be performed:
The functionalities offered in the sidebar depend on the selected submenu item. Some functionalities can also be selected directly by selecting the corresponding buttons. From any page, it is also possible to go back to the dashboard by clicking the "Dashboard" button, clicking on the MTG logo, or clicking on the "KMS Admin" button. |
05 |
Other functionalities:
To use these functionalities, proceed as follows:
Alternatively, you can access the "Profile" and "Logout" functionalities from the navigation menu in the sidebar. |
06 |
Change language: To change the language of the KMS-UI web application, please select the drop-down menu in the bottom right of the footer on any page of the web application. Here you can switch between "en" for English and "de" for German. |
07 |
Search, sort and export in list views: All objects that are managed with the KMS-UI web application are displayed as lists in their corresponding "Show" view. The structure of these lists is very similar and is usually characterized by the following features:
|
P-KMS-ADM-01 - KMS-Admin User (create, change, delete)
Profile | |
---|---|
Designation |
P-KMS-ADM-01 - KMS-Admin User (create, change, delete) |
Purpose |
Only admin users are allowed to use the KMS Admin application, which provides methods for managing HSMs, tenants, roles, admin users, and HSM profiles, among other things. The description of admin user management is the subject of P-KMS-ADM-01, which specifically includes managing admin user accounts and creating additional admin users. |
Responsibility |
KMS-Admin |
Working tool(s) |
Browser, KMS-UI web application |
Precondition/ |
The KMS platform is up and running. The KMS admin is logged into the KMS-UI application with his admin user account. |
Postcondition/ |
|
Remarks |
After creating a new admin user, the initial password should be sent securely to the responsible person (e.g. via encrypted email). The current administrator should not be able to use and reset this initial password without the new administrator noticing (e.g., to prevent misuse of the new account by the approving KMS Admin). Therefore, the first time the administrator logs in with a newly created KMS Admin account, they will be prompted to change their initial password. |
Process steps | |||
---|---|---|---|
01 |
Display the list of admin users:
|
||
02 |
Create admin user:
If the process was successful, an admin user has been created. The new user’s credentials are displayed and should be written down or stored safely. |
||
03 |
Change admin user:
|
||
04 |
Delete admin user:
|
P-KMS-ADM-02 - KMS-Tenant (create, change, delete, assign KMS resources)
Profile | |
---|---|
Designation |
P-KMS-ADM-02 - KMS-Tenant (create, change, delete, assign KMS resources). |
Purpose |
The tenant is a logical entity in the KMS platform that separates the managed key material into its own key domains. Tenant management, e.g., creating, modifying, and deleting tenants, and assigning and revoking tenant KMS resources (e.g., KMS tenant users, tenant HSM profiles, HSMs) is the responsibility of the admin. The description of tenant management is the subject of P-KMS-ADM-02. |
Responsibility |
KMS-Admin |
Working tool(s) |
Browser, KMS-UI web application |
Precondition/ |
The KMS platform is up and running. The KMS admin is logged into the KMS-UI application with his admin user account. HSM (see chapter P-KMS-ADM-03 - HSM object (create, change, delete)) is configured. |
Postcondition/ |
|
Remarks |
After creating a tenant when clicking "Existing Tenant-Users" → "Edit" action, you will be offered to create at least two new tenant users with the role KMS-Tenant (see steps 05). The access data (UserID and password) generated in this process for access to the KMS Tenant application must be transmitted confidentially by the admin, e.g. in a sealed envelope or in an encrypted e-mail, to the persons responsible for the tenant. This is an organizational process that is carried out individually with the tenants (clients) by the platform operator. With these credentials, the tenant user can then use the KMS Tenant application to configure and edit tenant-specific resources (see KMS012). At least two tenant users are always created. It is important that the tenant is set to "Active" status so that all the functions of the "KMS Tenant" are available to the tenant users. An HSM profile is created for a tenant (see chapter P-KMS-ADM-04 - KMS-Tenant HSM-Profiles (create, delete)). A tenant cannot be deleted until all links to the resources it uses (HSMs, HSM profiles, tenant users) have been deleted. Deleting a tenant is an action that cannot be undone. |
Process steps: KMS-Tenant (create, change, delete, assign KMS resources)
Process steps | |||
---|---|---|---|
01 |
Display the list of tenants:
|
||
02 |
Create Tenant:
The tenant has been created, but more configuration needs to be done to prepare the tenant for use:
|
||
03 |
Change Tenant:
|
||
04 |
Create tenant user:
|
||
05 |
Delete KMS tenant user:
|
||
06 |
Delete tenant:
|
||
07 |
Attach or detach tenants with HSM:
|
||
08 |
Attach and detach Issuer CAs:
|
||
09 |
Create a CMP configuration:
CMP Server
CMP server TLS
Signer
Click "Create CMP configuration" to save the CMP configuration. |
||
10 |
Edit a CMP configuration:
Edit CMP Server
Click "Save" to update the CMP configuration. Edit CMP Root Certificates
|
||
11 |
Delete a CMP configuration:
|
||
12 |
Edit audited KMIP operations:
|
P-KMS-ADM-03 - HSM object (create, change, delete)
Profile | |
---|---|
Designation |
P-KMS-ADM-03 - HSM object (create, change, delete) |
Purpose |
HSMs serve as secure containers for private cryptographic key material. The KMS platform can manage multiple HSMs and then use them for cryptographic functions and tenant private key storage. The KMS admin must make the HSM objects known to the platform, modify them, and delete them if necessary. They must work closely with the HSM admin. The description of the management of HSM objects is the subject of P-KMS-ADM-03. |
Responsibility |
KMS-Admin |
Working Tool(s) |
Browser, KMS-UI Web Application |
Precondition/ |
The KMS platform is up and running. The KMS admin is logged into the KMS-UI application with his admin user account. |
Postcondition/ |
|
Remarks |
None |
Process steps: HSM object (create, change, delete)
Process steps | |||
---|---|---|---|
01 |
Display the list of HSMs:
|
||
02 |
Create HSM object:
|
||
03 |
Change HSM object:
|
||
04 |
Delete HSM object:
|
P-KMS-ADM-04 - KMS-Tenant HSM-Profiles (create, delete)
Profile | ||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Designation |
P-KMS-ADM-04 - KMS-Tenant HSM-Profiles (create, delete) |
|||||||||||||||||||||||||
Purpose |
HSM profiles are used to manage the relationships between clients and their assigned HSMs, where the clients' KEKs are stored in a protected manner. The "Key Management" and "Key Usage" users set up by the HSM admin for the client on the HSM are stored in the HSM profile, including their authentication information (credentials), in AES-encrypted form. The HSM users to be entered when an HSM profile is generated must first be created by the HSM admin in the HSMs (and HSM-HA, if installed). They are stored together with their credentials in the KMS database within the HSM profile object encrypted with a Data-Encryption-Key (DEK). The DEK itself is protected by the MTG Secrets Protection Manager workflow (see document Secrets Protection Business Processes for details). The DEK can be used to decrypt the HSM credentials stored in the HSM profile so that KMS applications can log on to the HSM. Key management operations can then be performed on the HSM by the KMS applications (e.g., key generation for the client). The description of the management of KMS-Tenant HSM profiles is the subject of P-KMS-ADM-04. |
|||||||||||||||||||||||||
Responsibility |
KMS-Admin |
|||||||||||||||||||||||||
Working tool(s) |
Browser, KMS-UI web application |
|||||||||||||||||||||||||
Precondition/ |
The KMS platform is up and running. The KMS admin is logged into the KMS-UI application with his admin user account. Tenants (see chapter P-KMS-ADM-02 - KMS-Tenant (create, change, delete, assign KMS resources)) and HSMs (see chapter P-KMS-ADM-03 - HSM object (create, change, delete)) are set up. In an Utimaco HSM, the following HSM users have been created for the KMS client with the name <UserId> by the HSM admin (recommendation).
The KMS Admin must know this authentication information (username, password) of the client and enter it in the corresponding mask fields when creating an HSM profile. |
|||||||||||||||||||||||||
Postcondition/ |
|
|||||||||||||||||||||||||
Remarks |
An HSM Profile object cannot be modified after it has been created. It is only possible to delete the object. The creation of the users depend on the chosen HSM Type. |
Process steps: KMS-Tenant HSM-Profiles (create, delete)
Process steps | |
---|---|
01 |
Display the list of HSM profiles of a tenant:
|
02 |
Link tenant with HSM profile:
If the operation was successful, an HSM profile will be created. |
03 |
Show HSM profile object:
The following information is displayed:
|
04 |
Delete HSM profile object:
|
P-KMS-ADM-05 - CAs (show, delete)
Profile | |
---|---|
Designation |
P-KMS-ADM-05- CAs (show, delete) |
Purpose |
For a better overview, MTG KMS-UI provides an overview of attached issuer certification authorities (Issuer CAs). These CAs have been generated by the Mini-CA and automatically attached to MTG KMS. |
Responsibility |
KMS-Admin |
Working tool(s) |
Browser, KMS-UI web application |
Precondition/ |
The KMS platform is up and running. The KMS admin is logged into the KMS-UI application with his admin user account. |
Postcondition/ |
None |
Remarks |
None |
Edit steps: CAs (show, delete)
Process steps | |
---|---|
01 |
Display the list of connected CAs:
|
02 |
Display the CA details:
The following information is displayed for the CA:
|
03 |
Delete CA:
|
P-KMS-ADM-06 - KMS Roles (create, change, delete)
Profile | |
---|---|
Designation |
P-KMS-ADM-06 - KMS Roles (create, change, delete) |
Purpose |
The KMS Admin can use the KMS Admin application to manage KMS roles. The description of the management of KMS roles is the subject of P-KMS-ADM-06. This includes the creation, modification and deletion of KMS roles. |
Responsibility |
KMS-Admin |
Working tool(s) |
Browser, KMS-UI web application |
Precondition/ |
The KMS platform is up and running. The KMS admin is logged into the KMS-UI application with his admin user account. |
Postcondition/ |
|
Remarks |
None |
Process steps: KMS Roles (create, change, delete)
Process steps | |
---|---|
01 |
Display the list of KMS roles:
|
02 |
Create KMS role:
If the operation was successful, a KMS role has been created and the details of this role are displayed. |
03 |
Change KMS role:
|
04 |
Delete KMS role:
|
P-KMS-ADM-07 - Settings (edit)
Profile | |
---|---|
Name |
P-KMS-ADM-07- Settings (edit) |
Purpose |
MTG KMS allows the administrator to edit the settings of the KMS server. |
Responsibility |
KMS-Admin |
Working tool(s) |
Browser, KMS-UI web application |
Precondition/ |
The KMS platform is up and running. The KMS admin is logged into the KMS-UI application with his admin user account. |
Postcondition/ |
None |
Remarks |
None |
Process steps: Settings (edit)
Process steps | |
---|---|
01 |
Edit cron expressions:
|
02 |
Switch to debug mode for tracing:
|
03 |
Enable KMIP digest generation:
|
04 |
Configure the email server for license notifications:
|
05 |
Set the SNMP server for license notifications:
|
P-KMS-ADM-08 - Licenses (request, import)
Profile | |
---|---|
Designation |
P-KMS-ADM-08 - Licenses (request, import) |
Purpose |
MTG KMS allows the administrator to request and import KMS application licenses. |
Responsibility |
KMS-Admin |
Working tool(s) |
Browser, KMS-UI web application |
Precondition/ |
The KMS platform is up and running. The KMS admin is logged into the KMS-UI application with his admin user account. |
Postcondition/ |
|
Remarks |
At least one valid license is required for the KMS application to run correctly. Licenses are checked when the KMS server is started for the first time and every 7 days thereafter. |
Process steps: Licenses (request, import)
Process steps | |
---|---|
01 |
Display the list of licenses:
|
02 |
Request a license:
|
03 |
Import a license:
|
04 |
Download a licence request:
|
05 |
Delete a license or a license application:
|