crypto_api category

This category of logs contains all the business requests concerning the Crypto API module.

setup action

The setup action means that the Crypto API configuration is checked. It generates an "info" severity log if it is configured properly, or an "err" severity log in the event of an error.

The log fields for this action are as follows:

Field

Description

 Type

Mandatory/Optional

tenant_id

Tenant identifier.

Example: 025f02fe-bee2-444b-bf76-b5ead30327c0

 String in uuid v4 format Mandatory
enabled Specify if the Crypto API module is enabled. Boolean Mandatory
errors

If the Crypto API module cannot be enabled due to an incorrect configuration, this JSON object contains an error list with an error code and a message:

  • If the severity level is "info", the error list is empty, the Crypto API module is enabled.

  • If the severity level is "err", the list contains at least one error.

Example: [

{

code: 2002010,

message: 'Module: CryptoAPI not enabled for tenantId bc337abd-0d4f-43f9-aaf6-54ef7268d2e5. Reason: Validation failed. Reasons are: [Wrong type error: <tenant>/crypto_api/authentication property must be array]'

}

]

 Object

Mandatory if enabled is set to true

 

Encrypt and decrypt actions

  • The encrypt action means that an encrypt request has been made. This is the case whenever data is encrypted using the KMaaS service.

  • The decrypt action means that a decrypt request has been made. This is the case every time data is decrypted using the KMaaS service.

These actions generate an "info" severity log in the event of success, or a "crit" severity log in the event of an error.

The log fields for these actions are as follows:

Field

Description

 Type

Mandatory/Optional

tenant_id

Tenant identifier.

Example: 025f02fe-bee2-444b-bf76-b5ead30327c0

 String in uuid v4 format Mandatory

kek_id

Identifier of the KEK used.

Example: ed7e4c13-6199-30a3-7bce-1c82a9e31e21

 String Mandatory