KeyControl Audit Messages
There are many audit messages produced by KeyControl. Many of these are informative and require no action. In the tables below, we list many of the audit messages and show:
- Whether an Alert is also generated.
- The severity (L=Low, M=Medium, H=High).
- What the resolution is if any action should be taken.
-
In the Message column, a %s represents a string value. For example, in the following message:
Added user %s to group %s
The actual message will be displayed with the name of the user and group, for example:
Added user fred to group IT
|
Msg ID |
Message |
Severity |
Alert? |
Description |
Resolution |
|---|---|---|---|---|---|
| 1 | System License installed. | L | False | A new license has been uploaded and installed. | |
| 2 | Begin System Initialization | L | False | ||
| 3 | Created group %s | M | False | The specified admin group has just been created. | |
| 4 | Created Domain %s | L | False | This message appears during initialization of the first KeyControl node. | |
| 5 | Added user %s to group %s | M | False | The user shown has been added to the specified admin group. | |
| 6 | Expired password for user %s | H | False | A password has expired for the specified user. | The specified user needs to log into the GUI and change his/her password. |
| 7 | User %s logged out from ipaddr %s | L | False | The specified user has just logged out from the IP address shown. | |
| 8 | Changed following attributes for user Security Administrator :- Password, Password Expiration Date, Password History List | M | False | One or more of the listed attributes has been changed for the user. | |
| 9 | Changed SMTP Auth Settings | M | False | Email settings have been modified. | |
| 10 | EKS has been removed, not destroying old admin keypair | M | False | Permission to use External Key Store has been removed. The old Admin Key was NOT removed on the EKS to allow restoration of older backups. | Informational only. Restore or add new access if so desired. |
| 11 | Regenerated Admin Key. The generation count of this key is %s. Reason: %s | H | True | ||
| 12 | Created Cloud VM Set %s | L | False | ||
| 13 | Could not create Cloud VM Set %s, HTCC server connection not configured | M | False | ||
| 14 | Masterkey Recovered on node %s | H | True | ||
| 15 | User %s logged in from ipaddr %s | L | False | The specified user has just logged in from the IP address shown. | |
| 16 | Repeated login failures for %s from ipaddr %s | H | True | There have been a succession of login failures for the specified user. | A security admin should check whether the correct user has been trying to log in or not. |
| 17 | Account disabled for %s due to repeated login failures | H | True | The number of failed login attempts has reached the maximum allowed value. | A security admin needs to reset the account to enable access. |
| 18 | Server registration failed -- No license Installed | H | True | ||
| 19 | Attempt to register a new %s server "%s" failed -- licensed limit reached. | H | True | The number of KeyControl servers is already at the limit imposed by the license. An attempt is being made to another another node. | A new license will be required before the number of nodes in the cluster can be extended. Please contact hytrust.support@entrust.com |
| 20 | Storage Pool %s Filestore %s on server %s is low on space. | H | True | ||
| 21 | Changed following Settings :- %s | M | False | ||
| 22 | Changed following attributes for group %s :- %s | M | False | One or more of the listed attributes has been changed for the group shown. | |
| 23 | Virtual Machine %s authenticated | L | False | A VM has registered or re-authenticated. | This message is in response to direct admin actions. No action is required. |
| 24 | Virtual Machine %s created in group %s | L | False | ||
| 25 | Removed Server %s from Cloud %s | L | False | ||
| 26 | Created Cluster Info %s | L | False | ||
| 27 | Removed Cluster Info %s | L | False | ||
| 28 | Activated account for user %s | M | False | A user's account has been activated. | |
| 29 | Disabled account for user %s | H | False | A user's account has been disabled. | A security admin should check to see if the account should be enabled again. |
| 30 | Created user %s | M | False | The specified user has been created. | |
| 31 | Deleted user %s | M | False | The specified user has been deleted. | |
| 32 | Renamed user %s to %s | L | False | A username has been modified. | |
| 33 | Deleted group %s | L | False | The specified groups has been deleted. | |
| 34 | Renamed group %s to %s | L | False | An admin group has been renamed. | |
| 35 | Removed user %s from group %s | M | False | The specified user has been removed from the group shown. | |
| 36 | Using EKS for MasterKey protection | M | False | An External Key Store has been configured to protect the Admin Key. | |
| 37 | Admin Key regeneration failed. Failed to use external KMIP Server for MasterKey protection | M | True | An External Key Store has been configured to protect the Admin Key but access was not allowed for keypair creation. | EKS denied access to create/retrieve an RSA keypair. Please check KMIP settings and configuration. |
| 38 | Could not register to HTCC, htcc server, password and login must be specified | H | False | ||
| 39 | Could not register to HTCC %s: HTCC login failed | H | False | ||
| 40 | Could not register to HTCC %s. Please check user privileges and Boundary Control License on HTCC | H | False | ||
| 41 | Successfully registered with HTCC Server %s | M | False | ||
| 42 | Keyid %s has %s | H | True | Keyid has expired and/or rotated. Keys only expire if a Cloud Admin has explicitly set them to expire. | |
| 43 | The Key for disk %s Virtual Machine %s has %s | H | True | A key for the specified VM has either expired or been rotated. Keys only expire or rotate if a Cloud Admin has explicitly set them to expire or rotate. | |
| 44 | Key in VMSet %s on VMV %s has %s | M | True | ||
| 45 | Changed following KeyControl cluster settings :- %s | M | False | The name of the cluster has been modified. | |
| 46 | Deleted Domain %s | M | True | ||
| 47 | Changed following KPS Settings :- %s | M | False | ||
| 48 | Changed following VS Appliance Settings :- %s | M | False | ||
| 49 | Unknown pool %s appeared on VMV, destroying... | M | True | ||
| 50 | Changed following Storage Pool Settings :- %s | M | False | ||
| 51 | Changed following attributes of filestore %s :- %s | M | False | ||
| 52 | Changed following settings for Cluster Info %s :- %s | M | False | ||
| 53 | Coretrace Server %s, changed following attributes :- %s | M | False | ||
| 54 | Changed following settings for Cloud VM Set %s :- %s | M | False | ||
| 55 | Cloud VM Set %s changed group ownership from %s to %s. | H | False | ||
| 56 | Deleted Cloud VM Set %s | M | False | ||
| 57 | Cloud VM Set %s: added keyid %s using %s cipher | H | False | A VM user has explicitly requested creation of a KeyID using the specified cipher. | |
| 58 | Cloud VM Set %s: Virtual Machine %s removed keyid %s | M | False | A VM user has explicitly requested deletion of the specified KeyID. It has been removed from the specified Cloud VM. | |
| 59 | Cloud VM Set %s: updated keyid %s | L | False | The KeyID description was changed. | |
| 60 | Cloud VM Set %s: Virtual Machine %s attempted to fetch inactive keyid %s | M | False | The KeyID shown has been revoked but an attempt was made to fetch it. | The cloud admin who owns the key should determine whether access should be reinstated or not. |
| 61 | Cloud VM Set %s: Virtual Machine %s attempted to fetch expired keyid %s | M | False | An attempt has been made to fetch an expired KeyID. | The cloud admin who owns the key should determine whether access should be reinstated or not. This is only possible if the KeyID was set to 'No use?' on expiration. |
| 62 | Cloud VM Set %s: Virtual Machine %s fetched keyid %s | M | False | A request has been made to access the specified KeyID. | |
| 63 | Revoked permission for keyid %s | M | True | KeyID is currently revoked. It must be activated before use. | The cloud admin who owns the key should determine whether access should be reinstated or not. |
| 64 | Granted permission for keyid %s | H | True | KeyID has been activated after having been previously revoked. | |
| 65 | Cloud VM Set %s keyid %s updated - description %s | L | False | The description field for the specified KeyID has been updated. | |
| 66 | Cloud VM Set %s keyid %s updated - key expires on %s, onexpiry %s | M | False | The expiration date and effect on expiration for the specified KeyID have been updated. | |
| 67 | Cloud VM Set %s Keyid %s has expired | M | True | An expiration date has been hit for the specified KeyID | The owning cloud admin should verify that the KeyID should be no longer used. |
| 68 | Keyid %s has expired | M | True | A request to access an expired KeyID has been made. | The owning cloud admin should verify that the KeyID should be no longer used. |
| 69 | The Key for keyid %s in Cloud VM Set %s expires in %d day(s). Please extend the key life. | M | True | A KeyID is about to expire. | The owning cloud admin should verify that the KeyID should be expire and change the date if not. |
| 70 | Unable to check keyid %s | M | False | An error occurred while attempting to check properties of KeyID. | An internal error occurred while checking expiration/rotation properties for specific keyid. Informational only, keyid will be checked again. |
| 71 | Cloud VM Set %s: added fsid %s using %s cipher | M | False | ||
| 72 | Cloud VM Set %s: Virtual Machine %s removed fsid %s | M | False | ||
| 73 | Cloud VM Set %s: Virtual Machine %s updated fsid %s | M | False | ||
| 74 | Revoked permission for fsid %s | M | True | ||
| 75 | Granted permission for fsid %s | M | True | ||
| 76 | Cloud VM Set %s fsid %s updated - key expires on %s, onexpiry %s | M | False | ||
| 77 | Cloud VM Set %s Fsid %s has expired | M | True | ||
| 78 | Properties changed for VMSet %s on server %s (%s) | M | False | ||
| 79 | Virtual Machine %s, changed following attributes: %s | M | False | ||
| 80 | Deleted Virtual Machine %s | L | True | ||
| 81 | Deleted Certificate %s | L | False | An unused certificate was deleted | |
| 82 | The Virtual Machine %s, could not be checked for geo-location boundary. HTCC login failed | H | True | ||
| 83 | The Virtual Machine %s, is not in the geo-location boundary. Key access is denied | H | True | ||
| 84 | The Virtual Machine %s, is in the geo-location boundary. Key access is granted | M | True | ||
| 85 | Added Virtual Machine %s, authentication complete | L | True | A VM has completed registration. | This message is in response to direct admin actions. No action is required. |
| 86 | Added Virtual Machine %s, authentication pending | M | True | A VM has a registration request pending. | The cloud admin needs to complete authentication in the KeyControl GUI. |
| 87 | Removed Server %s from Cloud %s | L | False | ||
| 88 | Renamed Server %s to %s | L | False | ||
| 89 | Virtual Machine %s re-connected, authentication pending | H | True | A VM has a re-authorization request pending. | The cloud admin needs to complete re-authorization in the KeyControl GUI. |
| 90 | Revoked permissions for Virtual Machine %s | M | False | ||
| 91 | Re-authenticated Virtual Machine %s from KPS | M | False | A VM has a re-authorized. | This message is in response to direct admin actions. No action is required. |
| 92 | Virtual Machine %s added disk %s | L | False | A new disk has been added to the specified VM. | |
| 93 | Virtual Machine %s removed disk %s | L | True | A disk has been removed from the specified VM. | |
| 94 | Virtual Machine %s : disk %s renamed to %s | L | False | ||
| 95 | Virtual Machine %s attempted to fetch key for inactive disk %s. %s | L | False | If a disk is not active, no keys will be delivered. | |
| 96 | Virtual Machine %s attempted to fetch expired key for disk %s. %s | H | False | If a key has expired an attempt by a VM to fetch the key will fail. | The cloud admin should determine whether the expiration date should be extended. This does not apply to shredded keys. |
| 97 | Virtual Machine %s fetched key for disk %s. %s | L | False | A key for the specified disk has been requested by the VM shown. | |
| 98 | Virtual Machine %s created key for disk %s using %s cipher | L | False | A disk has been encrypted. The type of cipher is shown. | |
| 99 | Virtual Machine %s revoked permission for disk %s | M | True | ||
| 100 | Virtual Machine %s granted permission for disk %s | M | True | ||
| 101 | Virtual Machine %s added mount point %s | L | False | An encrypted folder has been mounted. | |
| 102 | Virtual Machine %s removed fs %s | L | True | An encrypted folder has been removed. | |
| 103 | Virtual Machine %s attempted to fetch key for inactive fsid %s | M | False | A virtual machine attempted to access an inactive FSID. | The cloud admin should determine whether the FSID should be made accessible. |
| 104 | Virtual Machine %s attempted to fetch expired key for fsid %s | H | False | The FSID has expired and therefore the filesystem cannot be mounted. | The cloud admin should determine whether the FSID should be made accessible. This is only possible if the FSID has not been shredded. |
| 105 | Virtual Machine %s fetched key for fsid %s | L | False | A filesystem was mounted using the specified FSID. | |
| 106 | The Key for disk %s Virtual Machine %s has expired | H | True | An attempt is being made to change properties for an already expired key. | The cloud admin should determine whether the key of the disk should be made accessible. This is only possible if the disk's key has not been shredded. |
| 107 | Virtual Machine %s set key expiry to %s, onexpiry to %s for disk %s | H | False | An expiration date has been set on a key for the specified disk. The effect taken on expiration is shown. | The cloud admin should determine whether the expiration date should be extended. |
| 108 | The Certificate for Virtual Machine %s expire%s %d days%s. Please renew the certificate. | M | True | ||
| 109 | The Key for disk %s Virtual Machine %s has expired | H | True | The key shown for the specified VM has expired. | The cloud admin should determine whether the expiration date should be extended. |
| 110 | The Key for disk %s Virtual Machine %s expires in %d day(s). Please extend the key life. | H | True | The encryption key shown is about to expire. | The cloud admin should determine whether the expiration date should be extended. |
| 111 | Unable to check key for disk %s Virtual Machine %s | M | False | An error occurred while attempting to check properties of key for the given disk and VM. | An internal error occurred while checking expiration/rotation properties for specified key. Informational only, key will be checked again. |
| 112 | Virtual Machine %s rebooted, reauthentication required | H | True | A VM has rebooted and the reboot setting requires that the VM is re-authenticated. | The cloud admin needs to complete re-authorization in the KeyControl GUI. |
| 113 | Virtual Machine %s has new alerts, please check | M | True | ||
| 114 | Added Coretrace policy "%s" to Virtual Machine %s | L | True | ||
| 115 | Activated Coretrace policy "%s" for Virtual Machine %s | M | False | ||
| 116 | De-activated Coretrace policy "%s" for Virtual Machine %s | M | False | ||
| 117 | Modified Coretrace policy "%s" for Virtual Machine %s | M | False | ||
| 118 | Removed Coretrace policy "%s" for Virtual Machine %s | M | False | ||
| 119 | Deleted CAStore %s | M | False | ||
| 120 | Removed Server %s from Domain %s | L | False | ||
| 121 | Storage pool %s created on server %s (%s) | L | False | ||
| 122 | Storage pool %s extended on server %s (%s) | L | False | ||
| 123 | Log added to Storage pool %s on server %s (%s) | L | False | ||
| 124 | Log removed from Storage pool %s on server %s (%s) | L | False | ||
| 125 | Storage pool %s deleted from server %s (%s) | L | False | ||
| 126 | Disk added to hot spare list on server %s (%s) | L | False | ||
| 127 | Disk removed from hot spare list on server %s (%s) | L | False | ||
| 128 | Filestore %s created on server %s (%s) | L | False | ||
| 129 | Filestore %s deleted from server %s (%s) | L | False | ||
| 130 | Removed server %s (%s) from domain %s | L | True | ||
| 131 | KMIP Server restarted on %s | M | False | The KMIP server has been restarted on the specified host. | |
| 132 | KMIP Server started on %s | L | True | The KMIP server has been started on the specified host. | |
| 133 | KMIP Server halted on %s | H | True | The KMIP server has been halted on the specified host. | |
| 134 | KMIP Server: All client certificates removed | H | True | All client certificates have been removed from the KMIP server. | |
| 135 | KMIP Server: Client certificate %s removed | H | True | The specified client certificate has been removed from the KMIP server. | |
| 136 | KMIP Server: Client certificate %s updated | M | False | The specified client certificate has been updated on the KMIP server. | |
| 137 | KMIP Server: Client certificate %s created | M | True | The specified client certificate has been created on the KMIP server. | |
| 138 | Could not store oskey on %s/%s. Needs recovery | H | True | Could not store object store key on joining KC node | KC join did not succeed, node should be removed from cluster. If problem persists contact support. |
| 139 | Reconnect not allowed for %s/%s. Please follow reauthenication steps | H | True | KC has attempted to reauthenticate with cluster that does not recognize it | KC node likely was in the cluster and removed. Should be re-joined |
| 140 | Cluster join failed for %s/%s. | H | True | KC has failed to join cluster | KC node join can be attempted again. If problem persists contact support |
| 141 | Reconnect info does NOT match. Follow reauthentication steps for node %s/%s | H | True | KC has attempted to reauthenticate with cluster but its info has changed | KC node likely needs MasterKey recovery or kicked out of cluster and re-joined |
| 142 | Could not store connection info for %s/%s | H | True | KC cannot store info to reconnect to cluster on restart | Condition could be transitory, node could be restarted. Also could indicate that KC disk is full |
| 143 | Problem with auth/secd communication | H | True | Communication stack on KC is not working | |
| 144 | System utilities NOT functioning. Authentication will not happen | H | True | Auth daemon unable to query system information | |
| 145 | Attempt to add node %s/%s which has valid data but no clusterid. Please reauthenticate if this is a valid action. | M | True | KC was formerly in a cluster that has no identifying cluster ID | If action is a valid one, proceed with join. Note that the KC data on joining node will be destroyed |
| 146 | Attempt to add node %s/%s which has a different clusterid. Please reauthenticate if this is a valid action. | M | True | KC was formerly in a different cluster than the one it is attempting to join | If action is a valid one, proceed with join. Note that the KC data on joining node will be destroyed |
| 147 | Could not restore cluster to normal operating mode after adding new node, error $rc | M | True | KC cluster state could not be restored to normal operating state | Can indicate cluster join issues |
| 148 | KeyControl Server system `hostname` ($myip) $act. | L | False | ||
| 149 | Restricted support login enabled on `hostname` | M | True | Restricted support login was enabled on KC | |
| 150 | %s support login enabled on `hostname` | M | True | Full or Restricted support login was enabled on KC | |
| 151 | %s support login disabled on `hostname` | M | True | Full or Restricted support login were disabled on KC | |
| 152 | KeyControl node {$myip[0]}/{$myhost[0]} has failed upgrade to version {$curver} | H | True | KC upgrade to new version has failed | KC will revert to prior install. Upgrade can be attempted again if valid or contact support |
| 153 | KeyControl node {$myip[0]}/{$myhost[0]} reverted from {$str[1]} to {$str[2]} | M | True | User initiated revert to previous version has succeeded. | |
| 154 | KeyControl node {$myip[0]}/{$myhost[0]} has successfully upgraded to version {$curver} | M | True | KC upgrade to new version has succeeded. | |
| 155 | KeyControl node {$myip[0]}/{$myhost[0]} has failed upgrade finalization to version {$curver} | H | True | KC upgrade to new version has failed | KC will revert to prior install. Upgrade can be attempted again if valid or contact support |
| 156 | Hostname %s, Management IP %s, Current Version %s, New Version %s. Upgrade from version {$oldver} (b{$oldrevision}) to version {$curver} (b{$newrevision}) not allowed. Consult product documentation for upgrade procedure | H | True | KC upgrade to this version is not supported from current version | Upgrade to a supported version and/or contact support |
| 157 | Upgrade from version {$oldver} to version {$curver} not officially supported but allowed for development | L | True | KC upgrade to this version is not officially supported but allowed for development build | |
| 158 | Internal error $ret checking upgrade from {$oldver} to {$curver} | H | True | An error has occurred attempting to valid upgrade | Contact support |
| 159 | Multiple KeyControl nodes still in cluster. All excess KeyControl nodes must be removed before upgrade. | H | True | Upgrade should be attempted on only a single node cluster | Remove all nodes from cluster except the node to be upgraded |
| 160 | Insufficient free space to perform upgrade. Consult product documentation for procedure to add another disk | H | True | Disk does not have enough space for upgrade | Consult support for freeing disk space or create/join a node with more space and upgrade that |
| 161 | System has reverted to prior installation. | L | True | System has successfully reverted to prior version | |
| 162 | Failed revert to prior installation. | H | True | System failed to revert to prior version | Contact support. Current version is still in place |
| 163 | System utilities NOT functioning. | H | True | Unable to query system info | |
| 164 | Error resizing partition | H | True | An error occurred while resizing the KeyControl storage. Please contact support. | |
| 165 | Error resizing storage pool | H | True | An error occurred while resizing the KeyControl storage. Please contact support. | |
| 166 | Successfully resized KeyControl storage pool | M | False | The storage pool on the KeyControl node was successfully resized. | |
| 167 | KMIP Server operation failed - internal error | M | True | KMIP server operation failed with an internal error. | Consult support or retry operation |
| 168 | %s operation %s for %s on %s, TaskId: %s. | L | False | A task has changed state | |
| 169 | Virtual Machine %s : disk %s resized to %s | L | False | Virtual Machine disk is resized | |
| 170 | Virtual Machine %s : KC mapping %s attached | L | False | A KC Mapping is attached to a VM | |
| 172 | Passwd changed for htadmin | M | True | An admin reset console/htadmin passwd | |
| 173 | User %s failed to change %s passwd | M | True | An admin attempted a reset console/htadmin passwd that failed | |
| 174 | A support event has occurred on KeyControl node %s. Please create a Support Bundle as described in the online help, then contact support. | H | True | Please contact support for more information | |
| 175 | New certificate created with guid %s in group %s | L | False | A new certificate has been create for use with policy agent or KMIP server | |
| 176 | Backup created successfully for %s (%s) | L | False | A new backup image has been created on the KeyControl appliance | |
| 177 | Failed to create backup for %s (%s) | M | False | Creation of the backup image failed. | Backup will be retried automatically or can be triggered manually via the WebGUI |
| 178 | KeyControl Cluster is in normal mode | L | False | The KeyControl cluster state has returned to normal operating mode | |
| 179 | KeyControl Cluster is in degraded mode | H | False | The KeyControl cluster has gone into degraded mode. This occurs when the KeyControl nodes in the cluster are not able to communicate successfully | Check the availability and connectivity of the KeyControl nodes in the cluster |
| 180 | KeyControl Cluster is in standby mode | L | False | The KeyControl cluster is in a standby state. This is a temporary state which occurs when a node is joining the cluster | |
| 181 | Freespace available on %s has fallen below 2G. An upgrade to the storage for this system should be considered. | H | True | The amount of free disk space available to the KeyControl appliance has dropped below our recommended threshold. Please increase the size of the disk or contact support for more assistance | Increase the size of the disk and reboot the KeyControl appliance to resize |
| 182 | Login failure for %s from %s | L | False | User unsuccessfully attempted to login to the KeyControl instance | |
| 183 | Reboot of %s initiated by %s | M | True | Domain administrator initiated reboot of KeyControl node | |
| 184 | KeyControl node reboot initiated from console | M | True | The KeyControl node was rebooted from the console | |
| 185 | KeyControl node shutdown initiated from console | M | True | The KeyControl node was shutdown from the console | |
| 186 | Azure agent: illegal attempt to install plugin | M | True | Azure "extensions" (a.k.a. "plugins") to a KeyControl VM are not allowed | |
| 187 | Azure agent: illegal attempt to disable or uninstall a plugin | M | True | Azure "extensions" (a.k.a. "plugins") to a KeyControl VM are not allowed | |
| 188 | %d inactive tasks found on Cloud VM Set %s. %s task for %s on %s not updated since %s, TaskId: %s. | L | True | List of tasks that have not been updated for a long time | |
| 189 | Updated LDAP configuration: %s | M | False | The values for the given LDAP fields have been updated | |
| 190 | Virtual Machine %s synchronized devices. Following devices were not found - %s | M | False | The Policy Agent synchronized the registered device list; some devices not found | |
| 191 | Virtual Machine %s synchronized devices. Reason for sync: %s | M | True | The Policy Agent synchronized the registered device list | |
| 192 | Virtual Machine %s state for disk %s changed to %s. %s | L | False | Disk state on policy agent changed | |
| 193 | HyTrust bootloader ssh key updated for %s | L | False | Private key required for ssh login to hytrust bootloader updated on KC | |
| 194 | Two-factor authentication enabled for %s | L | False | Two factor authentication has been enabled for the user | |
| 195 | Two-factor authentication disabled for %s | M | True | Two factor authentication has been disabled for the user | |
| 196 | KeyControl Cluster is in degraded mode during node-join | L | False | The KeyControl cluster has gone into degraded mode while a new node is joining the cluster. This occurs as KeyControl restarts communication protocols after a new node has joined the cluster. | |
| 197 | KeyControl Cluster is in degraded mode during node-join | L | False | The KeyControl cluster has gone into normal mode while a new node is joining the cluster. This occurs as KeyControl restarts communication protocols after a new node has joined the cluster. | |
| 198 | New AppLink created to %s | M | True | A new Application Link has been created. This link will allow secure communication between the Entrust products. | |
| 199 | Application link removed for Product (%s) Version (%s) IP List (%s) | L | False | Application link has been removed for the external product. | |
| 200 | admin user logged in successfully | M | False | htadmin account login successful in one of the KeyControl nodes | |
| 201 | %s account logged in from <IP> | M | False | Full support account login successful in one of the KeyControl nodes | |
| 202 | htadmin account login failure | M | False | Failed attempt to login to htadmin account | |
| 203 | %s account login failure from <IP> - <Reason> | M | False | Failed attempt to login to full support account | |
| 204 | Full support account <user> logged in from <IP> and executed <command> | M | False | Full support account login successful and executed a command | |
| 205 | %s account login failure from <IP> attempting <command> | M | False | Failed attempt to login to full support account and execute command | |
| 206 | Created new log bundle - %s with options - %s | L | False | New log bundle creation has been initiated by some user | |
| 207 | Downloaded log bundle - %s | L | False | Latest log bundle has been downloaded by some user | |
| 208 | Exported Cloud VM Set %s | M | False | A Cloud VM Set has been exported | |
| 209 | Imported Cloud VM Set %s | M | False | A Cloud VM Set has been imported | |
| 210 | Following guests have unsupported policy agent installed in Cloud VM Set %s: %s(%s) | M | True | A Cloud VM Set has guests with unsupported agent version | Upgrade policy agent on reported guests |
| 211 | Unsupported Policy Agent (version %s ) detected on guest %s. | M | False | A guests has unsupported agent version installed | Upgrade policy agent on reported guest |
| 212 | Download of admin key generation %s initiated by %s | M | False | Download of admin key initiated via admin_key GET call | |
| 213 | Reset of KMIP server initiated | M | False | Reset of KMIP server initiated | |
| 214 | KMIP Response/Request: <op> <obj> <result> | M | False | Create, destroy or revoke of KMIP object initiated | |
| 215 | KMIP Response/Request: <op> <obj> <result> | M | False | Operation on some KMIP object initiated | |
| 216 | The Certificate for Virtual Machine %s will auto-renew in %d days%s. | L | True | ||
| 217 | The Certificate for Virtual Machine %s failed to auto-renew. Certificate expire%s %d days%s. Please renew the certificate. | H | True | ||
| 218 | Set Key Encryption Key expiry to %s onexpiry to %s, for Cloud VM Set %s. %s Cloud VMs affected. | H | False | An expiration date has been set for Key Encryption Key for the specified Cloud VM Set. The effect taken on expiration is shown. | The cloud admin should determine whether the expiration date should be extended. |
| 219 | The Key Encryption Key for Cloud VM Set %s expire%s in %d days%s. | H | True | The cloud admin should determine whether the expiration date should be extended. | |
| 220 | The Key Encryption Key for Cloud VM Set %s has expired. %s Cloud VMs affected. | H | True | The Key Encryption Key for specified Cloud VM Set has expired. | The cloud admin should determine whether the expiration date should be extended. |
| 221 | Access to Key Encryption Key of Cloud VM Set %s has been revoked. %s Cloud VMs affected. | H | True | Access to specified Cloud VM Set has been revoked. | |
| 222 | Access to Key Encryption Key of Cloud VM Set %s has been granted. %s Cloud VMs affected. | H | True | Access to specified Cloud VM Set has been granted. | |
| 223 | The Key Encryption Key for Cloud VM Set %s has expired. %s Cloud VMs deleted. Deleted CVM Set %s. | H | True | The Key Encryption Key for specified Cloud VM Set has expired. | |
| 224 | The Certificate for Virtual Machine %s failed to auto-renew as the Virtual Machine is unreachable. | H | True | The Certificate Auto Renewal of a VM fails if the VM is in auto renewal period and is unreachable. | |
| 225 | Authentication of Server %s (%s) failed due to incorrect passphrase | False | Authentication of KeyControl node failed due to incorrect passphrase. | ||
| 226 | Cloud VM Set creation failed. Error: Failed to store key in HSM. %s | H | True | Cloud VM Set creation failed. Failed to store key in HSM. | A security admin should check whether the HSM connection is configured properly |
| 227 | Key Encryption Key import failed. Error: Failed to store key in HSM. %s | H | True | Key Encryption Key import failed. Failed to store key in HSM. | A security admin should check whether the HSM connection is configured properly |
| 228 | Failed to fetch Key Encryption Key from HSM. Error: %s | H | True | Failed to fetch Key Encryption Key from HSM. | A security admin should check whether the HSM connection is configured properly |
| 229 | Successfully imported Key Encryption Key for Cloud VM Set %s. | False | Successfully imported Key Encryption Key | ||
| 230 | Removed Domain %s from group %s | False | Removed Domain from group | ||
| 231 | Authenticated Server %s (%s) | False | New Key Control has been successfully authenticated and added to the cluster | ||
| 232 | Added Server %s (%s) to Domain %s | False | Server has been successfully added to a domain | ||
| 233 | Invalid Key Encryption Key size specified for Cloud VM Set %s. | H | True | Invalid Key Encryption Key size | Verify that the Key Encryption Key size is 128 bits or 256 bits |
| 234 | Retention period has expired for Cloud VM Set %s. %s Cloud VMs deleted. Deleted Cloud VM Set %s. | L | True | Retention period has expired for Cloud VM Set | |
| 235 | Retention period for Cloud VM Set %s will expire in %d days. | H | True | Retention period expiration for Cloud VM Set | The cloud admin should determine whether the retention date should be extended. |
| 236 | Set Retention Date to %s for Cloud VM Set %s. | False | Changed Retention period for Cloud VM Set | ||
| 237 | Failed to delete Key Encryption Key from HSM for Cloud VM Set %s. Error: %s. | M | True | Failed to delete Key Encryption Key from HSM | |
| 238 | New CA Certificate added to Certificate Store for verifying %s | False | New CA certficate has been added to verify some subsystem | ||
| 239 | CA Certificate for %s removed from Certificate Store | False | CA Certificate for some subsystem has been removed from Certificate Store | ||
| 240 | Authentication for LDAP user %s failed. Reason :- %s | False | Reason for LDAP login failures | ||
| 241 | Cannot register Cloud VM until Key Encryption Key for Cloud VM Set %s is imported | L | True | Cannot register Cloud VM | |
| 242 | Virtual Machine %s HTcrypt driver update -- %s | L | False | HTcrypt driver state on policy agent changed | |
| 243 | New self-signed certificates generated for %s | L | False | New self-signed certificates generated for server | |
| 244 | New SSL certificate installed for %s | L | False | New SSL certificate installed for server | |
| 245 | CSR generated with common name - %s | L | False | New CSR generated | |
| 246 | Web server for %s restarted | L | False | Webserver/Apache restarted for server | |
| 247 | Certificate installation task got timed out. There are VMs that did not receive the new CA certificate. Please contact Cloud Administrators to login to the VM and execute hcl heartbeat before restarting the webserver | H | True | One (or more) policy agents did not receive the new CA certificate uploaded. Cloud administrator has to login to the policy agent and execute hcl heartbeat | |
| 248 | Cannot update CA as part of SSL certificate installation for %s. Please login to the VM and execute hcl heartbeat | H | True | Domain Administrator has attempted to install a new SSL certificate for the webserver. Unfortunately one of the policy agents did not receive a copy of the new CA certificate that can verify the SSL certificate of the webserver. Cloud administrator has to login to the policy agent and execute hcl heartbeat | |
| 249 | External web server certificate of %s has expired. A new certificate must be installed before the associated VMs can communicate with %s. After the new certificate has been installed, the certificate information on the associated VMs must be manually updated if the new certificate is from a different Certificate Authority. For more information, search for certificates in the WebGUI online help. | H | True | Certificate used by the external webserver of one of the nodes has expired. Domain administrator has to install a new certificate. If the newly installed certificate is generated by a new CA, cloud administrators will have to login to policy agent and update the CA certificate file. The latest CA certificate file can be found in the cloud tab in webGUI | |
| 250 | External web server certificate of %s will expire in %s days, %s hours and %s minutes. If another certificate is not installed before the current one expires, the VMs will not be able to communicate with %s after %s and all VMs may need to be manually updated after the new certificate is installed. For more information, search for certificates in the WebGUI online help. | H | True | Certificate used by the external webserver of one of the nodes is about to get expired. Domain administrator has to install a new certificate before it gets expired. Otherwise policy agents will not be able to communicate with the KC after expiry | |
| 251 | CA certificate used for verifying %s:%s has already expired. Please upload a new CA certificate to verify the %s server certificate. Otherwise %s users will not be able to login to the WebGUI. | H | True | CA certificate used by the LDAP server has already expired. Security Administrator has to install a new certificate to verify the LDAP server certificate. Otherwise LDAP users will not be able to login to the WebGUI. | |
| 252 | CA certificate used for verifying %s:%s will expire in %s days, %s hours and %s minute. If another CA certificate is not installed before the currentone expires, %s users will not be able to login to the WebGUI after %s. | M | True | CA certificate used for evaluating LDAP server certificate is about to get expired. Security Administrator has to install a new certificate before the current one expires. Otherwise LDAP users will not be able to login to the WebGUI after the CA certificate expiry date. | |
| 253 | Certificate for %s:%s has already expired. Please re-configure %s after updating the certificate in %s. | H | True | Certificate for APPLINK has already expired. APPLINK should be reconfigured after uploading a new certificate. | |
| 254 | Certificate for %s:%s will expire in %s days, %s hours and %s minutes. Once the certificate of %s is updated, please re-configure the %s:%s | M | True | Certificate for APPLINK is about to get expired. Security Administrator has to install a new certificate and re-configure the APPLINK before the current one expires. | |
| 255 | KeyControl Cluster is in maintenance mode | L | False | The KeyControl cluster is in maintenance state. This is a temporary state which occurs during upgrade process | |
| 256 | Virtual Machine with IP %s is a possible clone of %s (%s) and hardware signature verification is turned off. | H | True | A possible clone of a Virtual Machine that is already registered has been detected. Verify that the VM is valid and register it as a new VM using 'hcl register -c' command. | |
| 257 | KeyControl cluster has been successfully upgraded from KC %s to version KC %s | M | True | KeyControl cluster upgrade to new version has succeeded. | |
| 258 | KeyControl cluster has been successfully reverted from KC %s to version KC %s | M | True | KeyControl cluster revert to old version has succeeded | |
| 259 | Access Control Policy: %s, at version: %s applied to disk: %s on VM: %s | H | True | Access Controls Policy version update to disk. | |
| 260 | Access Control Policy removed from disk: %s on VM: %s | H | True | Access Controls Policy removed. | |
| 261 | New Access Control Policy: %s created. | L | False | New Access Control Policy Created. | |
| 262 | Access Control Policy: %s updated. Policy now available as: %s. | H | False | Access Control Policy Updated. | |
| 263 | Access Control Policy: %s deleted. | L | False | Access Control Policy Deleted. | |
| 264 | Access Control Rule: %s added to Policy: %s. | H | False | New Access Control Rule added to Policy. | |
| 265 | Access Control Rule: %s updated for Policy: %s. | H | False | Access Control Rule updated for Policy. | |
| 266 | Access Control Rule: %s deleted from Policy: %s. | H | False | Access Control Rule deleted from Policy. | |
| 267 | hytrust_accesscontrols rpm state changed to: %s on VM: %s | M | False | HyTrust Access Controls rpm state changed | |
| 268 | Initiated application of Access Control Policy: %s to disk: %s on VM: %s. | H | False | Access Control Policy application initiated by Admin. | |
| 269 | Initiated removal of Access Control Policy: %s from disk: %s on VM: %s. | H | False | Access Control Policy removal initiated by Admin. | |
| 270 | Created Cloud VM Set %s with Single Encryption Key | L | True | CVMSet created with Single Encryption Key for dedup | |
| 271 | Failed to upgrade KeyControl nodes: %s. Reverting upgraded nodes: %s. | L | True | Failed to upgrade KeyControl nodes. | |
| 272 | Failed to revert KeyControl nodes: %s. Remove nodes from KeyControl after reboot. | L | True | Failed to revert KeyControl nodes. | |
| 273 | Upgrade Cancelled. Error: %s | L | True | Failed to finalize upgrade. | |
| 274 | %s got reverted during upgrade. Reverting other nodes in the cluster to revision %s | L | False | Failed to upgrade KeyControl node. | |
| 275 | Successfully cancelled KeyControl Upgrade. | M | False | Cancelled KeyControl Upgrade. | |
| 276 | IP conflict detected for %ipaddr with MAC %this_mac on %this_month %this_day %this_time | H | True | Another VM is/was using this KeyControl IP address. | |
| 277 | Access Controls removed successfully on VM %s | H | True | Successful Access Controls removal on VM | |
| 278 | Applying Policy %s, version %s failed on VM %s. %s | H | True | Policy application failure on VM with reason. | |
| 279 | Applying Policy %s, version %s failed on disk %s of VM %s | H | True | Failure in Policy application on a specific disk of a VM. | |
| 280 | Error removing Access Control Policy on disk %s of VM %s | H | True | Error removing Access Control Policy on a disk. | |
| 281 | %s doesn't allow local user creation. Cannot support Access Controls | H | True | VM doesn't support Access Controls due to inability to create local users | |
| 282 | %s doesn't allow ssh for localhost. Cannot support Access Controls | H | True | Cannot setup Access Controls on VM since it doesn't allow ssh for localhost | |
| 283 | %s doesn't allow password-based ssh login. Cannot support Access Controls | H | True | Cannot setup Access Controls on VM since it doesn't allow password-based ssh login. | |
| 284 | Access Control setup failed on VM %s. Please check /var/log/htac.log on VM for more details | H | True | Failure in initial Access Controls setup | |
| 285 | Insufficient free space on %s to perform upgrade. Consult product documentation for procedure to add another disk | H | True | Disk does not have enough space for upgrade | Consult support for freeing disk space or create/join a node with more space and upgrade that |
| 286 | Access Control tampering detected on VM %s | H | True | Access Control Tampering | |
| 287 | Error enforcing policy %s, version %s on VM %s. %s | H | True | Access Control Policy application failure due to htadmin error | |
| 288 | New AD Server: %s created. | L | False | Create AD Server | |
| 289 | Updated AD Server config: %s. | L | False | Updated AD Server config | |
| 290 | Deleted AD Server: %s. | L | False | Deleted AD server | |
| 291 | User account htadmin already exists on VM %s. Please delete htadmin, before enforcing Access Control Policy | L | True | Local user account htadmin detected before Access Control pre-setup tests | |
| 292 | VM - %s cannot verify communications from KeyControl because the KeyControl SSL certificate has changed but the CA certificate on the VM was not updated when the new SSL certificate was installed for KeyControl. To update the CA certificate on the VM and restore connectivity, log into the webGUI, download the latest CA certificate from Cloud tab > Actions > Download CA Certificate, copy the CA certificate to the VM, and execute "hcl update_ca -f </path/to/cert>" | H | True | SSL certificate of KeyControl has changed and webserver has been restarted. One of the VMs did not receive the latest copy of the CA certificate to verify KeyControl. To restore communication, download the latest CA certificate from webgui cloud tab, copy it to the VM and execute hcl update_ca command | |
| 293 | KMIP user certificate for %s has expired. KMIP client(s) that is/are using the expired certificate will not be authenticated to perform KMIP operations. Please extend the user certificate or create new user certificate, and update the KMIP clients with the new certificate bundle | H | True | KMIP user certificate for one of the users has expired. KMIP client(s) using the expired certificate will not be authenticated to perform KMIP operations. Please create new KMIP certificate for the KMIP client(s) to use | |
| 294 | KMIP user certificate for %s will expire in %s days, %s hours and %s minutes. Upon expiry, client(s) that is/are using the expired certificate will not be authenticated to perform KMIP operations. Please extend the user certificate or create new user certificate, and update the KMIP clients with the new certificate bundle | H | True | KMIP user certificate for one of the users will expire soon. Upon expiry, KMIP client(s) using the expired certificate will not be authenticated to perform KMIP operations. Please create new KMIP certificate for the KMIP client(s) to use | |
| 295 | VM %s is using an older Hardware Signature format. Please run "hcl auth" cmd on the VM for a more secure signature. | H | True | VM is using an older Hardware Signature format. Please run "hcl auth" cmd on the VM for a more secure signature. | |
| 296 | L | True | Alert email sent to Security Admins on upgrade. | ||
| 297 | Abandoning %d inactive tasks on %s. Abandoning %s task %s on %s not updated since %s, TaskId: %s | L | True | List of tasks that have been abandoned due to inactivity | |
| 298 | Error!!! Could not enable support login. Please make sure there is enough space in the filesystem | H | True | Cannot enable support login. Please make sure there is enough space in the file-system | Increase the size of the disk and reboot the KeyControl appliance to resize |
| 299 | Error!!! Could not disable support login. Please make sure there is enough space in the filesystem | H | True | Cannot disable support login. Please make sure there is enough space in the file-system | Increase the size of the disk and reboot the KeyControl appliance to resize |
| 300 | %s attempting %s account login when object store is not readable | M | False | Attempt to login to support login in one of the KeyControl nodes when object store is down | |
| 301 | Decryption is not allowed for device %s on VM %s. To decrypt: Access Control Policy : %s Version: %d must be removed from device. Auto Encryption Policy should be changed so as to exclude the device. | L | True | Device decryption refused due to applied policies. | Change policies as suggested in error message. |
| 302 | Space on HyTrust Bootloader partition %s is running low (%lld bytes free). Often times USN journal is the culprit. You can check USN journal size using the command: "fsutil usn queryjournal %s". To delete USN journal, use the command: "fsutil usn deletejournal /N %s " | H | True | Device decryption refused due to applied policies. | Change policies as suggested in error message. |
| 303 | Login failure for %s from %s because %s is in lock out period. | M | False | Attempt to login to secroot in the lock out period after repeated unsuccessful login attempts | |
| 304 | Changed AD group members for group %s. %s | L | False | List of AD Group members has been changed for a KeyControl Group | |
| 305 | The current number of KeyControl nodes (%d) exceeds the maximum number of nodes allowed by your license (%d). You cannot add any more KeyControl nodes to this cluster until you upgrade your license. | M | True | KeyControl nodes in use exceeds license limit of installed license | |
| 306 | The current number of VMs registered with this KeyControl cluster (%d) exceeds the maximum number of VMs allowed by your license (%d). You cannot register any additional VMs until you upgrade your license. | M | True | Registered VM count exceeds license limit of installed license | |
| 307 | Service %s is up | L | False | KeyControl system service is up | |
| 308 | Service %s is down | H | True | KeyControl system service is down | |
| 309 | Using AD group membership for %s - %s | M | False | ADgroup membership of the AD user that was returned by the LDAP server during first time login. The ADgroup membership will be used to determine the KeyControl Group membership of the AD user. | |
| 310 | Updating AD group membership for %s - %s | M | False | ADgroup membership of the AD user that was returned by the LDAP server. The new ADgroup membership will be used to determine the KeyControl Group membership of the AD user who has already logged into KeyControl previously. | |
| 311 | Added KMIP client configuration. Server: %s | L | False | Added KMIP client configuration | |
| 312 | Updated KMIP client configuration. Server: %s | L | False | Updated KMIP client configuration | |
| 313 | Deleted KMIP client configuration. Server: %s | H | True | Deleted KMIP client configuration | |
| 314 | Deleted all KMIP client configurations. | H | True | Deleted KMIP client configuration | |
| 315 | Failed to delete key:%s on external KMIP server | M | False | Failed to delete key on KMIP server | |
| 316 | Added AD Domain: %s | L | False | Added a new AD Domain | |
| 317 | Updated AD Domain %s. Changed Attributes - %s | L | False | Updated the AD Domain | |
| 318 | Remomved AD Domain %s | L | False | Removed AD Domain from KeyControl | |
| 319 | Added new Domain Controller %s for AD Domain %s | L | False | Added a new AD Domain Controller | |
| 320 | Updated Domain Controller %s for AD Domain %s. Changed Attributes - %s | L | False | Updated Domain Controller | |
| 321 | Removed Domain Controller %s for AD Domain %s | L | False | Removed Domain Controller from KeyControl | |
| 322 | encrypt failed for device %s on VM %s, error %d | M | True | Encrypt operation failed on VM | |
| 323 | decrypt failed for device %s on VM %s, error %d | M | True | Decrypt operation failed on VM | |
| 324 | rekey failed for device %s on VM %s, error %d | M | True | Rekey operation failed on VM | |
| 325 | Successfully deleted admin key on EKS: %s | M | False | Successfully deleted admin key on KMIP server | |
| 326 | Successfully generated admin key on EKS: %s | M | False | Successfully generated admin key on KMIP server | |
| 327 | Failed to generate admin key on EKS: %s | H | True | Failed to generate admin key on KMIP server | |
| 328 | Failed to store admin key on EKS: %s | H | True | Failed to store admin key on KMIP server | |
| 329 | Successfully stored admin key on EKS: %s | M | False | Successfully stored admin key on KMIP server | |
| 330 | Failed to fetch admin key from EKS: %s | M | True | Failed to fetch admin key from KMIP server | |
| 331 | KeyControl Upgrade failed. Please contact Support | H | True | Post upgrade failed | |
| 332 | Domain Controllers re-ordered for %s | L | False | Order of Domain Controllers has been changed for an AD domain configured | |
| 333 | Failed to set backup hosts to %s on %s | H | True | Failed to update backup hosts | |
| 334 | Virtual Machine %s is in BoundaryControl grace period | M | True | VM in Boundary Control grace period | |
| 335 | Virtual Machine %s, BoundaryControl grace period expired | M | True | VM Boundary Control grace period expired | |
| 336 | Application Link created from Product (%s) Version (%s) IP List (%s) | L | False | A new Application Link has been created from an external product. This link will allow the external product to make API calls to KeyControl. | |
| 337 | Application Link renewed for Product (%s) Version (%s) IP List (%s) | L | False | An Application Link has been renewed for the external product. | |
| 338 | Failed to upgrade LDAP Settings. Please reconfigure LDAP settings manually | H | True | Failed to upgrade LDAP Settings. | |
| 339 | Failed to store adminkey on HSM | H | True | Failed to store adminkey on HSM | |
| 340 | Removed Server(s) %s from Domain %s | L | True | ||
| 341 | Grace period will expire on %s for Virtual Machine %s, please check connectivity | H | True | ||
| 342 | Grace period expired for Virtual Machine %s, please authenticate again | H | True | ||
| 343 | Virtual Machine %s, failed to update following attributes: %s | H | False | Failed to update Virtual Machine settings | |
| 344 | Finished propagating changed attributes: %s to all Virtual Machines in Cloud VMSet: %s | H | False | Propagation of changed attributes completed for CVMSet | |
| 345 | Invalid software was discovered on KeyControl system %s. This is a possible trojan horse attack. Contact Support for assistance | H | True | Whitelisting violation detected on production build | |
| 346 | Entrust Whitelist validation on KeyControl system %s has discovered modified files. These changes are allowed for development systems, but please review Whitelist logs for correctness. | L | True | Whitelisting violation detected on development build | |
| 347 | Could not set password for %s: %s | H | True | Failed to set password | |
| 348 | Password changed for %s | H | True | Password changed | |
| 349 | Enabled %s user | H | True | Enabled user | |
| 350 | Failed to enable %s user | H | True | Failure in enabling user | |
| 351 | Disabled %s account | H | True | Disable account | |
| 352 | %s user logged out successfully | L | False | User logout | |
| 353 | Could not download the certificate: %s | M | True | Download certificate failure | |
| 354 | Downloaded a new CA certificate | M | True | Downloaded CA certificate | |
| 355 | ssh %sd for %s | M | False | SSH enabled/disabled for user | |
| 356 | Failed to %s ssh for %s | M | False | Failure in enabling/disabling SSH for user | |
| 357 | KeyControl restored from version %s backup file | M | False | KeyControl restored from backup successfully | |
| 358 | License auto-update: %s | M | True | License change during auto-update | |
| 359 | Failed to %s syslog on %s | H | True | Failed to enable/disable syslog on KeyControl node(s) | |
| 360 | Generated Syslog Certificate Signing Request with common name %s | L | False | Generated Syslog Certificate Signing Request with common name | |
| 361 | Changed following Syslog settings attributes: %s | L | False | Changed some Syslog settings attributes. | |
| 362 | Exporting audit log succeeded for %s (%s). Audit log is available to download. | M | True | Finish exporting audit log | |
| 363 | Exporting audit log failed for %s (%s). | M | True | Exporting audit log failed | |
| 364 | CVM Certificate %s, associated with CVM %s, CVMSet %s, revoked successfully | H | True | ||
| 365 | Cloud VM Set creation failed. Error: Failed to create root key in HSM. %s. | H | True | Root key creation failure on HSM during Cloud VM Set creation. | Security Admin should determine whether HSM is properly configured. |
| 366 | Cloud VM Set creation failed. Error: Failed to generate wrapped Key Encryption Key in HSM. %s. | H | True | Wrapped Key Encryption Key generation failed on HSM during Cloud VM Set creation | Security Admin should determine whether HSM is properly configured.. |
| 367 | Virtual Machine %s moved from Cloud VM Set - %s (in KeyControl Group - %s) to Cloud VM Set - %s in (KeyControl Group - %s) | M | True | Virtual Machine has been moved from Cloud VM Set to another one (might be in another KeyControl Group | |
| 368 | Successfully enabled passphrase based startup authentication | M | False | Set startup authentication type | |
| 369 | Successfully changed passphrase for startup authentication | M | False | Changed passphrase for startup authentication | |
| 370 | Recovered access to KeyControl node %s using passphrase | M | True | Recovered Masterkey using passphrase | |
| 371 | Successfully disabled passphrase based startup authentication | M | False | Set startup authentication type | |
| 372 | Successfully reset nShield HSM configuration | M | False | nShield HSM configuration reset | |
| 373 | Cloud VM Set %s: Asymmetric KeyID %s created. | M | False | Asymmetric KeyID created | |
| 374 | Cloud VM Set %s: Asymmetric KeyID %s revoked/unrevoked. | M | False | Asymmetric KeyID revoked/unrevoked | |
| 375 | Cloud VM Set %s: Asymmetric KeyID %s updated - expires %s, onexpiry %s. | M | False | Asymmetric KeyID expiration attributes updated | |
| 376 | Cloud VM Set %s: Asymmetric KeyID %s description updated. | M | False | Asymmetric KeyID description updated | |
| 377 | Cloud VM Set %s: Asymmetric KeyID %s deleted. | M | False | Asymmetric KeyID deleted | |
| 378 | Successfully encrypted plaintext using KeyID: %s | M | False | Encrypted plaintext using keyid key | |
| 379 | Successfully decrypted ciphertext using KeyID: %s | M | False | Decrypted ciphertext using keyid key | |
| 380 | Cloud VM Set %s: Asymmetric KeyID %s has expired | M | True | Asymmetric KeyID expired | |
| 381 | Fatal error on KeyControl nodes: %s. Please contact Support | H | True | KeyControl Upgrade Failure | Reinstall specified nodes to secure KeyControl Cluster |
| 382 | CRL regenerated and applied successfully on %s | M | False | CRL regeneration | |
| 383 | Attempt to register a new KeyControl node (%s) with revision %s failed. Error: %s | M | True | Attempt to register a new KeyControl node failed | |
| 384 | Successfully reset %s | M | True | The KeyControl node has been reset. | |
| 385 | %s. Please contact HyTrust to buy/renew the license. If you do not plan to use this feature, you should delete your existing vault(s) to stop this message. For more information, see the Administration Guide. | M | True | Vault license not enabled or expired | |
| 386 | Created PASM Vault %s | M | False | The specified vault has just been created. | |
| 387 | Successfully removed pre-upgrade snapshots. | M | True | KC pre-upgrade snapshots were removed. | |
| 388 | KeyControl node {$myip[0]}/{$myhost[0]} removed pre-upgrade snapshots. | M | True | KC pre-upgrade snapshots were removed from a node. | |
| 389 | KeyControl configuration has been successfully updated. New node %s needs to be added to nShield HSM server configuration | M | True | Update nShield HSM server configuration | |
| 390 | Failed to configure newly joined node %s for nShield HSM server | H | True | Failed to configure node for nShield HSM | |
| 391 | Successfully completed decryption of KMIP objects | H | True | Decrypt operation completed for KMIP objects | |
| 392 | Successfully completed rekey of KMIP objects | H | True | Rekey operation completed for KMIP objects | |
| 393 | Successfully enabled encryption of KMIP objects | H | True | Enabled encryption of KMIP objects | |
| 394 | Successfully disabled encryption of KMIP objects | H | True | Disabled encryption of KMIP objects | |
| 395 | Failed to generate Key Encryption Key on HSM. Error: %s | H | True | Failed to generate Key Encryption Key on HSM | |
| 396 | Successfully generated Key Encrytion Key on HSM | M | False | Generated Key Encryption Key on HSM | |
| 397 | Successfully cancelled node-join | M | False | Cancelled KeyControl Node-Join | |
| 398 | Failed to join %s to KeyControl Cluster. Error: %s | M | True | Failed to join KeyControl node | |
| 399 | Successfully joined %s to KeyControl Cluster | M | False | Added new node to KeyControl Cluster | |
| 400 | CSR generated with common-name %s for node-join | M | False | Certificate Signing Request generated for node-join | |
| 401 | Certificate bundle generated for node-join | M | False | Certificate bundle generated for node-join | |
| 402 | Returning keys to VM %s running on ESXi Host %s. VM UUID is %s. | M | False | Returning keys to VM on successful authorization with HTCC with additional VM info | |
| 403 | Returning keys to VM %s | M | False | Returning keys to VM on successful authorization with HTCC | |
| 404 | NTP servers not found on KeyControl %s | H | True | NTP servers not found on KeyControl | Configure NTP servers using KeyControl TUI |
| 405 | NTP synchronization failed on KeyControl %s | M | True | NTP synchronization failed on KeyControl | Check if NTP servers are reachable from KeyControl |
| 406 | Freespace available on %s has fallen below %s%% for the /boot volume. Please contact support. | H | The amount of free disk space on the KeyControl appliance /boot filesystem has dropped below our recommended threshold. Please contact support for assistance. | Contact support. | |
| 407 | Set Key Encryption Key expiry to %s, onexpiry to %s for Cloud VMSet %s. Initiated rekey process to encrypt all Data Encryption Keys. | M | False | Added Key Encryption Key to Cloud VMSet | |
| 408 | Successfully encrypted Data Encryption Keys of all CVMs in CVMSet: %s with a Key Encryption Key: %s. %s VMs, %s KeyIDs %s Asymmetric KeyIDs affected | M | False | Successfully encrypted Data Encryption Keys with Key Encryption Key | |
| 409 | Successfully reset Luna HSM configuration | M | False | Luna HSM configuration reset | |
| 410 | Successfully tested nShield HSM configuration | M | False | nShield HSM configuration was successfully tested | |
| 411 | Luna HSM configuration changed:- | M | False | Luna HSM configuration changed | |
| 412 | Successfully tested Luna HSM configuration | M | False | Luna HSM configuration was successfully tested | |
| 413 | Luna Cloud HSM configuration changed:- | M | False | Luna Cloud HSM configuration changed | |
| 414 | Successfully reset Luna Cloud HSM configuration | M | False | Luna Cloud HSM configuration was reset | |
| 415 | Successfully tested Luna Cloud HSM configuration | M | False | Luna Cloud HSM configuration was successfully tested | |
| 416 | Failed to create /bootext filesystem. Please contact support for more assistance | H | True | Failed to create /bootext filesystem. Please contact support for more assistance | |
| 417 | Failed to join %s/%s to KeyControl Cluster. Please contact Support | H | True | Failed to join KeyControl node to cluster | |
| 418 | CloudKey: {} modified | M | True | CloudKey: {} modified | |
| 419 | CloudKey: {} : KeySet {} migrated to HSM | M | False | CloudKey: {} : KeySet {} migrated to HSM | |
| 420 | Cloud Key {} deleted from KMS | H | True | Cloud Key {} deleted from KMS | |
| 421 | Cloud Key {} restored to KMS | M | True | Cloud Key {} restored to KMS | |
| 422 | Cloud Key {} state changed to {} on KMS | H | True | Cloud Key {} state changed to {} on KMS | |
| 423 | Tag {} (value {}) set on Cloud Key {} | M | False | Tag {} (value {}) set on Cloud Key {} | |
| 424 | Removed Tag {} on Cloud Key {} | M | False | Removed Tag {} on Cloud Key {} | |
| 425 | Set users ({}) and administrators ({}) to Cloud Key {} | M | True | Set users ({}) and administrators ({}) to Cloud Key {} | |
| 426 | Removed {} ({}) from Cloud Key {} | M | True | Removed {} ({}) from Cloud Key {} | |
| 427 | New Cloud Key {} created in KeySet {} | M | True | New Cloud Key {} created in KeySet {} | |
| 428 | New Cloud Key {} created in KeySet {} {} {} | M | True | New Cloud Key {} created in KeySet {} Region/Vault {} | |
| 429 | Cloud Key {} : KeySet {} uploaded to {} {} | M | True | Cloud Key {} : KeySet {} uploaded to {} {} | |
| 430 | Cloud Key {} : KeySet {} rotated | M | True | Cloud Key {} : KeySet {} rotated | |
| 431 | Cloud Key {} : KeySet {} scheduled for deletion in {} days | H | True | Cloud Key {} : KeySet {} scheduled for deletion in {} days | |
| 432 | Deletion schedule canceled on Cloud Key {} : KeySet {} | M | True | Deletion schedule canceled on Cloud Key {} : KeySet {} | |
| 433 | Cloud Key {} : KeySet {} deletion complete | M | False | Cloud Key {} : KeySet {} deletion complete | |
| 434 | Processed Expiry Action {} on Cloud Key {} : KeySet {} | H | True | Processed Expiry Action {} on Cloud Key {} : KeySet {} | |
| 435 | Cloud Key {} region {} imported in KeySet {} | M | False | Cloud Key {} region {} imported in KeySet {} | |
| 436 | Started Key Import from {} {} from KMS to KeySet {} | M | True | Started Key Import from region/keyvault/keyring {} from KMS to KeySet {} | |
| 437 | Keys imported from {} {} from KMS to KeySet {} | M | True | Keys imported from region/keyvault/keyring {} from KMS to KeySet {} | |
| 438 | Keys imported from AWS KMS to KeySet {} | M | True | Keys imported from AWS KMS to KeySet {} | |
| 439 | Keys migrated to HSM from KEYCONTROL for KeySet {} | H | True | Keys migrated to HSM from KEYCONTROL for KeySet {} | |
| 440 | KeySet: {} modified | M | True | KeySet: {} modified | |
| 441 | Started key migration, from KEYCONTROL to HSM, for KeySet {} | H | True | Started key migration, from KEYCONTROL to HSM, for KeySet {} | |
| 442 | New KeySet: {} created | M | True | New KeySet: {} created | |
| 443 | Key Set {} deleted | H | True | Key Set {} deleted | |
| 444 | CSP Account: {} modified | M | True | CSP Account: {} modified | |
| 445 | CSP Account {} access keys rotated | H | True | CSP Account {} access keys rotated | |
| 446 | New CSP Account: {} created | M | True | New CSP Account: {} created | |
| 447 | CSP Account {} deleted | H | True | CSP Account {} deleted | |
| 448 | Access key rotation failed | H | True | Access key rotation failed | |
| 449 | CloudKey rotation failed | M | True | CloudKey rotation failed | |
| 450 | CloudKey expiry processing failed | M | True | CloudKey expiry processing failed | |
| 451 | CloudKey import failed | M | True | CloudKey import failed | |
| 452 | CloudKey auto import failed | M | True | CloudKey auto import failed | |
| 453 | Set Key Policy for Cloud Key {} | M | True | Set Key Policy for Cloud Key | |
| 454 | False | ||||
| 455 | Encryption finished on system volumes of KeyControl {} | M | False | Encryption finished on system volumes of KeyControl | |
| 456 | Successfully installed managed Secret Vault Plugin: {} (version {}) | M | False | Managed Secret Vault Plugin install success | |
| 457 | Cloud Key {} : KeySet {} deleted as upload failed | L | False | Cloud Key object deleted as upload failed | |
| 458 | Enabled Root-of-Trust in password mode | M | False | Enabled Root-of-Trust in password mode | |
| 459 | Failed to enable Root-of-Trust | M | False | Failed to enable Root-of-Trust | |
| 460 | Enabled Root-of-Trust in hwsig mode | M | False | Enabled Root-of-Trust in hwsig mode | |
| 461 | Failed to enable Root-of-Trust | M | False | Failed to enable Root-of-Trust | |
| 462 | Disabled Root-of-Trust | M | False | Disabled Root-of-Trust | |
| 463 | Failed to disable Root-of-Trust: %s | M | False | Failed to disable Root-of-Trust: %s | |
| 464 | A differenet Cloud Key with name {} for KeyVault {} is already present in KeySet {}.If you want to overwrite the key in Key Control, delete the existing key from key control and import again | M | True | Could not import cloudkey as a different key with the same keyname already present in Key Control | |
| 467 | Internal web server certificate of %s has expired. A new certificate must be installed for KeyControl Cluster to be healthy | H | True | Certificate used by the internal web server of one of the nodes has expired. Domain administrator has to install a new certificate for the KeyControl cluster to be healthy. | |
| 468 | Internal web server certificate of %s will expire in %s days, %s hours and %s minutes. A new certificate must be installed before the current one expires for the KeyControl Cluster to be healthy. | H | True | Certificate used by the internal web server of one of the nodes is about to get expired. Domain administrator has to install a new certificate before it gets expired. Otherwise cluster will be degraded | |
| 469 | Cloud Key {} KeyVault {} in KeySet {} synced from KMS | M | False | Cloud Key {} KeyVault {} in KeySet {} synced from KMS | |
| 470 | Cloud Key {} operations changed to {} on Azure KMS | M | True | Cloud Key {} operations changed to {} on Azure KMS | |
| 471 | Cloud Key {} KeyVault {} imported in KeySet {} | M | False | Cloud Key {} KeyVault {} imported in KeySet {} | |
| 472 | CloudKey import failed in KeyVault {} KeySet {} Error {} | M | False | CloudKey import failed in KeyVault {} KeySet {} Error {} | |
| 473 | Client Secret for Service application {} (CSP {}) will expire on {}. Please update it now to avoid BYOK management service disruption | H | True | ||
| 474 | Client Secret for Service application {} (CSP {}) has expired on {}. Please update it now to resume BYOK management service | H | True | ||
| 480 | Successfully reset administrator account password of Vault tenant %s | M | False | Reset Vault tenant administrator account password | |
| 481 | Failed to initialize Authentication database | M | True | ||
| 482 | Cloud Key {} KeyRing {} imported in KeySet {} | M | False | Cloud Key {} KeyRing {} imported in KeySet {} | |
| 483 | Cloud Key {} KeyRing {} in KeySet {} synced from KMS | M | False | Cloud Key {} KeyRing {} in KeySet {} synced from KMS | |
| 484 | CloudKey import failed in KeyRing {} KeySet {} Error {} | M | False | CloudKey import failed in KeyRing {} KeySet {} Error {} | |
| 485 | Label {} (value {}) set on Cloud Key {} | M | False | Label {} (value {}) set on Cloud Key {} | |
| 486 | Removed Label {} on Cloud Key {} | M | False | Removed Label {} on Cloud Key {} | |
| 487 | Failed to delete old access keys for CSP Account '{}'. Error - '{}' | M | False | Failed to delete old access keys for CSP Account '{}'. Error - '{}' | |
| 488 | EKM Key Access Justification policy violation while accessing Cloud Key {} : KeySet {} : error {} | M | False | EKM Key Access Justification policy violation | |
| 489 | TDE Connector {} state changed to {} on Keyset {} | M | True | TDE Connector state changed | |
| 490 | TDE Connector {} expiry date changed to {} on Keyset {} | M | True | TDE Connector expiry date changed | |
| 491 | Added TDE Connector {} for CVM {} in KeySet {} | M | True | Add TDE connector | |
| 492 | Removed TDE Connector {} from CVM {} in KeySet {} | M | True | Remove TDE connector | |
| 493 | Successfully registered with KCM (KeyControl Compliance Manager) (id: {}) from {} | M | True | KCM (KeyControl Compliance Manager) register | |
| 494 | Successfully unregistered with KCM (KeyControl Compliance Manager) (id: {}) from {} | M | True | KCM (KeyControl Compliance Manager) unregister | |
| 495 | Successfully reset KCM (KeyControl Compliance Manager) registration configuration from {} | M | True | KCM (KeyControl Compliance Manager) configuration reset | |
| 496 | User %s reset syslog settings | M | False | Reset Syslog settings | |
| 497 | Attempt to register a new %s server "%s" failed -- maximum node limit reached. | M | True | Maximum allowed cluster node count reached | |
| 498 | Backup failed due to insufficent space on root device. Please contact support. | H | True | Backup failed due to insufficent space on root device | |
| 499 | Backup was not started due to heavy load on %s | M | True | Backup was not started due to heavy load on KeyControl | |
| 500 | '%s can be downloaded from the Settings page (https://%s/appliance/#!/account). Reason for regeneration: %s | H | True | Regenerated Admin Key | |
| 501 | Rescued %s vault: %s | L | True | Rescued Vault | |
| 502 | %s logged in from ipaddr %s using Personal Access Token %s | L | False | The specified user has just logged in from the IP address shown with Personal Access Token. | |
| 503 | AD authorization(Personal Access Token login) for user %s failed. Reason :- %s | False | Reason for AD/LDAP login failure for Personal Access Token login | ||
| 504 | %s %s Personal Access Token %s from ipaddr %s | False | Create/Update/Delete Actions on Personal Access Token | ||
| 505 | Keys migrated from HSM to KEYCONTROL for KeySet {} | H | True | Keys migrated from HSM to KEYCONTROL for KeySet {} | |
| 506 | CloudKey: {} : KeySet {} migrated to KEYCONTROL | M | False | CloudKey: {} : KeySet {} migrated to KEYCONTROL | |
| 507 | Keys migrated from KEYCONTROL to HSM for KeySet {} | H | True | Keys migrated from KEYCONTROL to HSM for KeySet {} | |
| 508 | Updated %s Vault %s with KCM %s | M | False | The specified vault has just been updated with KCM. | |
| 509 | Configured OIDC without AD with client id %s | M | False | Configured OIDC without AD | |
| 510 | OIDC without AD configuration removed | M | False | OIDC without AD configuration removed | |
| 511 | Changed Password Settings :- %s from %s to %s | M | False | One or more of the listed password settings has been changed. | |
| 512 | Keys cached from HSM to KEYCONTROL for KeySet {} | H | True | Keys cached from HSM to KEYCONTROL for KeySet {} | |
| 513 | Keys uncached from KEYCONTROL for KeySet {} | H | True | Keys uncached from KEYCONTROL for KeySet {} | |
| 514 | CloudKey: {} : KeySet {} cached to KeyControl | M | False | CloudKey: {} : KeySet {} cached to KeyControl | |
| 515 | CloudKey: {} : KeySet {} uncached from KeyControl | M | False | CloudKey: {} : KeySet {} uncached from KeyControl | |
| 516 | OIDC authorization failed. Reason :- %s | M | False | Reason for OIDC login failure | |
| 517 | Connection from node %s to HSM %s has failed | H | True | The node is unable to communicate with the HSM | Security Admin should check the HSM configuration. |
| 518 | Connection from node %s to HSM %s is restored | L | True | The node is able to communiucate with the HSM again | |
| 519 | Connection from node %s to HSM %s still failed after HSMROT timeout, locking down | H | True | The node is shutting down because it has lost contact with the HSM | Fix the issue preventing the node from contacting the HSM and restart the node. |
| 520 | HSM issue on node %s: %s | M | True | Some HSM issues have been detected on the node that do not prevent communication with the HSM | Security Admin should check the HSM configuration. |
| 521 | HSM issues resolved on node %s | L | True | The HSM issues previously reported on the node have been resolved | |
| 522 | Failed to install self-signed certificate cluster-wide | M | True | Install self signed certificate cluster-wide | |
| 523 | Failed to clean cacert list. | M | False | Clean cacert list guid from system setting | |
| 524 | Successfully moved the cluster to self-signed certificate. | M | False | Install self signed certificate cluster-wide | |
| 525 | Successfully changed the EMS Enforcement crypto policy. | M | False | Change EMS Enforced Configuration | |
| 526 | The license for this system expired %s days ago.\nPlease renew or upgrade the license. Start that process from the licensing page in the webgui at https://%s/appliance/#!/license" | H | True | License expired | |
| 527 | The license for this system expires in %s days.\nPlease renew or upgrade the license. Start that process from the licensing page in the webgui at https://%s/appliance/#!/license | H | True | License will expire after some days. | |
| 528 | The license for this system expires today.\nPlease renew or upgrade the license. Start that process from the licensing page in the webgui at https://%s/appliance/#!/license | H | True | License is expiring today. | |
| 529 | This system has exceeded the licensed limit of %s Virtual Machines.\nFurther Virtual Machine creation is disabled.\nPlease renew or upgrade the license. Start that process from the licensing page in the webgui at https://%s/appliance/#!/license | H | True | This system has exceeded the licensed limit of virtual machines count. Further Virtual Machine creation is disabled. | |
| 530 | This system has exceeded the licensed limit of %s Virtual Machines. Please renew or upgrade the license. Start that process from the licensing page in the webgui at https://%s/appliance/#!/license | H | True | This system has exceeded the licensed limit of virtual machines count. | |
|
531 |
System Initialization Complete |
L |
False |
System Initialization Complete |
|
|
532 |
System Autoconfiguration Complete |
L |
False |
System Autoconfiguration Complete |
|
