Secrets

Secret resources are used to securely store sensitive information such as user names and passwords that must be used by KUMA to interact with external services.

Available settings:

• Name (required)—a unique name for this type of resource. Must contain from 1 to 128 Unicode characters.
• Tenant (required)—name of the tenant that owns the resource.
• Type (required)—the type of secret.

  When you select the type in the drop-down list, the parameters for configuring this secret type also appear. These parameters are described below.

• Description—you can add up to 256 Unicode characters describing the resource.

Available parameters that depend on the Secret kind:

• credentials—used to store credentials required to connect to an external service, for example, to SMTP server.
  • User and Password (required fields)—user name and password that are used for connecting to an external service.
• token—used to store tokens for API requests. For example, token are used when connecting to R-Vision IRP.
  • Token (required)—this field is used to store a token.
• ktl—used to store Kaspersky Threat Intelligence Portal credentials.
  • Name and Password (required fields)—user name and password of your Kaspersky Threat Intelligence Portal account.
  • PFX (required)—this section is used to upload your Kaspersky Threat Intelligence Portal certificate key.
  • PFX password (required)—this field is used to enter the password for accessing the Kaspersky Threat Intelligence Portal certificate key.
• urls—used for storing URLs. You can add URL fields by clicking the Add button, and can remove them by clicking the button.

  Available formats: hostname:port, IPv4:port, IPv6:port, :port.

• snmpV1—used to store the values of Community access (for example, public or private) required for interaction over the Simple Network Management Protocol.
• snmpV3—used for storing data required for interaction over the Simple Network Management Protocol:
  • User—user name indicated without a domain.
  • Security level—security level of the user.
    • NoAuthNoPriv—messages are forwarded without authentication and without ensuring confidentiality.
    • AuthNoPriv—messages are forwarded with authentication but without ensuring confidentiality.
    • AuthPriv—messages are forwarded with authentication and ensured confidentiality.

    You may see additional settings depending on the selected level.

  • Password—user password. This field becomes available when the AuthNoPriv or AuthPriv security level is selected.
  • Authentication protocol—the following protocols are available: MD5, SHA, SHA224, SHA256, SHA384, SHA512. This field becomes available when the AuthNoPriv or AuthPriv security level is selected.
  • Privacy Protocol—protocol used for encrypting messages. Available protocols: DES, AES. This field becomes available when AuthPriv security levels are selected.
  • Privacy password—encryption password that was set when the user was created. This field becomes available when AuthPriv security levels are selected.
• certificate—used for storing certificate files. Files are uploaded to a resource by clicking the Upload certificate file button.

Page top