This is the multi-page printable view of this section. Click here to print.

Return to the regular view of this page.

Protegrity Command Line Interface (CLI) Reference

Overview of the Protegrity CLI.

The Protegrity CLI include the following CLI:

  • Administrator CLI: The Administrator CLI is used to perform administrative tasks for the PPC.
  • Policy Management CLI: The Policy Management CLI is used to create or manage policies. The CLI performs the same function that can be performed using the Policy Management APIs. For more information about using the Policy Management APIs, refer to the section Using the Policy Management REST APIs.

Important: The Policy Management CLI will work only after you have installed the workbench.

  • Insight CLI: The Insight CLI is used to work with logs, such as, forwarding logs to an external SIEM.

1 - Administrator Command Line Interface (CLI) Reference

Administrator CLI documentation.

admin

This section shows how to access help and provides examples for admin.

admin --help
Usage: admin [OPTIONS] COMMAND [ARGS]...

  Users, Roles, Permissions, Groups, SAML and Azure AD management commands.

Options:
  --help  Show this message and exit.

Commands:
  create  Create a resource.
  delete  Delete a resource.
  get     Display one resource.
  list    List resources.
  set     Update fields of a resource.
  test    Test various configurations and connections.

create

This section lists the create commands.

The following command shows how to access help and provides examples for create.

admin create --help
Usage: admin create [OPTIONS] COMMAND [ARGS]...

  Create a resource.

Options:
  --help  Show this message and exit.

Commands:
  entra-id                Create Entra ID configuration.
  entra-id-import-groups  Import Entra ID groups with optional member...
  entra-id-import-users   Import Entra ID users with role assignments.
  groups                  Create a new group.
  roles                   Create a new role.
  saml-mappers            Create an attribute mapper for a SAML provider.
  saml-providers          Create a new SAML SSO provider.
  users                   Create a new user.

create entra-id

The following command shows how to access help and provides examples for create entra-id.

admin create entra-id --help
Usage: admin create entra-id [OPTIONS]

  Create Entra ID configuration.

  Required Entra ID Setup:
  1. Register an application in Entra ID
  2. Grant Microsoft Graph API permissions:
     - User.Read.All (Application)
     - Group.Read.All (Application) - if importing groups
  3. Create a client secret for the application
  4. Note the Tenant ID, Application (Client) ID, and Client Secret

  Examples:
      admin create entra-id --tenant-id "12345678-1234-1234-1234-123456789012" --client-id "87654321-4321-4321-4321-210987654321" --client-secret "your-secret-here"

Options:
  -t, --tenant-id TEXT      Entra ID Tenant ID  [required]
  -c, --client-id TEXT      Entra ID Application (Client) ID  [required]
  -s, --client-secret TEXT  Entra ID Application Client Secret  [required]
  --enabled / --disabled    Enable/disable configuration
  --help                    Show this message and exit.

create entra-id-import-users

The following command shows how to access help and provides examples for create entra-id-import-users.

admin create entra-id-import-users --help
Usage: admin create entra-id-import-users [OPTIONS]

  Import Entra ID users with role assignments.

  Import users from Entra ID into the application with role assignments.
  Users must be provided via JSON data.

  JSON Format:
  {
      "users": [
          {
              "userPrincipalName": "john.doe@company.com",
              "email": "john.doe@company.com",
              "firstName": "John",
              "lastName": "Doe",
              "roles": ["admin", "user"],
              "identityProviders": ["AWS-IDP", "AZURE-IDP"]
          }
      ],
      "dryRun": false
  }

  Examples:
      # Direct JSON input with identity providers
      admin create entra-id-import-users --json-data '{"users":[{"userPrincipalName":"john@company.com","email":"john@company.com","firstName":"John","lastName":"Doe","roles":["user"],"identityProviders":["AWS-IDP","AZURE-IDP"]}]}'

      # Dry run with JSON
      admin create entra-id-import-users --json-data '{"users":[...]}' --dry-run

Options:
  --dry-run             Validate import without creating users
  -j, --json-data TEXT  JSON string with users data to import directly
                        [required]
  --help                Show this message and exit.

create entra-id-import-groups

The following command shows how to access help and provides examples for create entra-id-import-groups.

admin create entra-id-import-groups --help
Usage: admin create entra-id-import-groups [OPTIONS]

  Import Entra ID groups with optional member import.

  Import groups from Entra ID into the system with role assignments for members.
  Groups must be provided via JSON data.

  JSON Format:
  {
      "groups": [
          {
              "id": "12345678-1234-1234-1234-123456789012",
              "displayName": "Administrators",
              "description": "Administrative users group",
              "importMembers": true,
              "memberRoles": ["admin", "user"],
              "identityProviders": ["AWS-IDP", "AZURE-IDP"]
          }
      ],
      "dryRun": false
  }

  Examples:
      # Direct JSON input with identity providers
      admin create entra-id-import-groups --json-data '{"groups":[{"id":"12345678-1234-1234-1234-123456789012","displayName":"IT Admins","description":"IT department administrators","importMembers":true,"memberRoles":["admin"],"identityProviders":["AWS-IDP","AZURE-IDP"]}]}'

      # Dry run with JSON
      admin create entra-id-import-groups --json-data '{"groups":[...]}' --dry-run

Options:
  --dry-run             Validate import without creating groups
  -j, --json-data TEXT  JSON string with groups data to import directly
                        [required]
  --help                Show this message and exit.

create groups

The following command shows how to access help and provides examples for create groups.

admin create groups --help
Usage: admin create groups [OPTIONS]

  Create a new group.

  Examples:
      admin create groups --name developers --description "Development team"
      admin create groups --name admins --members "john,jane" --roles "admin,user_manager"
      admin create groups --name operators --description "System operators" --members "user1,user2" --roles "operator"

Options:
  -n, --name TEXT         Group name  [required]
  -d, --description TEXT  Group description
  -m, --members TEXT      Comma-separated list of usernames to add as members
  -r, --roles TEXT        Comma-separated list of role names to assign to
                          group
  --help                  Show this message and exit.

create roles

The following command shows how to access help and provides examples for create roles.

admin create roles --help
Usage: admin create roles [OPTIONS]

  Create a new role.

  Examples:
      admin create roles --name manager --description "Manager role"
      admin create roles --name admin --permissions "security_officer"
      admin create roles --name operator --description "System operator" --permissions "security_officer"

Options:
  -n, --name TEXT         Role name  [required]
  -d, --description TEXT  Role description
  -p, --permissions TEXT  Comma-separated list of permission names
  --help                  Show this message and exit.

create saml-mappers

The following command shows how to access help and provides examples for create saml-mappers.

admin create saml-mappers --help
Usage: admin create saml-mappers [OPTIONS] PROVIDER_ALIAS

  Create an attribute mapper for a SAML provider.

  Examples:
      admin create saml-mappers azure-ad --name email-mapper --mapper-type saml-user-attribute-idp-mapper --attribute-name "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress" --user-attribute email
      admin create saml-mappers azure-ad --name role-mapper --mapper-type saml-role-idp-mapper --attribute-value admin --role admin

Options:
  -n, --name TEXT                 Name of the attribute mapper  [required]
  --mapper-type [saml-user-attribute-idp-mapper|saml-role-idp-mapper|saml-advanced-group-idp-mapper|saml-username-idp-mapper]
                                  Type of mapper  [required]
  --sync-mode TEXT                Sync mode for the mapper
  --attribute-name TEXT           SAML attribute name to map from
  --user-attribute TEXT           User attribute to map to
  --attribute-value TEXT          SAML attribute value for role mapping
  --role TEXT                     Role to assign
  --group TEXT                    Group to assign users to
  --template TEXT                 Username template
  --attributes TEXT               Key-value pairs for attribute mapping (JSON
                                  format)
  --help                          Show this message and exit.

create saml-providers

The following command shows how to access help and provides examples for create saml-providers.

admin create saml-providers --help 
Usage: admin create saml-providers [OPTIONS]

  Create a new SAML SSO provider.

  Examples:
      admin create saml-providers --alias azure-ad --display-name "Azure AD" --config-type metadataUrl --service-provider-entity-id "https://your-saml.com/realms/your-realm" --metadata-url "https://..."
      admin create saml-providers --alias okta --display-name "Okta" --config-type metadataFile --service-provider-entity-id "https://your-saml.com/realms/your-realm" --metadata-file /path/to/metadata.xml

Options:
  -a, --alias TEXT                Unique alias for the SAML provider
                                  [required]
  -d, --display-name TEXT         Display name shown in login pages
                                  [required]
  --config-type [metadataUrl|metadataFile]
                                  Configuration type  [required]
  --service-provider-entity-id TEXT
                                  Service Provider Entity ID  [required]
  --metadata-url TEXT             URL to fetch SAML metadata (for metadataUrl
                                  type)
  --metadata-file FILENAME        Path to SAML metadata XML file (for
                                  metadataFile type)
  --signing-certificate TEXT      X.509 certificate for signing (PEM format
                                  without headers)
  --name-id-format TEXT           NameID Policy Format
  --force-authn / --no-force-authn
                                  Force re-authentication
  --validate-signature / --no-validate-signature
                                  Validate SAML response signatures
  --want-assertions-signed / --no-want-assertions-signed
                                  Require signed assertions
  --want-assertions-encrypted / --no-want-assertions-encrypted
                                  Require encrypted assertions
  --signature-algorithm TEXT      Signature algorithm for SAML requests
  --post-binding-response / --no-post-binding-response
                                  Use POST binding for SAML responses
  --post-binding-authn-request / --no-post-binding-authn-request
                                  Use POST binding for SAML authentication
                                  requests
  --post-binding-logout / --no-post-binding-logout
                                  Use POST binding for SAML logout requests
  --want-authn-requests-signed / --no-want-authn-requests-signed
                                  Sign SAML authentication requests
  --attribute-mapping TEXT        Attribute mapping as JSON string or
                                  key=value pairs
  --enabled / --disabled          Enable/disable the provider
  --store-token / --no-store-token
                                  Store tokens returned by the identity
                                  provider
  --help                          Show this message and exit.

Note: The --metadata-file option is not supported. You cannot upload or copy the metadata file. Instead, use the --metadata-url option to configure SAML.

create users

The following command shows how to access help and provides examples for create users.

admin create users --help
Usage: admin create users [OPTIONS]

  Create a new user.

  Examples:
      admin create users --username john.doe --email john@example.com --password "StrongPass123!"
      admin create users --username jane --email jane@example.com --password "SecurePass123!" --first-name Jane --last-name Smith --roles "admin,user"
      admin create users --username alpha --email alpha@example.com --password "AlphaPass123!" --identity-provider "AWS-IDP:alpha@example.com:alpha@example.com"
      admin create users --username beta --password "BetaPass123!" --identity-provider "AWS-IDP:beta@example.com:beta@example.com" --identity-provider "AZURE-IDP:beta@azure.com:beta"

Options:
  -u, --username TEXT       Username  [required]
  -e, --email TEXT          Email address
  --first-name TEXT         First name
  --last-name TEXT          Last name
  -p, --password TEXT       Password
  --roles TEXT              Comma-separated list of role names
  --groups TEXT             Comma-separated list of group names
  --identity-provider TEXT  Identity provider in format:
                            PROVIDER_NAME:userId:userName (can be specified
                            multiple times)
  --help                    Show this message and exit.

delete

This section lists the delete commands.

The following command shows how to access help and provides examples for delete.

admin delete --help
Usage: admin delete [OPTIONS] COMMAND [ARGS]...

  Delete a resource.

Options:
  --help  Show this message and exit.

Commands:
  entra-id        Delete Entra ID configuration.
  groups          Delete a group.
  roles           Delete a role.
  saml-mappers    Delete an attribute mapper for a SAML provider.
  saml-providers  Delete a SAML SSO provider.
  users           Delete a user by ID.

delete entra-id

The following command shows how to access help and provides examples for delete entra-id.

admin delete entra-id --help
Usage: admin delete entra-id [OPTIONS]

  Delete Entra ID configuration.

  Warning: This action cannot be undone and will permanently remove
  all stored Entra ID settings.

  Examples:
      admin delete entra-id

Options:
  --help  Show this message and exit.

delete groups

The following command shows how to access help and provides examples for delete groups.

admin delete groups --help
Usage: admin delete groups [OPTIONS] GROUP_ID

  Delete a group.

  Examples:
      admin delete groups group-uuid-here
      admin delete groups group-uuid-here --delete-members

Options:
  -d, --delete-members  Delete all members of the group along with the group
  --help                Show this message and exit.

delete roles

The following command shows how to access help and provides examples for delete roles.

admin delete roles --help
Usage: admin delete roles [OPTIONS] ROLE_NAME

  Delete a role.

  Examples:
      admin delete roles admin

Options:
  --help  Show this message and exit.

delete saml-mappers

The following command shows how to access help and provides examples for delete saml-mappers.

admin delete saml-mappers --help
Usage: admin delete saml-mappers [OPTIONS] PROVIDER_ALIAS MAPPER_ID

  Delete an attribute mapper for a SAML provider.

  Examples:
      admin delete saml-mappers azure-ad mapper-uuid

Options:
  --help  Show this message and exit.

delete saml-providers

The following command shows how to access help and provides examples for delete saml-providers.

admin delete saml-providers --help
Usage: admin delete saml-providers [OPTIONS] ALIAS

  Delete a SAML SSO provider.

  Examples:
      admin delete saml-providers azure-ad

Options:
  --help  Show this message and exit.

delete users

The following command shows how to access help and provides examples for delete users.

admin delete users --help
Usage: admin delete users [OPTIONS] USER_ID

  Delete a user by ID.

  Examples:
      admin delete users USER_ID

Options:
  --help  Show this message and exit.

get

This section lists the get commands.

The following command shows how to access help and provides examples for get.

admin get --help
Usage: admin get [OPTIONS] COMMAND [ARGS]...

  Display one resource.

Options:
  --help  Show this message and exit.

Commands:
  email            Get current SMTP configuration.
  email-health     Get detailed health status of the email service.
  email-log        Get current log level.
  email-version    Get email version information.
  entra-id         Get current Entra ID configuration.
  groups           Get detailed information about a specific group.
  log-level        Get current log level from the backend.
  password_policy  Get current password policy configuration.
  roles            Get detailed information about a specific role.
  saml-mappers     Get detailed information about a SAML provider...
  saml-providers   Get detailed information about a specific SAML provider.
  users            Get detailed information about a specific user.
  version          Get application version information.

get email

The following command shows how to access help and provides examples for get email.

admin get email --help
Usage: admin get email [OPTIONS]

  Get current SMTP configuration.

  Examples:
      admin get email

Options:
  --help  Show this message and exit.

get email-health

The following command shows how to access help and provides examples for get email-health.

admin get email-health --help
Usage: admin get email-health [OPTIONS]

  Get detailed health status of the email service.

  Examples:
      admin get email-health

Options:
  --help  Show this message and exit.

get email-log

The following command shows how to access help and provides examples for get email-log.

admin get email-log --help
Usage: admin get email-log [OPTIONS]

  Get current log level.

  Examples:
      admin get email-log

Options:
  --help  Show this message and exit.

get email-version

The following command shows how to access help and provides examples for get email-version.

admin get email-version --help
Usage: admin get email-version [OPTIONS]

  Get email version information.

  Examples:
      admin get email-version

Options:
  --help  Show this message and exit.

get entra-id

The following command shows how to access help and provides examples for get entra-id.

admin get entra-id --help
Usage: admin get entra-id [OPTIONS]

  Get current Entra ID configuration.

  Examples:
      admin get entra-id

Options:
  --help  Show this message and exit.

get groups

The following command shows how to access help and provides examples for get groups.

admin get groups --help
Usage: admin get groups [OPTIONS] GROUP_ID

  Get detailed information about a specific group.

  Examples:
      admin get groups group-uuid-here
      admin get groups developers

Options:
  --help  Show this message and exit.

get password_policy

The following command shows how to access help and provides examples for get password_policy.

admin get password_policy --help
Usage: admin get password_policy [OPTIONS]

  Get current password policy configuration.

Options:
  --help  Show this message and exit.

get roles

The following command shows how to access help and provides examples for get roles.

admin get roles --help
Usage: admin get roles [OPTIONS] ROLE_NAME

  Get detailed information about a specific role.

  Examples:
      admin get roles admin

Options:
  --help  Show this message and exit.

get saml-mappers

The following command shows how to access help and provides examples for get saml-mappers.

admin get saml-mappers --help
Usage: admin get saml-mappers [OPTIONS] ALIAS

  Get detailed information about a SAML provider including its mappers.

  Examples:
      admin get saml-mappers azure-ad

Options:
  --help  Show this message and exit.

get saml-providers

The following command shows how to access help and provides examples for get saml-providers.

admin get saml-providers --help
Usage: admin get saml-providers [OPTIONS] ALIAS

  Get detailed information about a specific SAML provider.

  Examples:
      admin get saml-providers tttt
      admin get saml-providers azure-ad-saml

Options:
  --help  Show this message and exit.

get users

The following command shows how to access help and provides examples for get users.

admin get users --help
Usage: admin get users [OPTIONS] USER_ID

  Get detailed information about a specific user.

  Examples:
      admin get users USER_ID
      admin get users 12345-uuid

Options:
  --help  Show this message and exit.

get version

The following command shows how to access help and provides examples for get version.

admin get version --help
Usage: admin get version [OPTIONS]

  Get application version information.

  Examples:
      admin get version

Options:
  --help  Show this message and exit.

get log-level

The following command shows how to access help and provides examples for get log-level.

admin get log-level --help
Usage: admin get log-level [OPTIONS]

  Get current log level from the backend.

  Examples:
      admin get log-level

Options:
  --help  Show this message and exit.

list

This section lists the list commands.

The following command shows how to access help and provides examples for list.

admin list --help
Usage: admin list [OPTIONS] COMMAND [ARGS]...

  List resources.

Options:
  --help  Show this message and exit.

Commands:
  entra-id-group-members  Search Entra ID group members.
  entra-id-groups         Search Entra ID groups.
  entra-id-users          Search Entra ID users.
  groups                  List all groups with their members and roles.
  permissions             List all available permissions.
  roles                   List all roles.
  saml-mappers            List all attribute mappers for a SAML provider.
  saml-providers          List all SAML SSO providers.
  users                   List all users.

list entra-id-group-members

The following command shows how to access help and provides examples for list entra-id-group-members.

admin list entra-id-group-members --help
Usage: admin list entra-id-group-members [OPTIONS]

  Search Entra ID group members.

  Search for members of a specific Entra ID group.

  Search Parameters:
  - Group ID: Required group unique identifier (GUID) - case-sensitive
  - Search Query: Optional filter for members (searches name and email fields)

  Examples:
      admin list entra-id-group-members --group-id "12345678-1234-1234-1234-123456789012"
      admin list entra-id-group-members --group-id "87654321-4321-4321-4321-210987654321" --search "john"
      admin list entra-id-group-members -g "group-guid-here" -s "admin"

Options:
  -g, --group-id TEXT  Group unique identifier (GUID)  [required]
  -s, --search TEXT    Search query to filter group members
  --help               Show this message and exit.

list entra-id-groups

The following command shows how to access help and provides examples for list entra-id-groups.

admin list entra-id-groups --help
Usage: admin list entra-id-groups [OPTIONS]

  Search Entra ID groups.

  Search across displayName field.
  If no search query provided, returns all groups.

  Pagination:
  - Use --max to control number of results per page (max: 999)
  - Use --first to skip results (offset)
  - Response shows if more results are available

  Examples:
      # Get first 100 groups (default)
      admin list entra-id-groups

      # Search with default pagination
      admin list entra-id-groups --search "admin"

      # Get first 500 groups
      admin list entra-id-groups --max 500

      # Get maximum groups per page (999)
      admin list entra-id-groups --max 999

      # Get next page of results
      admin list entra-id-groups --max 999 --first 999

      # Search with custom pagination
      admin list entra-id-groups --search "IT" --max 500 --first 0


  To fetch all groups:
      # Loop through pages until no more results
      admin list entra-id-groups --max 999 --first 0
      admin list entra-id-groups --max 999 --first 999
      admin list entra-id-groups --max 999 --first 1998
      # ... continue until "More results available" is not shown

Options:
  -s, --search TEXT    Search query to find groups
  -m, --max INTEGER    Maximum number of groups to return (default: 100, max:
                       999)
  -f, --first INTEGER  Offset for pagination (default: 0)
  --help               Show this message and exit.

list entra-id-users

The following command shows how to access help and provides examples for list entra-id-users.

admin list entra-id-users --help
Usage: admin list entra-id-users [OPTIONS]

  Search Entra ID users.

  Search across userPrincipalName, givenName, surname, and mail fields.
  If no search query provided, returns all enabled users.

  Pagination:
  - Use --max to control number of results per page (max: 999)
  - Use --first to skip results (offset)
  - Response shows if more results are available

  Examples:
      # Get first 100 users (default)
      admin list entra-id-users

      # Search with default pagination
      admin list entra-id-users --search "john"

      # Get first 500 users
      admin list entra-id-users --max 500

      # Get maximum users per page (999)
      admin list entra-id-users --max 999

      # Get next page of results
      admin list entra-id-users --max 999 --first 999

      # Search with custom pagination
      admin list entra-id-users --search "smith" --max 500 --first 0


  To fetch all users:
      # Loop through pages until no more results
      admin list entra-id-users --max 999 --first 0
      admin list entra-id-users --max 999 --first 999
      admin list entra-id-users --max 999 --first 1998
      # ... continue until "More results available" is not shown

Options:
  -s, --search TEXT    Search query to find users
  -m, --max INTEGER    Maximum number of users to return (default: 100, max:
                       999)
  -f, --first INTEGER  Offset for pagination (default: 0)
  --help               Show this message and exit.

list groups

The following command shows how to access help and provides examples for list groups.

admin list groups --help
Usage: admin list groups [OPTIONS]

  List all groups with their members and roles.

  Examples:
      admin list groups
      admin list groups --max 10
      admin list groups --max 5 --first 10

Options:
  -m, --max INTEGER    Maximum number of groups to return
  -f, --first INTEGER  Offset for pagination
  --help               Show this message and exit.

list permissions

The following command shows how to access help and provides examples for list permissions.

admin list permissions --help
Usage: admin list permissions [OPTIONS]

  List all available permissions.

  Examples:
      admin list permissions
      admin list permissions --filter "read*"

Options:
  -f, --filter TEXT  Filter permissions by name pattern
  --help             Show this message and exit.

list roles

The following command shows how to access help and provides examples for list roles.

admin list roles --help
Usage: admin list roles [OPTIONS]

  List all roles.

  Examples:
      admin list roles

Options:
  --help  Show this message and exit.

list saml-mappers

The following command shows how to access help and provides examples for list saml-mappers.

admin list saml-mappers --help
Usage: admin list saml-mappers [OPTIONS] PROVIDER_ALIAS

  List all attribute mappers for a SAML provider.

  Examples:
      admin list saml-mappers azure-ad

Options:
  --help  Show this message and exit.

list saml-providers

The following command shows how to access help and provides examples for list saml-providers.

admin list saml-providers --help
Usage: admin list saml-providers [OPTIONS]

  List all SAML SSO providers.

  Examples:
      admin list saml-providers

Options:
  --help  Show this message and exit.

list users

The following command shows how to access help and provides examples for list users.

admin list users --help
Usage: admin list users [OPTIONS]

  List all users.

  Examples:
      admin list users
      admin list users --max 10
      admin list users --max 5 --first 10

Options:
  -m, --max INTEGER    Maximum number of users to return
  -f, --first INTEGER  Offset for pagination
  --help               Show this message and exit.

set

This section lists the set commands.

The following command shows how to access help and provides examples for set.

admin set --help
Usage: admin set [OPTIONS] COMMAND [ARGS]...

  Update fields of a resource.

Options:
  --help  Show this message and exit.

Commands:
  email            Update SMTP configuration.
  email-log        Set application log level.
  entra-id         Update existing Entra ID configuration.
  groups           Update an existing group.
  lock_user        Lock a user account.
  log-level        Update the log level (critical, error, warning, info,...
  password_policy  Update password policy configuration.
  roles            Update an existing role.
  saml-providers   Update an existing SAML SSO provider.
  token            Update access token lifespan and SSO idle timeout.
  unlock_user      Unlock a user account and set a new password.
  update_password  Update user password.
  users            Update an existing user.

set email

The following command shows how to access help and provides examples for set email.

admin set email --help
Usage: admin set email [OPTIONS]

  Update SMTP configuration.

  Examples:
      admin set email -h "smtp.example.com" -p 587 --use-tls -u "app-user" -w "app-password"

Options:
  -h, --smtp-host TEXT     SMTP server hostname  [required]
  -p, --smtp-port INTEGER  SMTP server port  [required]
  --use-tls / --no-tls     Enable/disable TLS
  -u, --username TEXT      SMTP username
  -w, --password TEXT      SMTP password
  --help                   Show this message and exit.

set email-log

The following command shows how to access help and provides examples for set email-log.

admin set email-log --help
Usage: admin set email-log [OPTIONS]

  Set email application log level.

  Examples:
      admin set email-log -l debug
      admin set email-log -l info

Options:
  -l, --level [debug|info|warning|error|critical]
                                  Log level to set  [required]
  --help                          Show this message and exit.

set entra-id

The following command shows how to access help and provides examples for set entra-id.

admin set entra-id --help
Usage: admin set entra-id [OPTIONS]

  Update existing Entra ID configuration.

  Only provided fields are updated. Configuration is tested if credentials are changed.

  Examples:
      admin set entra-id --enabled
      admin set entra-id --client-secret "new-secret-here"
      admin set entra-id --tenant-id "new-tenant-id" --client-id "new-client-id"

Options:
  -t, --tenant-id TEXT      Update Entra ID Tenant ID
  -c, --client-id TEXT      Update Entra ID Application (Client) ID
  -s, --client-secret TEXT  Update Entra ID Application Client Secret
  --enabled / --disabled    Enable/disable configuration
  --help                    Show this message and exit.

set groups

The following command shows how to access help and provides examples for set groups.

admin set groups --help
Usage: admin set groups [OPTIONS] GROUP_ID

  Update an existing group.

  Examples:
      admin set groups group-uuid --members "john,jane,bob"
      admin set groups group-uuid --roles "admin,user_manager"
      admin set groups group-uuid --members "user1,user2" --roles "operator,viewer"
      admin set groups group-uuid --identity-providers "AWS-IDP,AZURE-IDP"
      admin set groups group-uuid --members "john.doe,senior.dev" --roles "senior_admin,lead_developer" --identity-providers "AWS-IDP,AZURE-IDP"

Options:
  -m, --members TEXT             Comma-separated list of usernames (replaces
                                 existing members)
  -r, --roles TEXT               Comma-separated list of role names (replaces
                                 existing roles)
  -i, --identity-providers TEXT  Comma-separated list of identity provider
                                 names (replaces existing providers)
  --help                         Show this message and exit.

set lock_user

The following command shows how to access help and provides examples for set lock_user.

admin set lock_user --help
Usage: admin set lock_user [OPTIONS] USER_ID

  Lock a user account.

  Examples:
      admin set lock_user USER_ID

Options:
  --help  Show this message and exit.

set log-level

The following command shows how to access help and provides examples for set log-level.

admin set log-level --help
Usage: admin set log-level [OPTIONS] {critical|error|warning|info|debug}

  Update the log level (critical, error, warning, info, debug).

  Examples:
      admin set log-level info
      admin set log-level debug

Options:
  --help  Show this message and exit.

set password_policy

The following command shows how to access help and provides examples for set password_policy.

admin set password_policy --help
Usage: admin set password_policy [OPTIONS]

  Update password policy configuration.

Options:
  --policy TEXT  Password policy configuration as JSON string.

                 Common Keys:
                 - length: Minimum password length
                 - digits: Number of digits required
                 - lowerCase: Number of lowercase characters required
                 - upperCase: Number of uppercase characters required
                 - specialChars: Number of special characters required
                 - notUsername: Password cannot be same as username (0 or 1)
                 - passwordHistory: Number of previous passwords to remember
                 - maxLength: Maximum password length

                 Examples:
                     admin set password_policy --policy '{"length": 8, "digits": 1, "upperCase": 1, "specialChars": 1}'
                     admin set password_policy --policy '{"length": 12, "digits": 2, "lowerCase": 1, "upperCase": 1, "specialChars": 2, "notUsername": 1}'
                     admin set password_policy --policy '{"length": 10, "passwordHistory": 5, "maxLength": 128}'   [required]
  --help         Show this message and exit.

set roles

The following command shows how to access help and provides examples for set roles.

admin set roles --help
Usage: admin set roles [OPTIONS] ROLE_NAME

Update an existing role.

Examples:
    admin set roles admin --description "Updated admin role"
    admin set roles manager --permissions "security_officer"
    admin set roles operator --description "System operator" --permissions "security_officer"

Options:
  -d, --description TEXT  New role description
  -p, --permissions TEXT  Comma-separated list of permission names (replaces existing)
  --help                  Show this message and exit.
             Show this message and exit.

set saml-providers

The following command shows how to access help and provides examples for set saml-providers.

admin set saml-providers --help
Usage: admin set saml-providers [OPTIONS] ALIAS

  Update an existing SAML SSO provider.

  Only the parameters you explicitly provide will be updated.

  Examples:
      admin set saml-providers azure-ad --display-name "New Azure AD"
      admin set saml-providers Test --enabled
      admin set saml-providers Test --disabled
      admin set saml-providers Test --force-authn
      admin set saml-providers Test --no-validate-signature
      admin set saml-providers Test --metadata-url "https://new-metadata-url.com"
      admin set saml-providers Test --signature-algorithm "RSA_SHA512"

Options:
  -d, --display-name TEXT         Update display name for the provider
  --config-type [metadataUrl|metadataFile]
                                  Update configuration type
  --service-provider-entity-id TEXT
                                  Update Service Provider Entity ID
  --metadata-url TEXT             Update metadata URL
  --metadata-file FILENAME        Update metadata file content
  --signing-certificate TEXT      Update signing certificate
  --name-id-policy-format TEXT    Update NameID Policy Format
  --force-authn                   Enable force authentication
  --no-force-authn                Disable force authentication
  --validate-signature            Enable signature validation
  --no-validate-signature         Disable signature validation
  --want-assertions-signed        Require signed assertions
  --no-want-assertions-signed     Don't require signed assertions
  --want-assertions-encrypted     Require encrypted assertions
  --no-want-assertions-encrypted  Don't require encrypted assertions
  --signature-algorithm TEXT      Update signature algorithm
  --post-binding-response         Enable POST binding for responses
  --no-post-binding-response      Disable POST binding for responses
  --post-binding-authn-request    Enable POST binding for auth requests
  --no-post-binding-authn-request
                                  Disable POST binding for auth requests
  --post-binding-logout           Enable POST binding for logout
  --no-post-binding-logout        Disable POST binding for logout
  --want-authn-requests-signed    Enable authentication request signing
  --no-want-authn-requests-signed
                                  Disable authentication request signing
  --attribute-mapping TEXT        Update attribute mapping (JSON format)
  --enabled                       Enable the provider
  --disabled                      Disable the provider
  --store-token                   Enable token storage
  --no-store-token                Disable token storage
  --help                          Show this message and exit.

Note: The --metadata-file option is not supported. You cannot upload or copy the metadata file. Instead, use the --metadata-url option to configure SAML.

set unlock_user

The following command shows how to access help and provides examples for set unlock_user.

admin set unlock_user --help
Usage: admin set unlock_user [OPTIONS] USER_ID

  Unlock a user account and set a new password.

  Examples:
      admin set unlock_user USER_ID --password "NewPassword123!"
      admin set unlock_user USER_ID -p "StrongPass123!"

Options:
  -p, --password TEXT  New password to set after unlocking  [required]
  --help               Show this message and exit.

set update_password

The following command shows how to access help and provides examples for set update_password.

admin set update_password --help
Usage: admin set update_password [OPTIONS] USER_ID

  Update user password.

  Examples:
      admin set update_password USER_ID --new-password "NewPassword123!" --old-password "OldPass123!"
      admin set update_password USER_ID -n "NewPass123!" -o "OldPass123!"

Options:
  -n, --new-password TEXT  New password  [required]
  -o, --old-password TEXT  Current password for validation  [required]
  --help                   Show this message and exit.

set users

The following command shows how to access help and provides examples for set users.

admin set users --help
Usage: admin set users [OPTIONS] USER_ID

  Update an existing user.

  Examples:
      admin set users USER_ID --email newemail@example.com
      admin set users USER_ID --roles "admin,manager"
      admin set users USER_ID --identity-provider "AWS-IDP:alpha@example.com:alpha@example.com"
      admin set users USER_ID --identity-provider "AWS-IDP:alpha@example.com:alpha@example.com" --identity-provider "AZURE-IDP:beta@azure.com:beta"

Options:
  -e, --email TEXT          New email address
  --first-name TEXT         New first name
  --last-name TEXT          New last name
  --roles TEXT              Comma-separated list of role names (replaces
                            existing)
  --groups TEXT             Comma-separated list of group names (replaces
                            existing)
  --identity-provider TEXT  Identity provider in format:
                            PROVIDER_NAME:userId:userName (can be specified
                            multiple times, replaces existing)
  --help                    Show this message and exit.

set token

The following command shows how to access help and provides examples for set token.

admin set token --help
Usage: admin set token [OPTIONS]

  Update access token lifespan and SSO idle timeout.

  Examples:
      admin set token --lifespan 600
      admin set token --lifespan 1200

Options:
  --lifespan INTEGER RANGE  Access token lifespan in seconds (minimum: 60,
                            maximum: 3600)  [60<=x<=3600; required]
  --help                    Show this message and exit.

test

This section lists the test commands.

The following command shows how to access help and provides examples for test.

admin test --help
Usage: admin test [OPTIONS] COMMAND [ARGS]...

  Test various configurations and connections.

Options:
  --help  Show this message and exit.

Commands:
  email     Send an email.
  entra-id  Test Entra ID connection.

test email

The following command shows how to access help and provides examples for test email.

admin test email --help
Usage: admin test email [OPTIONS]

  Send an email.

  Examples:
      admin test email -f "sender@example.com" -t "recipient@example.com" -s "Test" -b "This is a test"
      admin test email -f "sender@example.com" -t "recipient@example.com" -c "cc@example.com" --bcc-emails "bcc@example.com" -s "Test" -b "Message"

Options:
  -f, --from-email TEXT  Sender email address  [required]
  -t, --to-emails TEXT   Recipient email address. For multiple recipients,
                         provide a comma-separated list  [required]
  -s, --subject TEXT     Email subject  [required]
  -b, --body TEXT        Email body content  [required]
  -c, --cc-emails TEXT   CC email address. For multiple recipients, provide a
                         comma-separated list
  --bcc-emails TEXT      BCC email address. For multiple recipients, provide a
                         comma-separated list
  --help                 Show this message and exit.

test entra-id

The following command shows how to access help and provides examples for test entra-id.

admin test entra-id --help
Usage: admin test entra-id [OPTIONS]

  Test Entra ID connection.

  Test Options:
  1. Test stored configuration: --use-stored
  2. Test provided credentials: --tenant-id, --client-id, --client-secret

  Examples:
      admin test entra-id --use-stored
      admin test entra-id --tenant-id "tenant-id" --client-id "client-id" --client-secret "secret"

Options:
  --use-stored              Test stored configuration
  -t, --tenant-id TEXT      Entra ID Tenant ID (for direct test)
  -c, --client-id TEXT      Entra ID Application (Client) ID (for direct test)
  -s, --client-secret TEXT  Entra ID Application Client Secret (for direct
                            test)
  --help                    Show this message and exit.

1.1 - Configuring SAML SSO

Steps to configure SAML SSO using the CLI

SAML SSO enables users to authenticate using enterprise‑managed credentials instead of maintaining separate application passwords.

This section describes how to configure SAML Single Sign‑On (SSO) using an external Identity Provider (IdP) in cloud environments such as Entra ID, AWS, and Google Cloud Platform (GCP).

Setting up SAML SSO using the CLI

This section describes how to configure SAML SSO using the PPC CLI.

Prerequisites

Before you begin, ensure the following prerequisites are met:

  • Access to an IdP.
  • Administrative privileges to configure SAML settings in the IdP.
  • Copy the Metadata URL.
  • Users and groups already created in the IdP.
  • Administrative access to the PPC CLI.

The same setup flow applies across Entra ID, AWS, and GCP, with differences limited to the IdP administration interface.

Setting up SAML SSO on Entra ID IdP - An Example

To configure SAML SSO on PPC using Entra ID IdP, perform the following steps:

  1. Log in to the PPC CLI.

  2. Create a SAML provider using the metadata URL from the IdP using the following command.

    admin create saml-providers \
    --alias <saml-provider-alias> \
    --display-name "<saml-provider-display-name>" \
    --config-type metadataUrl \
    --service-provider-entity-id "https://<service-provider-entity-id>" \
    --metadata-url "https://<idp-metadata-url>" \
    

    Uploading a metadata file is not supported. --metadata-url must be used.

    The key parameters are listed below.

  • --alias: Unique identifier for the SAML provider.

  • --display-name: Name shown on the login page.

  • --config-type: Must be metadataUrl.

  • --service-provider-entity-id: Entity ID expected by the IdP.

  • --metadata-url: URL from which SAML metadata is fetched.

    After successful execution, the following message displays.

    SAML provider '<saml-provider-alias>' created successfully!
    
  1. Verify if the SAML provider is created successfully using the following command.

    admin list saml-providers
    

    A list of configured SAML providers appears.

  2. After creating the SAML provider, retrieve the SAML provider details to obtain the Redirect URI using the following command.

    admin get saml-providers <saml-provider-alias>
    

    Note the Redirect URI from the displayed information.

  3. Update the SAML configuration in Entra ID Idp.

    To update the SAML configuration in the Idp, perform the following steps:

    1. Log in to Entra ID IdP.
    2. Navigate to Enterprise applications, and select the application.
    3. In the Basic SAML Configuration, update the Redirect URI noted in the previous step.
  4. In the PPC CLI, create the Entra ID configuration using the following command.

    admin create entra-id --tenant-id "<tenant-id>" --client-id "<client-id>" --client-secret "your-secret-here"
    

    After successful execution, the following message displays.

    Entra ID configuration '<tenant-id>' created successfully!
    

    This confirms trust is established between the IdP and the appliance.

  5. Import the user from Entra ID IdP using the following command.

    admin create entra-id-import-users --json data {
      "users": [
          {
              "userPrincipalName": "john.doe@company.com",
              "email": "john.doe@company.com",
              "firstName": "John",
              "lastName": "Doe",
              "roles": ["security_administrator"],
              "identityProviders": ["Entra ID-IDP"],
              "password": "Password@123"
          }
      ],
    }'
    

    After successful execution, the following message displays.

    Successfully imported 1 user(s)
    
  6. Verify if the user is imported using the following command.

    admin list users
    

    A list of all available users display. The imported user appears in the list. Note the USER_ID.

  7. To get detailed information about a user, run the following command.

    admin get users USER_ID
    

    The user details display. The attributes display user type as external, stating that the user is imported from an external IdP.

  8. Open the Web browser and enter the FQDN of the PPC. The Login page displays.

  9. Click Sign in with SAML SSO.

  10. The screen is redirected to the IdP portal for authentication. If the user is not logged in, the login dialog appears. Provide the user credentials for login.

  11. After logging in successfully, the screen automatically redirects to the PPC Dashboard.

SAML SSO is now configured. Users can authenticate using enterprise‑managed credentials and are granted access based on the roles assigned in the PPC.

Creating users for AWS and GCP

This section describes environments where users are created locally using the Admin CLI, rather than being imported from an external IdP. This procedure is applicable to AWS and GCP deployments where SAML SSO is enabled but users are created using the CLI.

Creating local users for AWS and GCP using the CLI

In AWS and GCP environments, administrators can create users directly using the Admin CLI. These users authenticate through the configured SAML provider, while credentials, roles, and access control are managed locally.

To create the users for AWS and GCP using the CLI, perform the following steps:

  1. Configure the SAML provider using the CLI.

  2. Create a local user, set a password, assign one or more roles to define access permissions, using the following command.

    admin create users \
    --username john.doe \
    --email john.doe@example.com \
    --first-name John \
    --last-name Doe \
    --password StrongPassword123! \
    --roles admin
    

    Here,

    • The --password parameter sets the initial login password.
    • The --roles parameter assigns one or more roles that control user permissions.
  3. The user authenticates via the SAML IdP and is authorized based on locally assigned roles.

  4. To update the roles, run the following command:

    admin set users USER_ID --roles admin,operator
    
  5. To update an existing user password, run the following command:

    admin set update_password USER_ID \
    --old-password OldPassword123! \
    --new-password NewPassword123!
    
  6. To unlock an account, run the following command:

    admin set unlock_user USER_ID --password NewPassword123!
    

Note: In this process, users are not imported from AWS IAM or GCP IAM. Identity authentication is handled through the SAML provider, while user records, passwords, and role assignments are managed locally through the CLI.

Understanding SAML Mappers

SAML mappers define how attributes received from the SAML Identity Provider (IdP) are mapped to local user attributes, roles, or groups during authentication.

SAML mappers are configured per SAML provider and allow administrators to control how identity data is interpreted and applied within the system.

Why SAML Mappers Are Required

SAML assertions typically contain user attributes such as email, username, group membership, or role indicators. SAML mappers translate these attributes into:

  • Local usernames
  • User attributes
  • Role assignments
  • Group memberships

Without SAML mappers, users may authenticate successfully but will not be assigned the correct access permissions.

Note: SAML mappers are evaluated during user authentication. Ensure that the IdP sends the required attributes and that mapper definitions align with the IdP’s SAML assertion format.

2 - Using the Insight Command Line Interface (CLI)

Insight CLI documentation

Main Insight Command

The following command shows to access the help for the insight commands.

insight --help
Usage: insight [OPTIONS] COMMAND [ARGS]...

  Log Management and Log Forwarding commands.

  EXAMPLES:

  # Verify if configuration exists
  insight list fluentd
  or
  insight list syslog

  # Test connection to SIEM
  insight test fluentd --host <fluentd_address> --port <fluentd_port>
  or
  insight test syslog --host <syslog_address> --port <syslog_port>

  # Configure external SIEM
  insight configure fluentd --host <fluentd_address> --port <fluentd_port> --ca_content "<ca.crt_content>"  --cert_content "<client.crt_content>" --key_content "<client.key_content>"
  or
  insight configure syslog --host <syslog_address> --port <syslog_port> --ca_content "<ca.crt_content>"  --cert_content "<client.crt_content>" --key_content "<client.key_content>"

  # Update configurations
  insight update fluentd --host <fluentd_address> --port <fluentd_port> --ca_content "<ca.crt_content>"  --cert_content "<client.crt_content>" --key_content "<client.key_content>"
  or
  insight update syslog --host <syslog_address> --port <syslog_port> --ca_content "<ca.crt_content>"  --cert_content "<client.crt_content>" --key_content "<client.key_content>"

  # Delete if configuration exists
  insight delete fluentd
  or
  insight delete syslog

Options:
  --help  Show this message and exit.

Commands:
  configure  Configure log forwarding to external system.
  delete     Remove log forwarding configurations to external system.
  list       Show the current log forwarding configurations.
  test       Test connectivity to external system.
  update     Update log forwarding configurations.

Configure Command

The following section lists the insight configure commands. The pods take some time to initialize and stabilize, about 15 minutes, after running this command. Avoid updating any more configurations till the pds are ready. Verify the status of the pods using the kubectl get pods -n pty-insightcommand.

Main Configure Command

The following command shows how to access help for the insight configure command.

insight configure --help
Usage: insight configure [OPTIONS] COMMAND [ARGS]...

  Configure log forwarding to external system.

  EXAMPLES:

  # Configure external SIEM
  insight configure fluentd --host <fluentd_address> --port <fluentd_port> --ca_content "<ca.crt_content>"  --cert_content "<client.crt_content>" --key_content "<client.key_content>"
  or
  insight configure syslog --host <syslog_address> --port <syslog_port> --ca_content "<ca.crt_content>"  --cert_content "<client.crt_content>" --key_content "<client.key_content>"

Options:
  --help  Show this message and exit.

Commands:
  fluentd  Set up log forwarding to an external Fluentd server.
  syslog   Set up log forwarding to an external Syslog server.

Configure Fluentd Command

The following command shows how to access help for the insight configure fluentd command.

insight configure fluentd --help
Usage: insight configure fluentd [OPTIONS]

  Set up log forwarding to an external Fluentd server.

  EXAMPLES:

  # Configure external Fluentd server

  insight configure fluentd --host <fluentd_address> --port <fluentd_port>
  --ca_content "<ca.crt_content>"  --cert_content "<client.crt_content>"
  --key_content "<client.key_content>"

  # Configure external Fluentd server (with troubleshooting logs)

  insight configure fluentd --host <fluentd_address> --port <fluentd_port>
  --ca_content "<ca.crt_content>"  --cert_content "<client.crt_content>"
  --key_content "<client.key_content>" --troubleshooting_log True

Options:
  --host TEXT                    External Fluentd server address  [required]
  --port INTEGER                 External Fluentd server port  [required]
  --ca_content TEXT              Content of the CA certificate  [required]
  --cert_content TEXT            Content of the client certificate  [required]
  --key_content TEXT             Content of the client private key  [required]
  --troubleshooting_log  BOOLEAN Enable troubleshooting log forward
  --help                         Show this message and exit.

Configure Syslog Command

The following command shows how to access help for the insight configure syslog command.

insight configure syslog --help

Usage: insight configure syslog [OPTIONS]

  Set up log forwarding to an external Syslog server.

  EXAMPLES:

  # Configure external Syslog server

  insight configure syslog --host <syslog_address> --port <syslog_port>
  --ca_content "<ca.crt_content>"  --cert_content "<client.crt_content>"
  --key_content "<client.key_content>"

  # Configure external Syslog server (with troubleshooting logs)

  insight configure syslog --host <syslog_address> --port <syslog_port>
  --ca_content "<ca.crt_content>"  --cert_content "<client.crt_content>"
  --key_content "<client.key_content>" --troubleshooting_log True

Options:
  --host TEXT                    Syslog server address  [required]
  --port INTEGER                 Syslog server port  [required]
  --ca_content TEXT              Content of the CA certificate  [required]
  --cert_content TEXT            Content of the client certificate  [required]
  --key_content TEXT             Content of the client private key  [required]
  --troubleshooting_log  BOOLEAN Enable troubleshooting log forward
  --help                         Show this message and exit.

Delete Command

The following section lists the insight delete commands. The pods take some time to initialize and stabilize, about 15 minutes, after running this command. Avoid updating any more configurations till the pds are ready. Verify the status of the pods using the kubectl get pods -n pty-insightcommand.

Main Delete Command

The following command shows how to access help for the insight delete command.

insight delete --help
Usage: insight delete [OPTIONS] COMMAND [ARGS]...

  Remove log forwarding configurations to external system.

  EXAMPLES:

  # Delete if configuration exists
  insight delete fluentd
  or
  insight delete syslog

Options:
  --help  Show this message and exit.

Commands:
  fluentd  Remove log forwarding configurations and certificates to external system.
  syslog   Remove log forwarding configurations and certificates to external system.

Delete Fluentd Command

The following command shows how to access help for the insight delete fluentd command.

insight delete fluentd --help
Usage: insight delete fluentd [OPTIONS]

  Remove log forwarding configurations and certificates to external system.

  EXAMPLES:

  # Delete if configuration exists
  insight delete fluentd

Options:
  --help  Show this message and exit.

Delete Syslog Command

The following command shows how to access help for the insight delete syslog command.

insight delete syslog --help
Usage: insight delete syslog [OPTIONS]

  Remove log forwarding configurations and certificates to external system.

  EXAMPLES:

  # Delete if configuration exists
  insight delete syslog

Options:
  --help  Show this message and exit.

List Command

The following section lists the insight list commands.

Main List Command

The following command shows how to access help for the insight list command.

insight list --help
Usage: insight list [OPTIONS] COMMAND [ARGS]...

  Show the current log forwarding configurations.

  EXAMPLES:

  # Verify if configuration exists
  insight list fluentd
  or
  insight list syslog

Options:
  --help  Show this message and exit.

Commands:
  fluentd  Show the current log forwarding configurations.
  syslog   Show the current log forwarding configurations.

List Fluentd Command

The following command shows how to access help for the insight list fluentd command.

insight list fluentd --help
Usage: insight list fluentd [OPTIONS]

  Show the current log forwarding configurations.

  EXAMPLES:

  # Verify if configuration exists
  insight list fluentd

Options:
  --help  Show this message and exit.

List Syslog Command

The following command shows how to access help for the insight list syslog command.

insight list syslog --help
Usage: insight list syslog [OPTIONS]

  Show the current log forwarding configurations.

  EXAMPLES:

  # Verify if configuration exists
  insight list syslog

Options:
  --help  Show this message and exit.

Test Command

The following section lists the insight test commands.

Main Test Command

The following command shows how to access help for the insight test command.

insight test --help
Usage: insight test [OPTIONS] COMMAND [ARGS]...

  Test connectivity to external system.

  EXAMPLES:

  # Test connection to SIEM
  insight test fluentd --host <fluentd_address> --port <fluentd_port>
  or
  insight test syslog --host <syslog_address> --port <syslog_port>

Options:
  --help  Show this message and exit.

Commands:
  fluentd  Test connectivity to external Fluentd server.
  syslog   Test connectivity to external Syslog server.

Test Fluentd Command

The following command shows how to access help for the insight test fluentd command.

insight test fluentd --help
Usage: insight test fluentd [OPTIONS]

  Test connectivity to external Fluentd server.

  EXAMPLES:

  # Test connection
  insight test fluentd --host <fluentd_address> --port <fluentd_port>

Options:
  --host TEXT        External Fluentd server address  [required]
  --port INTEGER     External Fluentd server port  [required]
  --timeout INTEGER  Time allowed for the test  [default: 5]
  --help             Show this message and exit.

Test Syslog Command

The following command shows how to access help for the insight test syslog command.

insight test syslog --help
Usage: insight test syslog [OPTIONS]

  Test connectivity to external Syslog server.

  EXAMPLES:

  # Test connection
  insight test syslog --host <syslog_address> --port <syslog_port>

Options:
  --host TEXT        Syslog server address  [required]
  --port INTEGER     Syslog server port  [required]
  --timeout INTEGER  Time allowed for the test  [default: 5]
  --help             Show this message and exit.

Update Command

The following section lists the insight update commands. The pods take some time to initialize and stabilize, about 15 minutes, after running this command. Avoid updating any more configurations till the pds are ready. Verify the status of the pods using the kubectl get pods -n pty-insightcommand.

Main Update Command

The following command shows how to access help for the insight update command.

insight update --help
Usage: insight update [OPTIONS] COMMAND [ARGS]...

  Update log forwarding configurations.

  EXAMPLES:

  # Update log forwarding configurations to external SIEM
  insight update fluentd --host <fluentd_address> --port <fluentd_port> --ca_content "<ca.crt_content>"  --cert_content "<client.crt_content>" --key_content "<client.key_content>"
  or
  insight update syslog --host <syslog_address> --port <syslog_port> --ca_content "<ca.crt_content>"  --cert_content "<client.crt_content>" --key_content "<client.key_content>"

Options:
  --help  Show this message and exit.

Commands:
  fluentd  Update log forwarding for external Fluentd server.
  syslog   Update log forwarding for external Syslog server.

Update Fluentd Command

The following command shows how to access help for the insight update fluentd command.

insight update fluentd --help
Usage: insight update fluentd [OPTIONS]

  Update log forwarding for external Fluentd server.

  EXAMPLES:

  # Update configurations for external Fluentd server

  insight update fluentd --host <fluentd_address> --port <fluentd_port>
  --ca_content "<ca.crt_content>"  --cert_content "<client.crt_content>"
  --key_content "<client.key_content>"

  # Update configurations for external Fluentd server (with troubleshooting
  logs)

  insight update fluentd --host <fluentd_address> --port <fluentd_port>
  --ca_content "<ca.crt_content>"  --cert_content "<client.crt_content>"
  --key_content "<client.key_content>" --troubleshooting_log True

Options:
  --host TEXT                    External Fluentd server address  [required]
  --port INTEGER                 External Fluentd server port  [required]
  --ca_content TEXT              Content of the CA certificate  [required]
  --cert_content TEXT            Content of the client certificate  [required]
  --key_content TEXT             Content of the client private key  [required]
  --troubleshooting_log  BOOLEAN Enable troubleshooting log forward
  --help                         Show this message and exit.

Update Syslog Command

The following command shows how to access help for the insight update syslog command.

insight update syslog --help
Usage: insight update syslog [OPTIONS]

  Update log forwarding for external Syslog server.

  EXAMPLES:

  # Update configurations for external Syslog server

  insight update syslog --host <syslog_address> --port <syslog_port>
  --ca_content "<ca.crt_content>"  --cert_content "<client.crt_content>"
  --key_content "<client.key_content>"

  # Update configurations for external Syslog server (with troubleshooting
  logs)

  insight update syslog --host <syslog_address> --port <syslog_port>
  --ca_content "<ca.crt_content>"  --cert_content "<client.crt_content>"
  --key_content "<client.key_content>" --troubleshooting_log True

Options:
  --host TEXT                    Syslog server address  [required]
  --port INTEGER                 Syslog server port  [required]
  --ca_content TEXT              Content of the CA certificate  [required]
  --cert_content TEXT            Content of the client certificate  [required]
  --key_content TEXT             Content of the client private key  [required]
  --troubleshooting_log  BOOLEAN Enable troubleshooting log forward
  --help                         Show this message and exit.

2.1 - Sending logs to an external security information and event management (SIEM)

Information to forward the logs generated to the Audit Store and SIEM.

This is an optional step.

The Protegrity infrastructure provides a robust setup for logging and analyzing the logs generated. It might be possible that an existing infrastructure is available for collating and analyzing logs.

In the default setup, the logs are sent from the protectors directly to the Audit Store using the Log Forwarder on the protector. Use the configuration provided in this section to send the logs to the Audit Store and the external SIEM.

Prerequisites

Ensure that the following prerequisites are met:

  • The external SIEM is accessible.
  • The required ports are open on the external SIEM.
  • The certificates for accessing the external SIEM are available.
  • Prepare the CA.pem, client.pem, and client.key certificate content using the following steps:
    1. Navigate to the directory where the certificates from the SIEM are stored.

    2. Run the following command to obtain the CA certificate file content.

      awk '{printf "%s\\n", $0}' <CA_certificate_file>
      

      Example:

      awk '{printf "%s\\n", $0}' CA.pem
      
    3. Run the following command to obtain the client certificate content.

      awk '{printf "%s\\n", $0}' <client_certificate_file>
      

      Example:

      awk '{printf "%s\\n", $0}' client.pem
      
    4. Run the following command to obtain the client key content.

      awk '{printf "%s\\n", $0}' <client_key_file>
      

      Example:

      awk '{printf "%s\\n", $0}' client.key
      
  • Update the configuration on the protectors.

Updating the protector configuration

Configure the protector to send the logs to the fluentd. The fluentd in turn forwards the logs received to the Audit Store and the external location.

  1. Log in and open a CLI on the protector machine.

  2. Back up the existing files.

    1. Navigate to the config.d directory using the following command.

      cd /opt/protegrity/logforwarder/data/config.d
      
    2. Back up the existing out.conf file using the following command.

      cp out.conf out.conf_backup
      
    3. Back up the existing upstream.cfg file using the following command.

      cp upstream.cfg upstream.cfg_backup
      
  3. Update the out.conf file for specifying the logs that must be forwarded to the Audit Store.

    1. Navigate to the /opt/protegrity/logforwarder/data/config.d directory.

    2. Open the out.conf file using a text editor.

    3. Update the file contents with the following code.

      Update the code blocks for all the options with the following information:

      • Update the Name parameter from opensearch to forward.

      • Delete the following Index, Type, and Time_Key parameters:

            Index pty_insight_audit
            Type  _doc
            Time_Key ingest_time_utc            
        
      • Delete the Supress_Type_Name and Buffer_Size parameters:

            Suppress_Type_Name on
            Buffer_Size false
        

      The updated extract of the code is shown here.

      [OUTPUT]
       Name forward
       Match logdata
       Retry_Limit False
       Upstream /opt/protegrity/logforwarder/data/config.d/upstream.cfg
       storage.total_limit_size 256M
       net.max_worker_connections 1
       net.keepalive off
       Workers 1
      
      [OUTPUT]
       Name forward
       Match flulog
       Retry_Limit no_retries
       Upstream /opt/protegrity/logforwarder/data/config.d/upstream.cfg
       storage.total_limit_size 256M
       net.max_worker_connections 1
       net.keepalive off
       Workers 1
      

      Ensure that the file does not have any trailing spaces or line breaks at the end of the file.

    4. Save and close the file.

  4. Update the upstream.cfg file for forwarding the logs to the Audit Store.

    1. Navigate to the /opt/protegrity/logforwarder/data/config.d directory.

    2. Open the upstream.cfg file using a text editor.

    3. Update the file contents with the following code.

      Update the code blocks for all the nodes with the following information:

      • Update the Port to 24284.

      • Delete the Pipeline, tls, and tls.verify parameters:

            Pipeline   logs_pipeline
            tls        on
            tls.verify off
        

      The updated extract of the code is shown here.

      
      [UPSTREAM]
          Name       pty-insight-balancing
      
      [NODE]
          Name       node-1
          Host       <PPC FQDN>
          Port       24284
      

      The was configured in Step 4 of Deploying PPC. Ensure the FQDN does not exceed 50 characters. The code shows information updated for one node. For multiple nodes, update the information for all the nodes.

      Ensure that there are no trailing spaces or line breaks at the end of the file.

    4. Save and close the file.

  5. Restart logforwarder on the protector using the following commands.

    /opt/protegrity/logforwarder/bin/logforwarderctrl stop
    /opt/protegrity/logforwarder/bin/logforwarderctrl start
    
  6. If required, complete the configurations on the remaining protector machines.

  7. Update the fluentd configuration to send logs to the external location using the information from syslog commands or fluentd commands.

syslog commands

The commands provided here are used for sending logs to the Audit Store, retaining the default storage location, and an external syslog SIEM.

Viewing the current configuration

The command to view the log forwarding configurations.

insight list syslog

Verifying connectivity

The command to verify that the external syslog SIEM is accessible.

insight test syslog --host <syslog_address> --port <syslog_port>

Example:

insight test syslog --host 192.168.1.100 --port 6514

Forwarding logs to the syslog server

The command to forward logs to the syslog server.

insight configure syslog --host <syslog_address> --port <syslog_port> --ca_content "<ca.crt_content>"  --cert_content "<client.crt_content>" --key_content "<client.key_content>"

Example:

insight configure syslog --host 192.168.1.110 --port 6514 --ca_content "-----BEGIN CERTIFICATE-----\nMIIFmDCCA4CgAwIBAgIIWF8OX+P4jAAwDQYJKoZIhvcNAQELBQAwVzEYMBYGA1UE\nCgwPUHJvdGVncml0eSBJbmMuMQswCQYDVQQGEwJVUzEuMCwGA1UEAwwlUHJvdGVn\ncml0eSBSb290IENBIC0gWklTbkdKRE5tekdPdGEyQzAgGA8yMDI1MTIyMTAwMDAw\nMFoXDTM1MTIyMDA3NDE1MFowVzEYMBYGA1UECgwPUHJvdGVncml0eSBJbmMuMQsw\nCQYDVQQGEwJVUzEuMCwGA1UEAwwlUHJvdGVncml0eSBSb290IENBIC0gWklTbkdK\nRE5tekdPdGEyQzCCAiIwDQYJKoZIhvcNAQEBBQADggIPADCCAgoCggIBAL6nK47Y\n/hs1nBnHxg2/S6ieL/JH9H6M9321qHaSIbqAS2KBy2iNDoy3EhKvHXOgd4TgWc7+\nMGiREDK9QsOZ1UKFn5p5cXt0lkGsRSVB5sh2GurGxCtKEwtXlK8OGAWhz46dmjEr\nT02SH7H6WQA+Zh8+OTdzjpo/aujdI6pGVslSY/ulFcqQF16U7aRTmobPpdSZuFWN\nuBcoAXLhDBLutCWQaYSodksRha6I6olrlSditoHHGOnMWC6S4/+NT1XtSvBEIhVn\nMDRym6UKLNlhR+bb3lyGK5HgA2frXduNIL244z931Ii+JAnvpIsZrQ9k1UghG0L7\n3zLTMSCf1y3yWKhXWnPcN41zWeqiF+gk0zFoIQiaDPjhqNyjzTheXX8YqiTf226E\nxTg1Xrac3LF5Ju+3gCioUzpOo3WbphDmZfDTMBj0cWn7GszLkiNd/AX5bLf/+OdJ\n9KaZSOQcit4A9bxERWFS0vT8aGfN43mUFXrpKLmpltZkmtt4XloEeGndZbHF60hy\n+nRzJVNs9B63xP9+NdpWgvoiRVOBKB04XVcNC6nMCMwYjJRLmBzQQ9PT3dQ2dnpj\nj0TuU/44bj5S5t6aVvEOeKanHHeVqRQm8Kzt4WfDvjp1ASOkApvA5+Xs+DpcKbWH\nMCAZDQpi2vWu8d+c569FvN4e0SbP0qM26NgvAgMBAAGjZjBkMBIGA1UdEwEB/wQI\nMAYBAf8CAQAwDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBSnfq6PGf8AwEL9XGyQ\nM1I6087OzjAfBgNVHSMEGDAWgBSnfq6PGf8AwEL9XGyQM1I6087OzjANBgkqhkiG\n9w0BAQsFAAOCAgEALXZZNaa60cpYNFEXgr780IqKUdZa995OvRUs1dCYd4WqzzJD\nVad8Z48GJX3/u/XAk2UM+mUSGaFowqhek58YX0b24O0PG+y3O0XT0EX/+80Fu+Kt\nkPSbiaPyeYxGqEjwed/Y9X5AJig68NA/FRcT5dq2sWA8hcej8Ghm6D3gu9PdBWpk\nRstITsdaSfx6N+avJ0keGMHqLDLSr948XbehRHH9FnvkPfDtkwKzNwhYmeB6/c+v\nal/JLfPy6VWi3fK37XmuhSh2aZ/vsjT7sxvfFTndUVBeumvCS4wW+bByxpC5XBHW\nB1TrPCczqaDqDD/ib1YCLfY6Qgi8IINEsDDkDgpevW2JxSjTywGGYea4J3M5oOdg\nNhjNWt00H/rugEzkB9hP4po9QHSFX5qWgzT/ws01mOcaOr4UQ8msSyVZmfpJkdHy\nx4n4jhvdlsQKhKM7OmpuXGIA7r/lqU5WDQl1Erj/6cNeWp4vx+606mvbjpzk2Lcp\ni0wBnz27jvN4Xvw+zBMzMBMm5iPwKDMKUyo3q87DFC6lBvBwF0kbPom+yLhHH/rF\n0hr21PATUrHHutFebZ3ZqZwusiKKOoD6fpQrF2mwnVGHQPwTUamSFKQZsf9jw3ic\n4zY2nruXc0OSWS2gf1FKRDxpgpMUjthA3nO1YJuiP4I7fB5mqSoYY8bsyhc=\n-----END CERTIFICATE-----\n"  --cert_content "-----BEGIN CERTIFICATE-----\nMIIFHDCCAwSgAwIBAgIIcePfAqBgEAAwDQYJKoZIhvcNAQELBQAwVzEYMBYGA1UE\nCgwPUHJvdGVncml0eSBJbmMuMQswCQYDVQQGEwJVUzEuMCwGA1UEAwwlUHJvdGVn\ncml0eSBSb290IENBIC0gWkldeedKRE5tekdPdGEyQzAgGA8yMDI1MTIyMTAwMDAw\nMFoXDTM1MTIyMDA3NDE1MlowQzEYMBYGA1UECgwPUHJvdGVncml0eSBJbmMuMQsw\nCQYDVQQGEwJVUzEaMBgGA1UEAwwRUHJvdGVncml0eSBDbGllbnQwggIiMA0GCSqG\nSIb3DQEBAQUAA4ICDwAwggIKAoICAQCn7/6ZMkJkt1/9iOj+0S8aE64w69iSpEUH\ns/wlCJG5mx7QhMKwTeJSjXO+oVSDH7Kr+eoIpTh4Zt6aC9oUaynJ4tLpE1/xb5V9\n2Brafthx6b49/kgeCEvDQtFbmwJPOZ9f2W71oK8s6zgM/dASpH4LgAu3Y7vfJ9eH\nZB63MuDFc429WyDuXQ4xnQ07RUKd40Q7JSKt4WNIdl7IVlAdAwTg+/4+xhYohSgi\ndi82XJRD0MCs0EQg6K5G0Do8DcAmdBsE3LTjJr55G1Juscv6qfh0BCTuyhJpS3dI\nQa5YiSuTIDiO45h8V4BS/+AB42tYSejvQKVmCbaCb9aqwn9LjrM0G4GYU0llvVi0\nvi8d76s9wb1V0Au0lkr/xFMCXebYWGr1I48kKlFKf0l11fP0rjAQO+qWwNJI1ax8\n7g1dh49NwBJbnZJvlv1Hb5KlrOvwHfr8UkFBZ1GVBZum0wbwFirZXxuU43AZp2S\nnwVDl+i3fP4FEu8SMIijhU3NQeA8PbVcyx3xgsOiNO3wXp2Rt380D4Ynw5A7pF6Y\nUD4TefMzUCgDFEykuUzZlnT9mBR34F4bYUQSLPPqWDXedAHfuUh9na2ws3BltpAV\nvpNM9xWl2NQN6Xsp+gAuMwIHcj0FTiJ38UFyzvPCJ/e+FsW3qWQkgDNhUYlOAplf\np8o/+1Fm7wIDAQABMA0GCSqGSIb3DQEBCwUAA4ICAQB+s91FIrthptvdBygBsen4\nLaQpfAGIEyeiG1VdTeXtlev2HjPk0p3FnbjZVQhyT00SCWPHa7Vd6ypIqlIFYvnq\nUvUc0fkUqnpAeRWK9p1bif32Qs3rS6Q8mDDVbe2BP/gxOdrPkKPZLZ/rA4cYQAh0\nx/RsdxXtiBkOQpNjZO+UUbyPqohRKek/yLEiltsdBcXeFzcUbZMxks8CAmKVB3Pn\n69NmqZOcJtcj0ydBKL1MdUxPSHXks0z8afVa5IlbJaeaa+Ef0dMDzL/JdH7FslaZ\ntHvgJpq2RinHx1emIlmAk1ji0L/4MCqRrCdNU1rVIob7amyd6gkAkEIYUlsHFEp1\nBdVU8hh4F9UQ6dQvZ6etO4/Pus8t4DjdY8Xllsgot4NXL94r/asG+z3QjIIokUfu\nEDRorE82P809hWhRVbZ1A66/3XERD4BGmn3PML94YdC+vOxricqkrZ4oJDD3gbow\nfJWQIZ96hMndAG0H055qvgoWNqjifw9KXLHqelHWOiyJftJrchCOwZ3gRlA8WaOy\nHvCNN1VzCOfaNw9YJlJ4c3DLzwwRxo/KinycCvDaYGhBLTkWjZFqqkdwm4cqK9cf\n3joxQKh51a5ENZ2hoJUEvlcfjerQGPMRMUR4n3GwPf7Vca3fd+S1+qA7tcldEKx9\nHte3R2N5rYd/obrdkh5J0A==\n-----END CERTIFICATE-----\n" --key_content "-----BEGIN PRIVATE KEY-----\nMIIJQgIBADANBgkqhkiG9w0BAQEFAASCCSwwggkoAgEAAoICAQCn7/6ZMkJkt1/9\niOj+0S8aE64w69iSpEUHs/wlCJG5mx7QhMKwTeJSjXO+oVSDH7Kr+eoIpTh4Zt6a\nC9oUaynJ4tLpE1/xb5V92Brafthx6b49/kgeCEvDQtFbmwJPOZ9f2W71oK8s6zgM\n/dASpH4LgAu3Y7vfJ9eHZB63MuDFc429WyDuXQ4xnQ07RUKd40Q7JSKt4WNIdl7I\nVlAdAwTg+/4+xhYohSgidi82XJRD0MCs0EQg6K5G0Do8DcAmdBsE3LTjJr55G1Ju\nscv6qfh0BCTuyhJpS3dIQa5YiSuTIDiO45h8V4BS/+AB42tYSejvQKVmCbaCb9aq\nwn9LjrM0G4GYU0llvVi0vi8d76s9wb1V0Au0lkr/xFMCXebYWGr1I48kKlFKf0l1\n1fP0rjAQO+qWwNJI1ax87g1dh49NwBJbnZJvlv1Hb5Kls2rvwHVcp4UkFBZ1GVBZu\nm0wbwFirZXxuU43AZp2SnwVDl+i3fP4FEu8SMIijhU3NQeA8PbVcyx3xgsOiNO3w\nXp2Rt380D4Ynw5A7pF6YUD4TefMzUCgDFEykuUzZlnT9mBR34F4bYUQSLPPqWDXe\ndAHfuUh9na2ws3BltpAVvpNM9xWl2NQN6Xsp+gAuMwIHcj0FTiJ38UFyzvPCJ/e+\nFsW3qWQkgDNhUYlOAplfp8o/+1Fm7wIDAQABAoICAQCbaiSpzbNX1cRFs7A8MYZv\nkYsAxyJ0AwXHLS/Jbfa+V+naeyJZWpp6X2GgJ1k4x9roAK4vNgfelQSodxNpFgtk\nRD9/Z2jA3Mzx205uqjjQospmQK6o7HCA0ZNCPV+TxfXSFDz1n7C91yjWDQXEWuoy\n5lrxaqDw0cRKDcPHMpSE5n1jobQGI6QBEiCum1gdGbeJLMK9O/pPkwwARrB5SNP5\nCfuuSE81TJVp3wmuO1sSr1vAEjUaZ3rxGb7q2Kbcb1KZ206jcLWRClHtEyl8XlQJ\nudQcEHGddDN9cRtR4A+tZoIw6juxxqCBLz81QCuVV0D0OVVX6uE2MR3uhXSawwgEU\nVWIcWvgXkTgEbg/KgrZ3R9VN7XjawMLVv+3dLQp4idD7keoKWCOHXZtdEXalCmLV\nQQxNtwHkjF0yG+mu6nFEiy89onvTLJtzwriu16BYf8kVnUyd3F94LYQZDWRxCuuG\nNppl0VfikZGM+0P0PpKGy3Yn+qR6d4NhaYFxbrgezRg0KlshWpM/N6ZISBj9QjsZ\nPID4oVDNiTk0nEiHlz4SYqsGrTmPdEIwLTO0QL2SFrcNwqh+qT50s7QFqu+Mwl8E\nieRXdEc5mV0qTQvUWPjNh0l6oEwsKi0dxUL5j4utr3WQgk1Fq/1LNgVFL/rBbAIX\ncI3hmU3UQBiTUtzJ3iDytQKCAQEA3LpDbn7TAwr7DMwA1nBTrv5bwGKN7SGan6fN\nL9BI0uyW3H9EZtlhE2kxapF20//gMlvIYO1kW+vySvXTK6IrBzb9s8dzycqbhpyP\n1Z7HQHJeRjNuExTHlX8hU2kW/evmWeRswJwSo37zf6XWMBN4D/i78OEbNDpTLFDA\n2iYWGx2+Cex7nzsSI1omOhek4UyejKsk4Iv2621ezH2mTsHfyxajP/GsCUIHDB6r\nB2nL8YzY/u4nzOVXu5N+sSthQTn3L4KiFavlOd00cCL22J7Dk15CyXn11MHxdo1p\npXZD/sEJfgmiWvroFlHBDRQRzHhPO7j0SzrssOkysNq/aW1eGQKCAQEAwsYkdUWt\nx0fRSaKyC4IJhsKiFcceZdbmHXPd1iaK+oAGhTzz3xDBDlQYbwy6ej8uk8/3PqBW\nfZPOWD9DszTE7k/Rsd4jwVFMD2daE09JVGyPZ7bq4X3qQ7oL120b6Oi1ZuYIXMPs\nlJzgQbOyPzUZess1OUSNwfB8pZhMkjvgmkkSUlZgyQx5+PRW9cZsf4POO9vCAFRL\nOyNlPMAqT1vvGbtatnHc6iY0v1Gl5J0NJfrzpd6b/Cr619NflpSUw6nEd0PLaGl7\naTqCPdMb5Fh7iISmysfSgVavZo5nIvRNY8vVQX8MBaQdmTKXXfYFbiYgZ+uL4hWg\nlTYXdQGQlIx+RwKCAQAjCKVfSl3vo7SJKXAQmS+PHOwvMvVX5/eE07trlWGZqNeh\nE8olkOcpj466XXBA4eIR3COHzuYY+PAyGaZ0zH6L3JyUBlpIcxIQYZUq0NLLVdvE\nxLD58lhjUBRYCtwNXX3oUqs4Pw1uSd4YKpg+dTifQFmEOBZ7Sa6d4AtcFKN5llTt\nek18zoFofwyGN+6BnAmmRhvKUCzW3TsoteDJq1f8AhHTOmaV6Zb4w31d5drq8fIX\nNHG4wcYVDaoUMNB06+Bh+BgF3Iy7jHKgQcxwQXLFVza+h88O/+F1caiNDKJqMvVw\nvdK5Ig3oTP2ZN9BDZe0di5OqxSWARuM20uGCuEsxAoIBABMLXLU6wushUo1ooxAM\n/vF2RnLqrUY35PgsRByUWDJ2Ii0U8KN29+l2v4zcKb+aPeumAf7Vnp9YvGxUg0Ia\nfsbudwp1NfnJAS7gZCZPMlRW6Q6zC/RQY3+LyWye9oOnfVU6WMb5QUCmtia2c09K\n2drv05xt345+/TET2yjRQfzT+D6kw4Hk/mghO/98D0/Ii3m+2xE9LL3zkAqIn5py\n2sYhU5VTPM6IPdAXI6le0dJM31Xwlj/p0+0Wddo7XPBkwRkIP/NNnQuE9QcmhSum\nmy2WCtj5ANQ0raHRerQoPwjq/UcSLRLAIUTBdZtyWsWSZMjEd0D77F+qklCWfpSH\nyDECggEAEaCankeqpmPcSBDdvHZ9TP42aYqvvgrb36bK8A4HdGujx2dWafPcLojm\nizEtUPv2nVU2sGjGmPct5gSCS0oSwjVoIj7UKjT1dLN2QA115mFuZXNsz7UEifdU\n6XuIHztTcDTmhsDGx/XtsnZFyfEl9z3zZIkO4aJ9lbBiyw5LamGD1ykQ2DavxCFE\neFalDX9PGS/VERX9foHLLXDyEXYuoo8pf3ltupYmqbxMSX5Hf1NvtqYBSTvYiaCv\nmQJ3EuuxjzxXcCuI0YWPcAxlAViz9NAzgk+gxbOB6kEHvq/GWWRebQdvGdSHE9zV\ng5HfdOn7snl93cZxCP+JcOFG55h0Dg==\n-----END PRIVATE KEY-----\n"
insight configure syslog --host <syslog_address> --port <syslog_port> --ca_content "<ca.crt_content>"  --cert_content "<client.crt_content>" --key_content "<client.key_content>" --troubleshooting_log True

Example:

insight configure syslog --host 192.168.1.110 --port 6514 --ca_content "-----BEGIN CERTIFICATE-----\nMIIFmDCCA4CgAwIBAgIIWF8OX+P4jAAwDQYJKoZIhvcNAQELBQAwVzEYMBYGA1UE\nCgwPUHJvdGVncml0eSBJbmMuMQswCQYDVQQGEwJVUzEuMCwGA1UEAwwlUHJvdGVn\ncml0eSBSb290IENBIC0gWklTbkdKRE5tekdPdGEyQzAgGA8yMDI1MTIyMTAwMDAw\nMFoXDTM1MTIyMDA3NDE1MFowVzEYMBYGA1UECgwPUHJvdGVncml0eSBJbmMuMQsw\nCQYDVQQGEwJVUzEuMCwGA1UEAwwlUHJvdGVncml0eSBSb290IENBIC0gWklTbkdK\nRE5tekdPdGEyQzCCAiIwDQYJKoZIhvcNAQEBBQADggIPADCCAgoCggIBAL6nK47Y\n/hs1nBnHxg2/S6ieL/JH9H6M9321qHaSIbqAS2KBy2iNDoy3EhKvHXOgd4TgWc7+\nMGiREDK9QsOZ1UKFn5p5cXt0lkGsRSVB5sh2GurGxCtKEwtXlK8OGAWhz46dmjEr\nT02SH7H6WQA+Zh8+OTdzjpo/aujdI6pGVslSY/ulFcqQF16U7aRTmobPpdSZuFWN\nuBcoAXLhDBLutCWQaYSodksRha6I6olrlSditoHHGOnMWC6S4/+NT1XtSvBEIhVn\nMDRym6UKLNlhR+bb3lyGK5HgA2frXduNIL244z931Ii+JAnvpIsZrQ9k1UghG0L7\n3zLTMSCf1y3yWKhXWnPcN41zWeqiF+gk0zFoIQiaDPjhqNyjzTheXX8YqiTf226E\nxTg1Xrac3LF5Ju+3gCioUzpOo3WbphDmZfDTMBj0cWn7GszLkiNd/AX5bLf/+OdJ\n9KaZSOQcit4A9bxERWFS0vT8aGfN43mUFXrpKLmpltZkmtt4XloEeGndZbHF60hy\n+nRzJVNs9B63xP9+NdpWgvoiRVOBKB04XVcNC6nMCMwYjJRLmBzQQ9PT3dQ2dnpj\nj0TuU/44bj5S5t6aVvEOeKanHHeVqRQm8Kzt4WfDvjp1ASOkApvA5+Xs+DpcKbWH\nMCAZDQpi2vWu8d+c569FvN4e0SbP0qM26NgvAgMBAAGjZjBkMBIGA1UdEwEB/wQI\nMAYBAf8CAQAwDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBSnfq6PGf8AwEL9XGyQ\nM1I6087OzjAfBgNVHSMEGDAWgBSnfq6PGf8AwEL9XGyQM1I6087OzjANBgkqhkiG\n9w0BAQsFAAOCAgEALXZZNaa60cpYNFEXgr780IqKUdZa995OvRUs1dCYd4WqzzJD\nVad8Z48GJX3/u/XAk2UM+mUSGaFowqhek58YX0b24O0PG+y3O0XT0EX/+80Fu+Kt\nkPSbiaPyeYxGqEjwed/Y9X5AJig68NA/FRcT5dq2sWA8hcej8Ghm6D3gu9PdBWpk\nRstITsdaSfx6N+avJ0keGMHqLDLSr948XbehRHH9FnvkPfDtkwKzNwhYmeB6/c+v\nal/JLfPy6VWi3fK37XmuhSh2aZ/vsjT7sxvfFTndUVBeumvCS4wW+bByxpC5XBHW\nB1TrPCczqaDqDD/ib1YCLfY6Qgi8IINEsDDkDgpevW2JxSjTywGGYea4J3M5oOdg\nNhjNWt00H/rugEzkB9hP4po9QHSFX5qWgzT/ws01mOcaOr4UQ8msSyVZmfpJkdHy\nx4n4jhvdlsQKhKM7OmpuXGIA7r/lqU5WDQl1Erj/6cNeWp4vx+606mvbjpzk2Lcp\ni0wBnz27jvN4Xvw+zBMzMBMm5iPwKDMKUyo3q87DFC6lBvBwF0kbPom+yLhHH/rF\n0hr21PATUrHHutFebZ3ZqZwusiKKOoD6fpQrF2mwnVGHQPwTUamSFKQZsf9jw3ic\n4zY2nruXc0OSWS2gf1FKRDxpgpMUjthA3nO1YJuiP4I7fB5mqSoYY8bsyhc=\n-----END CERTIFICATE-----\n"  --cert_content "-----BEGIN CERTIFICATE-----\nMIIFHDCCAwSgAwIBAgIIcePfAqBgEAAwDQYJKoZIhvcNAQELBQAwVzEYMBYGA1UE\nCgwPUHJvdGVncml0eSBJbmMuMQswCQYDVQQGEwJVUzEuMCwGA1UEAwwlUHJvdGVn\ncml0eSBSb290IENBIC0gWkldeedKRE5tekdPdGEyQzAgGA8yMDI1MTIyMTAwMDAw\nMFoXDTM1MTIyMDA3NDE1MlowQzEYMBYGA1UECgwPUHJvdGVncml0eSBJbmMuMQsw\nCQYDVQQGEwJVUzEaMBgGA1UEAwwRUHJvdGVncml0eSBDbGllbnQwggIiMA0GCSqG\nSIb3DQEBAQUAA4ICDwAwggIKAoICAQCn7/6ZMkJkt1/9iOj+0S8aE64w69iSpEUH\ns/wlCJG5mx7QhMKwTeJSjXO+oVSDH7Kr+eoIpTh4Zt6aC9oUaynJ4tLpE1/xb5V9\n2Brafthx6b49/kgeCEvDQtFbmwJPOZ9f2W71oK8s6zgM/dASpH4LgAu3Y7vfJ9eH\nZB63MuDFc429WyDuXQ4xnQ07RUKd40Q7JSKt4WNIdl7IVlAdAwTg+/4+xhYohSgi\ndi82XJRD0MCs0EQg6K5G0Do8DcAmdBsE3LTjJr55G1Juscv6qfh0BCTuyhJpS3dI\nQa5YiSuTIDiO45h8V4BS/+AB42tYSejvQKVmCbaCb9aqwn9LjrM0G4GYU0llvVi0\nvi8d76s9wb1V0Au0lkr/xFMCXebYWGr1I48kKlFKf0l11fP0rjAQO+qWwNJI1ax8\n7g1dh49NwBJbnZJvlv1Hb5KlrOvwHfr8UkFBZ1GVBZum0wbwFirZXxuU43AZp2S\nnwVDl+i3fP4FEu8SMIijhU3NQeA8PbVcyx3xgsOiNO3wXp2Rt380D4Ynw5A7pF6Y\nUD4TefMzUCgDFEykuUzZlnT9mBR34F4bYUQSLPPqWDXedAHfuUh9na2ws3BltpAV\nvpNM9xWl2NQN6Xsp+gAuMwIHcj0FTiJ38UFyzvPCJ/e+FsW3qWQkgDNhUYlOAplf\np8o/+1Fm7wIDAQABMA0GCSqGSIb3DQEBCwUAA4ICAQB+s91FIrthptvdBygBsen4\nLaQpfAGIEyeiG1VdTeXtlev2HjPk0p3FnbjZVQhyT00SCWPHa7Vd6ypIqlIFYvnq\nUvUc0fkUqnpAeRWK9p1bif32Qs3rS6Q8mDDVbe2BP/gxOdrPkKPZLZ/rA4cYQAh0\nx/RsdxXtiBkOQpNjZO+UUbyPqohRKek/yLEiltsdBcXeFzcUbZMxks8CAmKVB3Pn\n69NmqZOcJtcj0ydBKL1MdUxPSHXks0z8afVa5IlbJaeaa+Ef0dMDzL/JdH7FslaZ\ntHvgJpq2RinHx1emIlmAk1ji0L/4MCqRrCdNU1rVIob7amyd6gkAkEIYUlsHFEp1\nBdVU8hh4F9UQ6dQvZ6etO4/Pus8t4DjdY8Xllsgot4NXL94r/asG+z3QjIIokUfu\nEDRorE82P809hWhRVbZ1A66/3XERD4BGmn3PML94YdC+vOxricqkrZ4oJDD3gbow\nfJWQIZ96hMndAG0H055qvgoWNqjifw9KXLHqelHWOiyJftJrchCOwZ3gRlA8WaOy\nHvCNN1VzCOfaNw9YJlJ4c3DLzwwRxo/KinycCvDaYGhBLTkWjZFqqkdwm4cqK9cf\n3joxQKh51a5ENZ2hoJUEvlcfjerQGPMRMUR4n3GwPf7Vca3fd+S1+qA7tcldEKx9\nHte3R2N5rYd/obrdkh5J0A==\n-----END CERTIFICATE-----\n" --key_content "-----BEGIN PRIVATE KEY-----\nMIIJQgIBADANBgkqhkiG9w0BAQEFAASCCSwwggkoAgEAAoICAQCn7/6ZMkJkt1/9\niOj+0S8aE64w69iSpEUHs/wlCJG5mx7QhMKwTeJSjXO+oVSDH7Kr+eoIpTh4Zt6a\nC9oUaynJ4tLpE1/xb5V92Brafthx6b49/kgeCEvDQtFbmwJPOZ9f2W71oK8s6zgM\n/dASpH4LgAu3Y7vfJ9eHZB63MuDFc429WyDuXQ4xnQ07RUKd40Q7JSKt4WNIdl7I\nVlAdAwTg+/4+xhYohSgidi82XJRD0MCs0EQg6K5G0Do8DcAmdBsE3LTjJr55G1Ju\nscv6qfh0BCTuyhJpS3dIQa5YiSuTIDiO45h8V4BS/+AB42tYSejvQKVmCbaCb9aq\nwn9LjrM0G4GYU0llvVi0vi8d76s9wb1V0Au0lkr/xFMCXebYWGr1I48kKlFKf0l1\n1fP0rjAQO+qWwNJI1ax87g1dh49NwBJbnZJvlv1Hb5Kls2rvwHVcp4UkFBZ1GVBZu\nm0wbwFirZXxuU43AZp2SnwVDl+i3fP4FEu8SMIijhU3NQeA8PbVcyx3xgsOiNO3w\nXp2Rt380D4Ynw5A7pF6YUD4TefMzUCgDFEykuUzZlnT9mBR34F4bYUQSLPPqWDXe\ndAHfuUh9na2ws3BltpAVvpNM9xWl2NQN6Xsp+gAuMwIHcj0FTiJ38UFyzvPCJ/e+\nFsW3qWQkgDNhUYlOAplfp8o/+1Fm7wIDAQABAoICAQCbaiSpzbNX1cRFs7A8MYZv\nkYsAxyJ0AwXHLS/Jbfa+V+naeyJZWpp6X2GgJ1k4x9roAK4vNgfelQSodxNpFgtk\nRD9/Z2jA3Mzx205uqjjQospmQK6o7HCA0ZNCPV+TxfXSFDz1n7C91yjWDQXEWuoy\n5lrxaqDw0cRKDcPHMpSE5n1jobQGI6QBEiCum1gdGbeJLMK9O/pPkwwARrB5SNP5\nCfuuSE81TJVp3wmuO1sSr1vAEjUaZ3rxGb7q2Kbcb1KZ206jcLWRClHtEyl8XlQJ\nudQcEHGddDN9cRtR4A+tZoIw6juxxqCBLz81QCuVV0D0OVVX6uE2MR3uhXSawwgEU\nVWIcWvgXkTgEbg/KgrZ3R9VN7XjawMLVv+3dLQp4idD7keoKWCOHXZtdEXalCmLV\nQQxNtwHkjF0yG+mu6nFEiy89onvTLJtzwriu16BYf8kVnUyd3F94LYQZDWRxCuuG\nNppl0VfikZGM+0P0PpKGy3Yn+qR6d4NhaYFxbrgezRg0KlshWpM/N6ZISBj9QjsZ\nPID4oVDNiTk0nEiHlz4SYqsGrTmPdEIwLTO0QL2SFrcNwqh+qT50s7QFqu+Mwl8E\nieRXdEc5mV0qTQvUWPjNh0l6oEwsKi0dxUL5j4utr3WQgk1Fq/1LNgVFL/rBbAIX\ncI3hmU3UQBiTUtzJ3iDytQKCAQEA3LpDbn7TAwr7DMwA1nBTrv5bwGKN7SGan6fN\nL9BI0uyW3H9EZtlhE2kxapF20//gMlvIYO1kW+vySvXTK6IrBzb9s8dzycqbhpyP\n1Z7HQHJeRjNuExTHlX8hU2kW/evmWeRswJwSo37zf6XWMBN4D/i78OEbNDpTLFDA\n2iYWGx2+Cex7nzsSI1omOhek4UyejKsk4Iv2621ezH2mTsHfyxajP/GsCUIHDB6r\nB2nL8YzY/u4nzOVXu5N+sSthQTn3L4KiFavlOd00cCL22J7Dk15CyXn11MHxdo1p\npXZD/sEJfgmiWvroFlHBDRQRzHhPO7j0SzrssOkysNq/aW1eGQKCAQEAwsYkdUWt\nx0fRSaKyC4IJhsKiFcceZdbmHXPd1iaK+oAGhTzz3xDBDlQYbwy6ej8uk8/3PqBW\nfZPOWD9DszTE7k/Rsd4jwVFMD2daE09JVGyPZ7bq4X3qQ7oL120b6Oi1ZuYIXMPs\nlJzgQbOyPzUZess1OUSNwfB8pZhMkjvgmkkSUlZgyQx5+PRW9cZsf4POO9vCAFRL\nOyNlPMAqT1vvGbtatnHc6iY0v1Gl5J0NJfrzpd6b/Cr619NflpSUw6nEd0PLaGl7\naTqCPdMb5Fh7iISmysfSgVavZo5nIvRNY8vVQX8MBaQdmTKXXfYFbiYgZ+uL4hWg\nlTYXdQGQlIx+RwKCAQAjCKVfSl3vo7SJKXAQmS+PHOwvMvVX5/eE07trlWGZqNeh\nE8olkOcpj466XXBA4eIR3COHzuYY+PAyGaZ0zH6L3JyUBlpIcxIQYZUq0NLLVdvE\nxLD58lhjUBRYCtwNXX3oUqs4Pw1uSd4YKpg+dTifQFmEOBZ7Sa6d4AtcFKN5llTt\nek18zoFofwyGN+6BnAmmRhvKUCzW3TsoteDJq1f8AhHTOmaV6Zb4w31d5drq8fIX\nNHG4wcYVDaoUMNB06+Bh+BgF3Iy7jHKgQcxwQXLFVza+h88O/+F1caiNDKJqMvVw\nvdK5Ig3oTP2ZN9BDZe0di5OqxSWARuM20uGCuEsxAoIBABMLXLU6wushUo1ooxAM\n/vF2RnLqrUY35PgsRByUWDJ2Ii0U8KN29+l2v4zcKb+aPeumAf7Vnp9YvGxUg0Ia\nfsbudwp1NfnJAS7gZCZPMlRW6Q6zC/RQY3+LyWye9oOnfVU6WMb5QUCmtia2c09K\n2drv05xt345+/TET2yjRQfzT+D6kw4Hk/mghO/98D0/Ii3m+2xE9LL3zkAqIn5py\n2sYhU5VTPM6IPdAXI6le0dJM31Xwlj/p0+0Wddo7XPBkwRkIP/NNnQuE9QcmhSum\nmy2WCtj5ANQ0raHRerQoPwjq/UcSLRLAIUTBdZtyWsWSZMjEd0D77F+qklCWfpSH\nyDECggEAEaCankeqpmPcSBDdvHZ9TP42aYqvvgrb36bK8A4HdGujx2dWafPcLojm\nizEtUPv2nVU2sGjGmPct5gSCS0oSwjVoIj7UKjT1dLN2QA115mFuZXNsz7UEifdU\n6XuIHztTcDTmhsDGx/XtsnZFyfEl9z3zZIkO4aJ9lbBiyw5LamGD1ykQ2DavxCFE\neFalDX9PGS/VERX9foHLLXDyEXYuoo8pf3ltupYmqbxMSX5Hf1NvtqYBSTvYiaCv\nmQJ3EuuxjzxXcCuI0YWPcAxlAViz9NAzgk+gxbOB6kEHvq/GWWRebQdvGdSHE9zV\ng5HfdOn7snl93cZxCP+JcOFG55h0Dg==\n-----END PRIVATE KEY-----\n" --troubleshooting_log True

The pods take some time to initialize and stabilize after running this command. Verify the status of the pods using the kubectl get pods -n pty-insightcommand. Avoid updating any more configurations till the pods are ready.

Configuring the syslog that receives the logs

The logs forwarded to the SIEM are captured by syslog on the SIEM. Ensure that the syslog on the SIEM is configured to send the logs to the required location, such as, a file or another system. For more information about the forwarding logs to various systems, refer to the rsyslog documentation.

Updating the log forwarding configuration

The command to update the logs forwarding settings to the syslog server.

insight update syslog --host <syslog_address> --port <syslog_port> --ca_content "<ca.crt_content>"  --cert_content "<client.crt_content>" --key_content "<client.key_content>"

Example:

insight update syslog --host 192.168.1.110 --port 6514 --ca_content "-----BEGIN CERTIFICATE-----\nMIIFmDCCA4CgAwIBAgIIWF8OX+P4jAAwDQYJKoZIhvcNAQELBQAwVzEYMBYGA1UE\nCgwPUHJvdGVncml0eSBJbmMuMQswCQYDVQQGEwJVUzEuMCwGA1UEAwwlUHJvdGVn\ncml0eSBSb290IENBIC0gWklTbkdKRE5tekdPdGEyQzAgGA8yMDI1MTIyMTAwMDAw\nMFoXDTM1MTIyMDA3NDE1MFowVzEYMBYGA1UECgwPUHJvdGVncml0eSBJbmMuMQsw\nCQYDVQQGEwJVUzEuMCwGA1UEAwwlUHJvdGVncml0eSBSb290IENBIC0gWklTbkdK\nRE5tekdPdGEyQzCCAiIwDQYJKoZIhvcNAQEBBQADggIPADCCAgoCggIBAL6nK47Y\n/hs1nBnHxg2/S6ieL/JH9H6M9321qHaSIbqAS2KBy2iNDoy3EhKvHXOgd4TgWc7+\nMGiREDK9QsOZ1UKFn5p5cXt0lkGsRSVB5sh2GurGxCtKEwtXlK8OGAWhz46dmjEr\nT02SH7H6WQA+Zh8+OTdzjpo/aujdI6pGVslSY/ulFcqQF16U7aRTmobPpdSZuFWN\nuBcoAXLhDBLutCWQaYSodksRha6I6olrlSditoHHGOnMWC6S4/+NT1XtSvBEIhVn\nMDRym6UKLNlhR+bb3lyGK5HgA2frXduNIL244z931Ii+JAnvpIsZrQ9k1UghG0L7\n3zLTMSCf1y3yWKhXWnPcN41zWeqiF+gk0zFoIQiaDPjhqNyjzTheXX8YqiTf226E\nxTg1Xrac3LF5Ju+3gCioUzpOo3WbphDmZfDTMBj0cWn7GszLkiNd/AX5bLf/+OdJ\n9KaZSOQcit4A9bxERWFS0vT8aGfN43mUFXrpKLmpltZkmtt4XloEeGndZbHF60hy\n+nRzJVNs9B63xP9+NdpWgvoiRVOBKB04XVcNC6nMCMwYjJRLmBzQQ9PT3dQ2dnpj\nj0TuU/44bj5S5t6aVvEOeKanHHeVqRQm8Kzt4WfDvjp1ASOkApvA5+Xs+DpcKbWH\nMCAZDQpi2vWu8d+c569FvN4e0SbP0qM26NgvAgMBAAGjZjBkMBIGA1UdEwEB/wQI\nMAYBAf8CAQAwDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBSnfq6PGf8AwEL9XGyQ\nM1I6087OzjAfBgNVHSMEGDAWgBSnfq6PGf8AwEL9XGyQM1I6087OzjANBgkqhkiG\n9w0BAQsFAAOCAgEALXZZNaa60cpYNFEXgr780IqKUdZa995OvRUs1dCYd4WqzzJD\nVad8Z48GJX3/u/XAk2UM+mUSGaFowqhek58YX0b24O0PG+y3O0XT0EX/+80Fu+Kt\nkPSbiaPyeYxGqEjwed/Y9X5AJig68NA/FRcT5dq2sWA8hcej8Ghm6D3gu9PdBWpk\nRstITsdaSfx6N+avJ0keGMHqLDLSr948XbehRHH9FnvkPfDtkwKzNwhYmeB6/c+v\nal/JLfPy6VWi3fK37XmuhSh2aZ/vsjT7sxvfFTndUVBeumvCS4wW+bByxpC5XBHW\nB1TrPCczqaDqDD/ib1YCLfY6Qgi8IINEsDDkDgpevW2JxSjTywGGYea4J3M5oOdg\nNhjNWt00H/rugEzkB9hP4po9QHSFX5qWgzT/ws01mOcaOr4UQ8msSyVZmfpJkdHy\nx4n4jhvdlsQKhKM7OmpuXGIA7r/lqU5WDQl1Erj/6cNeWp4vx+606mvbjpzk2Lcp\ni0wBnz27jvN4Xvw+zBMzMBMm5iPwKDMKUyo3q87DFC6lBvBwF0kbPom+yLhHH/rF\n0hr21PATUrHHutFebZ3ZqZwusiKKOoD6fpQrF2mwnVGHQPwTUamSFKQZsf9jw3ic\n4zY2nruXc0OSWS2gf1FKRDxpgpMUjthA3nO1YJuiP4I7fB5mqSoYY8bsyhc=\n-----END CERTIFICATE-----\n"  --cert_content "-----BEGIN CERTIFICATE-----\nMIIFHDCCAwSgAwIBAgIIcePfAqBgEAAwDQYJKoZIhvcNAQELBQAwVzEYMBYGA1UE\nCgwPUHJvdGVncml0eSBJbmMuMQswCQYDVQQGEwJVUzEuMCwGA1UEAwwlUHJvdGVn\ncml0eSBSb290IENBIC0gWkldeedKRE5tekdPdGEyQzAgGA8yMDI1MTIyMTAwMDAw\nMFoXDTM1MTIyMDA3NDE1MlowQzEYMBYGA1UECgwPUHJvdGVncml0eSBJbmMuMQsw\nCQYDVQQGEwJVUzEaMBgGA1UEAwwRUHJvdGVncml0eSBDbGllbnQwggIiMA0GCSqG\nSIb3DQEBAQUAA4ICDwAwggIKAoICAQCn7/6ZMkJkt1/9iOj+0S8aE64w69iSpEUH\ns/wlCJG5mx7QhMKwTeJSjXO+oVSDH7Kr+eoIpTh4Zt6aC9oUaynJ4tLpE1/xb5V9\n2Brafthx6b49/kgeCEvDQtFbmwJPOZ9f2W71oK8s6zgM/dASpH4LgAu3Y7vfJ9eH\nZB63MuDFc429WyDuXQ4xnQ07RUKd40Q7JSKt4WNIdl7IVlAdAwTg+/4+xhYohSgi\ndi82XJRD0MCs0EQg6K5G0Do8DcAmdBsE3LTjJr55G1Juscv6qfh0BCTuyhJpS3dI\nQa5YiSuTIDiO45h8V4BS/+AB42tYSejvQKVmCbaCb9aqwn9LjrM0G4GYU0llvVi0\nvi8d76s9wb1V0Au0lkr/xFMCXebYWGr1I48kKlFKf0l11fP0rjAQO+qWwNJI1ax8\n7g1dh49NwBJbnZJvlv1Hb5KlrOvwHfr8UkFBZ1GVBZum0wbwFirZXxuU43AZp2S\nnwVDl+i3fP4FEu8SMIijhU3NQeA8PbVcyx3xgsOiNO3wXp2Rt380D4Ynw5A7pF6Y\nUD4TefMzUCgDFEykuUzZlnT9mBR34F4bYUQSLPPqWDXedAHfuUh9na2ws3BltpAV\nvpNM9xWl2NQN6Xsp+gAuMwIHcj0FTiJ38UFyzvPCJ/e+FsW3qWQkgDNhUYlOAplf\np8o/+1Fm7wIDAQABMA0GCSqGSIb3DQEBCwUAA4ICAQB+s91FIrthptvdBygBsen4\nLaQpfAGIEyeiG1VdTeXtlev2HjPk0p3FnbjZVQhyT00SCWPHa7Vd6ypIqlIFYvnq\nUvUc0fkUqnpAeRWK9p1bif32Qs3rS6Q8mDDVbe2BP/gxOdrPkKPZLZ/rA4cYQAh0\nx/RsdxXtiBkOQpNjZO+UUbyPqohRKek/yLEiltsdBcXeFzcUbZMxks8CAmKVB3Pn\n69NmqZOcJtcj0ydBKL1MdUxPSHXks0z8afVa5IlbJaeaa+Ef0dMDzL/JdH7FslaZ\ntHvgJpq2RinHx1emIlmAk1ji0L/4MCqRrCdNU1rVIob7amyd6gkAkEIYUlsHFEp1\nBdVU8hh4F9UQ6dQvZ6etO4/Pus8t4DjdY8Xllsgot4NXL94r/asG+z3QjIIokUfu\nEDRorE82P809hWhRVbZ1A66/3XERD4BGmn3PML94YdC+vOxricqkrZ4oJDD3gbow\nfJWQIZ96hMndAG0H055qvgoWNqjifw9KXLHqelHWOiyJftJrchCOwZ3gRlA8WaOy\nHvCNN1VzCOfaNw9YJlJ4c3DLzwwRxo/KinycCvDaYGhBLTkWjZFqqkdwm4cqK9cf\n3joxQKh51a5ENZ2hoJUEvlcfjerQGPMRMUR4n3GwPf7Vca3fd+S1+qA7tcldEKx9\nHte3R2N5rYd/obrdkh5J0A==\n-----END CERTIFICATE-----\n" --key_content "-----BEGIN PRIVATE KEY-----\nMIIJQgIBADANBgkqhkiG9w0BAQEFAASCCSwwggkoAgEAAoICAQCn7/6ZMkJkt1/9\niOj+0S8aE64w69iSpEUHs/wlCJG5mx7QhMKwTeJSjXO+oVSDH7Kr+eoIpTh4Zt6a\nC9oUaynJ4tLpE1/xb5V92Brafthx6b49/kgeCEvDQtFbmwJPOZ9f2W71oK8s6zgM\n/dASpH4LgAu3Y7vfJ9eHZB63MuDFc429WyDuXQ4xnQ07RUKd40Q7JSKt4WNIdl7I\nVlAdAwTg+/4+xhYohSgidi82XJRD0MCs0EQg6K5G0Do8DcAmdBsE3LTjJr55G1Ju\nscv6qfh0BCTuyhJpS3dIQa5YiSuTIDiO45h8V4BS/+AB42tYSejvQKVmCbaCb9aq\nwn9LjrM0G4GYU0llvVi0vi8d76s9wb1V0Au0lkr/xFMCXebYWGr1I48kKlFKf0l1\n1fP0rjAQO+qWwNJI1ax87g1dh49NwBJbnZJvlv1Hb5Kls2rvwHVcp4UkFBZ1GVBZu\nm0wbwFirZXxuU43AZp2SnwVDl+i3fP4FEu8SMIijhU3NQeA8PbVcyx3xgsOiNO3w\nXp2Rt380D4Ynw5A7pF6YUD4TefMzUCgDFEykuUzZlnT9mBR34F4bYUQSLPPqWDXe\ndAHfuUh9na2ws3BltpAVvpNM9xWl2NQN6Xsp+gAuMwIHcj0FTiJ38UFyzvPCJ/e+\nFsW3qWQkgDNhUYlOAplfp8o/+1Fm7wIDAQABAoICAQCbaiSpzbNX1cRFs7A8MYZv\nkYsAxyJ0AwXHLS/Jbfa+V+naeyJZWpp6X2GgJ1k4x9roAK4vNgfelQSodxNpFgtk\nRD9/Z2jA3Mzx205uqjjQospmQK6o7HCA0ZNCPV+TxfXSFDz1n7C91yjWDQXEWuoy\n5lrxaqDw0cRKDcPHMpSE5n1jobQGI6QBEiCum1gdGbeJLMK9O/pPkwwARrB5SNP5\nCfuuSE81TJVp3wmuO1sSr1vAEjUaZ3rxGb7q2Kbcb1KZ206jcLWRClHtEyl8XlQJ\nudQcEHGddDN9cRtR4A+tZoIw6juxxqCBLz81QCuVV0D0OVVX6uE2MR3uhXSawwgEU\nVWIcWvgXkTgEbg/KgrZ3R9VN7XjawMLVv+3dLQp4idD7keoKWCOHXZtdEXalCmLV\nQQxNtwHkjF0yG+mu6nFEiy89onvTLJtzwriu16BYf8kVnUyd3F94LYQZDWRxCuuG\nNppl0VfikZGM+0P0PpKGy3Yn+qR6d4NhaYFxbrgezRg0KlshWpM/N6ZISBj9QjsZ\nPID4oVDNiTk0nEiHlz4SYqsGrTmPdEIwLTO0QL2SFrcNwqh+qT50s7QFqu+Mwl8E\nieRXdEc5mV0qTQvUWPjNh0l6oEwsKi0dxUL5j4utr3WQgk1Fq/1LNgVFL/rBbAIX\ncI3hmU3UQBiTUtzJ3iDytQKCAQEA3LpDbn7TAwr7DMwA1nBTrv5bwGKN7SGan6fN\nL9BI0uyW3H9EZtlhE2kxapF20//gMlvIYO1kW+vySvXTK6IrBzb9s8dzycqbhpyP\n1Z7HQHJeRjNuExTHlX8hU2kW/evmWeRswJwSo37zf6XWMBN4D/i78OEbNDpTLFDA\n2iYWGx2+Cex7nzsSI1omOhek4UyejKsk4Iv2621ezH2mTsHfyxajP/GsCUIHDB6r\nB2nL8YzY/u4nzOVXu5N+sSthQTn3L4KiFavlOd00cCL22J7Dk15CyXn11MHxdo1p\npXZD/sEJfgmiWvroFlHBDRQRzHhPO7j0SzrssOkysNq/aW1eGQKCAQEAwsYkdUWt\nx0fRSaKyC4IJhsKiFcceZdbmHXPd1iaK+oAGhTzz3xDBDlQYbwy6ej8uk8/3PqBW\nfZPOWD9DszTE7k/Rsd4jwVFMD2daE09JVGyPZ7bq4X3qQ7oL120b6Oi1ZuYIXMPs\nlJzgQbOyPzUZess1OUSNwfB8pZhMkjvgmkkSUlZgyQx5+PRW9cZsf4POO9vCAFRL\nOyNlPMAqT1vvGbtatnHc6iY0v1Gl5J0NJfrzpd6b/Cr619NflpSUw6nEd0PLaGl7\naTqCPdMb5Fh7iISmysfSgVavZo5nIvRNY8vVQX8MBaQdmTKXXfYFbiYgZ+uL4hWg\nlTYXdQGQlIx+RwKCAQAjCKVfSl3vo7SJKXAQmS+PHOwvMvVX5/eE07trlWGZqNeh\nE8olkOcpj466XXBA4eIR3COHzuYY+PAyGaZ0zH6L3JyUBlpIcxIQYZUq0NLLVdvE\nxLD58lhjUBRYCtwNXX3oUqs4Pw1uSd4YKpg+dTifQFmEOBZ7Sa6d4AtcFKN5llTt\nek18zoFofwyGN+6BnAmmRhvKUCzW3TsoteDJq1f8AhHTOmaV6Zb4w31d5drq8fIX\nNHG4wcYVDaoUMNB06+Bh+BgF3Iy7jHKgQcxwQXLFVza+h88O/+F1caiNDKJqMvVw\nvdK5Ig3oTP2ZN9BDZe0di5OqxSWARuM20uGCuEsxAoIBABMLXLU6wushUo1ooxAM\n/vF2RnLqrUY35PgsRByUWDJ2Ii0U8KN29+l2v4zcKb+aPeumAf7Vnp9YvGxUg0Ia\nfsbudwp1NfnJAS7gZCZPMlRW6Q6zC/RQY3+LyWye9oOnfVU6WMb5QUCmtia2c09K\n2drv05xt345+/TET2yjRQfzT+D6kw4Hk/mghO/98D0/Ii3m+2xE9LL3zkAqIn5py\n2sYhU5VTPM6IPdAXI6le0dJM31Xwlj/p0+0Wddo7XPBkwRkIP/NNnQuE9QcmhSum\nmy2WCtj5ANQ0raHRerQoPwjq/UcSLRLAIUTBdZtyWsWSZMjEd0D77F+qklCWfpSH\nyDECggEAEaCankeqpmPcSBDdvHZ9TP42aYqvvgrb36bK8A4HdGujx2dWafPcLojm\nizEtUPv2nVU2sGjGmPct5gSCS0oSwjVoIj7UKjT1dLN2QA115mFuZXNsz7UEifdU\n6XuIHztTcDTmhsDGx/XtsnZFyfEl9z3zZIkO4aJ9lbBiyw5LamGD1ykQ2DavxCFE\neFalDX9PGS/VERX9foHLLXDyEXYuoo8pf3ltupYmqbxMSX5Hf1NvtqYBSTvYiaCv\nmQJ3EuuxjzxXcCuI0YWPcAxlAViz9NAzgk+gxbOB6kEHvq/GWWRebQdvGdSHE9zV\ng5HfdOn7snl93cZxCP+JcOFG55h0Dg==\n-----END PRIVATE KEY-----\n"
insight update syslog --host <syslog_address> --port <syslog_port> --ca_content "<ca.crt_content>"  --cert_content "<client.crt_content>" --key_content "<client.key_content>" --troubleshooting_log True

Example:

insight update syslog --host 192.168.1.110 --port 6514 --ca_content "-----BEGIN CERTIFICATE-----\nMIIFmDCCA4CgAwIBAgIIWF8OX+P4jAAwDQYJKoZIhvcNAQELBQAwVzEYMBYGA1UE\nCgwPUHJvdGVncml0eSBJbmMuMQswCQYDVQQGEwJVUzEuMCwGA1UEAwwlUHJvdGVn\ncml0eSBSb290IENBIC0gWklTbkdKRE5tekdPdGEyQzAgGA8yMDI1MTIyMTAwMDAw\nMFoXDTM1MTIyMDA3NDE1MFowVzEYMBYGA1UECgwPUHJvdGVncml0eSBJbmMuMQsw\nCQYDVQQGEwJVUzEuMCwGA1UEAwwlUHJvdGVncml0eSBSb290IENBIC0gWklTbkdK\nRE5tekdPdGEyQzCCAiIwDQYJKoZIhvcNAQEBBQADggIPADCCAgoCggIBAL6nK47Y\n/hs1nBnHxg2/S6ieL/JH9H6M9321qHaSIbqAS2KBy2iNDoy3EhKvHXOgd4TgWc7+\nMGiREDK9QsOZ1UKFn5p5cXt0lkGsRSVB5sh2GurGxCtKEwtXlK8OGAWhz46dmjEr\nT02SH7H6WQA+Zh8+OTdzjpo/aujdI6pGVslSY/ulFcqQF16U7aRTmobPpdSZuFWN\nuBcoAXLhDBLutCWQaYSodksRha6I6olrlSditoHHGOnMWC6S4/+NT1XtSvBEIhVn\nMDRym6UKLNlhR+bb3lyGK5HgA2frXduNIL244z931Ii+JAnvpIsZrQ9k1UghG0L7\n3zLTMSCf1y3yWKhXWnPcN41zWeqiF+gk0zFoIQiaDPjhqNyjzTheXX8YqiTf226E\nxTg1Xrac3LF5Ju+3gCioUzpOo3WbphDmZfDTMBj0cWn7GszLkiNd/AX5bLf/+OdJ\n9KaZSOQcit4A9bxERWFS0vT8aGfN43mUFXrpKLmpltZkmtt4XloEeGndZbHF60hy\n+nRzJVNs9B63xP9+NdpWgvoiRVOBKB04XVcNC6nMCMwYjJRLmBzQQ9PT3dQ2dnpj\nj0TuU/44bj5S5t6aVvEOeKanHHeVqRQm8Kzt4WfDvjp1ASOkApvA5+Xs+DpcKbWH\nMCAZDQpi2vWu8d+c569FvN4e0SbP0qM26NgvAgMBAAGjZjBkMBIGA1UdEwEB/wQI\nMAYBAf8CAQAwDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBSnfq6PGf8AwEL9XGyQ\nM1I6087OzjAfBgNVHSMEGDAWgBSnfq6PGf8AwEL9XGyQM1I6087OzjANBgkqhkiG\n9w0BAQsFAAOCAgEALXZZNaa60cpYNFEXgr780IqKUdZa995OvRUs1dCYd4WqzzJD\nVad8Z48GJX3/u/XAk2UM+mUSGaFowqhek58YX0b24O0PG+y3O0XT0EX/+80Fu+Kt\nkPSbiaPyeYxGqEjwed/Y9X5AJig68NA/FRcT5dq2sWA8hcej8Ghm6D3gu9PdBWpk\nRstITsdaSfx6N+avJ0keGMHqLDLSr948XbehRHH9FnvkPfDtkwKzNwhYmeB6/c+v\nal/JLfPy6VWi3fK37XmuhSh2aZ/vsjT7sxvfFTndUVBeumvCS4wW+bByxpC5XBHW\nB1TrPCczqaDqDD/ib1YCLfY6Qgi8IINEsDDkDgpevW2JxSjTywGGYea4J3M5oOdg\nNhjNWt00H/rugEzkB9hP4po9QHSFX5qWgzT/ws01mOcaOr4UQ8msSyVZmfpJkdHy\nx4n4jhvdlsQKhKM7OmpuXGIA7r/lqU5WDQl1Erj/6cNeWp4vx+606mvbjpzk2Lcp\ni0wBnz27jvN4Xvw+zBMzMBMm5iPwKDMKUyo3q87DFC6lBvBwF0kbPom+yLhHH/rF\n0hr21PATUrHHutFebZ3ZqZwusiKKOoD6fpQrF2mwnVGHQPwTUamSFKQZsf9jw3ic\n4zY2nruXc0OSWS2gf1FKRDxpgpMUjthA3nO1YJuiP4I7fB5mqSoYY8bsyhc=\n-----END CERTIFICATE-----\n"  --cert_content "-----BEGIN CERTIFICATE-----\nMIIFHDCCAwSgAwIBAgIIcePfAqBgEAAwDQYJKoZIhvcNAQELBQAwVzEYMBYGA1UE\nCgwPUHJvdGVncml0eSBJbmMuMQswCQYDVQQGEwJVUzEuMCwGA1UEAwwlUHJvdGVn\ncml0eSBSb290IENBIC0gWkldeedKRE5tekdPdGEyQzAgGA8yMDI1MTIyMTAwMDAw\nMFoXDTM1MTIyMDA3NDE1MlowQzEYMBYGA1UECgwPUHJvdGVncml0eSBJbmMuMQsw\nCQYDVQQGEwJVUzEaMBgGA1UEAwwRUHJvdGVncml0eSBDbGllbnQwggIiMA0GCSqG\nSIb3DQEBAQUAA4ICDwAwggIKAoICAQCn7/6ZMkJkt1/9iOj+0S8aE64w69iSpEUH\ns/wlCJG5mx7QhMKwTeJSjXO+oVSDH7Kr+eoIpTh4Zt6aC9oUaynJ4tLpE1/xb5V9\n2Brafthx6b49/kgeCEvDQtFbmwJPOZ9f2W71oK8s6zgM/dASpH4LgAu3Y7vfJ9eH\nZB63MuDFc429WyDuXQ4xnQ07RUKd40Q7JSKt4WNIdl7IVlAdAwTg+/4+xhYohSgi\ndi82XJRD0MCs0EQg6K5G0Do8DcAmdBsE3LTjJr55G1Juscv6qfh0BCTuyhJpS3dI\nQa5YiSuTIDiO45h8V4BS/+AB42tYSejvQKVmCbaCb9aqwn9LjrM0G4GYU0llvVi0\nvi8d76s9wb1V0Au0lkr/xFMCXebYWGr1I48kKlFKf0l11fP0rjAQO+qWwNJI1ax8\n7g1dh49NwBJbnZJvlv1Hb5KlrOvwHfr8UkFBZ1GVBZum0wbwFirZXxuU43AZp2S\nnwVDl+i3fP4FEu8SMIijhU3NQeA8PbVcyx3xgsOiNO3wXp2Rt380D4Ynw5A7pF6Y\nUD4TefMzUCgDFEykuUzZlnT9mBR34F4bYUQSLPPqWDXedAHfuUh9na2ws3BltpAV\nvpNM9xWl2NQN6Xsp+gAuMwIHcj0FTiJ38UFyzvPCJ/e+FsW3qWQkgDNhUYlOAplf\np8o/+1Fm7wIDAQABMA0GCSqGSIb3DQEBCwUAA4ICAQB+s91FIrthptvdBygBsen4\nLaQpfAGIEyeiG1VdTeXtlev2HjPk0p3FnbjZVQhyT00SCWPHa7Vd6ypIqlIFYvnq\nUvUc0fkUqnpAeRWK9p1bif32Qs3rS6Q8mDDVbe2BP/gxOdrPkKPZLZ/rA4cYQAh0\nx/RsdxXtiBkOQpNjZO+UUbyPqohRKek/yLEiltsdBcXeFzcUbZMxks8CAmKVB3Pn\n69NmqZOcJtcj0ydBKL1MdUxPSHXks0z8afVa5IlbJaeaa+Ef0dMDzL/JdH7FslaZ\ntHvgJpq2RinHx1emIlmAk1ji0L/4MCqRrCdNU1rVIob7amyd6gkAkEIYUlsHFEp1\nBdVU8hh4F9UQ6dQvZ6etO4/Pus8t4DjdY8Xllsgot4NXL94r/asG+z3QjIIokUfu\nEDRorE82P809hWhRVbZ1A66/3XERD4BGmn3PML94YdC+vOxricqkrZ4oJDD3gbow\nfJWQIZ96hMndAG0H055qvgoWNqjifw9KXLHqelHWOiyJftJrchCOwZ3gRlA8WaOy\nHvCNN1VzCOfaNw9YJlJ4c3DLzwwRxo/KinycCvDaYGhBLTkWjZFqqkdwm4cqK9cf\n3joxQKh51a5ENZ2hoJUEvlcfjerQGPMRMUR4n3GwPf7Vca3fd+S1+qA7tcldEKx9\nHte3R2N5rYd/obrdkh5J0A==\n-----END CERTIFICATE-----\n" --key_content "-----BEGIN PRIVATE KEY-----\nMIIJQgIBADANBgkqhkiG9w0BAQEFAASCCSwwggkoAgEAAoICAQCn7/6ZMkJkt1/9\niOj+0S8aE64w69iSpEUHs/wlCJG5mx7QhMKwTeJSjXO+oVSDH7Kr+eoIpTh4Zt6a\nC9oUaynJ4tLpE1/xb5V92Brafthx6b49/kgeCEvDQtFbmwJPOZ9f2W71oK8s6zgM\n/dASpH4LgAu3Y7vfJ9eHZB63MuDFc429WyDuXQ4xnQ07RUKd40Q7JSKt4WNIdl7I\nVlAdAwTg+/4+xhYohSgidi82XJRD0MCs0EQg6K5G0Do8DcAmdBsE3LTjJr55G1Ju\nscv6qfh0BCTuyhJpS3dIQa5YiSuTIDiO45h8V4BS/+AB42tYSejvQKVmCbaCb9aq\nwn9LjrM0G4GYU0llvVi0vi8d76s9wb1V0Au0lkr/xFMCXebYWGr1I48kKlFKf0l1\n1fP0rjAQO+qWwNJI1ax87g1dh49NwBJbnZJvlv1Hb5Kls2rvwHVcp4UkFBZ1GVBZu\nm0wbwFirZXxuU43AZp2SnwVDl+i3fP4FEu8SMIijhU3NQeA8PbVcyx3xgsOiNO3w\nXp2Rt380D4Ynw5A7pF6YUD4TefMzUCgDFEykuUzZlnT9mBR34F4bYUQSLPPqWDXe\ndAHfuUh9na2ws3BltpAVvpNM9xWl2NQN6Xsp+gAuMwIHcj0FTiJ38UFyzvPCJ/e+\nFsW3qWQkgDNhUYlOAplfp8o/+1Fm7wIDAQABAoICAQCbaiSpzbNX1cRFs7A8MYZv\nkYsAxyJ0AwXHLS/Jbfa+V+naeyJZWpp6X2GgJ1k4x9roAK4vNgfelQSodxNpFgtk\nRD9/Z2jA3Mzx205uqjjQospmQK6o7HCA0ZNCPV+TxfXSFDz1n7C91yjWDQXEWuoy\n5lrxaqDw0cRKDcPHMpSE5n1jobQGI6QBEiCum1gdGbeJLMK9O/pPkwwARrB5SNP5\nCfuuSE81TJVp3wmuO1sSr1vAEjUaZ3rxGb7q2Kbcb1KZ206jcLWRClHtEyl8XlQJ\nudQcEHGddDN9cRtR4A+tZoIw6juxxqCBLz81QCuVV0D0OVVX6uE2MR3uhXSawwgEU\nVWIcWvgXkTgEbg/KgrZ3R9VN7XjawMLVv+3dLQp4idD7keoKWCOHXZtdEXalCmLV\nQQxNtwHkjF0yG+mu6nFEiy89onvTLJtzwriu16BYf8kVnUyd3F94LYQZDWRxCuuG\nNppl0VfikZGM+0P0PpKGy3Yn+qR6d4NhaYFxbrgezRg0KlshWpM/N6ZISBj9QjsZ\nPID4oVDNiTk0nEiHlz4SYqsGrTmPdEIwLTO0QL2SFrcNwqh+qT50s7QFqu+Mwl8E\nieRXdEc5mV0qTQvUWPjNh0l6oEwsKi0dxUL5j4utr3WQgk1Fq/1LNgVFL/rBbAIX\ncI3hmU3UQBiTUtzJ3iDytQKCAQEA3LpDbn7TAwr7DMwA1nBTrv5bwGKN7SGan6fN\nL9BI0uyW3H9EZtlhE2kxapF20//gMlvIYO1kW+vySvXTK6IrBzb9s8dzycqbhpyP\n1Z7HQHJeRjNuExTHlX8hU2kW/evmWeRswJwSo37zf6XWMBN4D/i78OEbNDpTLFDA\n2iYWGx2+Cex7nzsSI1omOhek4UyejKsk4Iv2621ezH2mTsHfyxajP/GsCUIHDB6r\nB2nL8YzY/u4nzOVXu5N+sSthQTn3L4KiFavlOd00cCL22J7Dk15CyXn11MHxdo1p\npXZD/sEJfgmiWvroFlHBDRQRzHhPO7j0SzrssOkysNq/aW1eGQKCAQEAwsYkdUWt\nx0fRSaKyC4IJhsKiFcceZdbmHXPd1iaK+oAGhTzz3xDBDlQYbwy6ej8uk8/3PqBW\nfZPOWD9DszTE7k/Rsd4jwVFMD2daE09JVGyPZ7bq4X3qQ7oL120b6Oi1ZuYIXMPs\nlJzgQbOyPzUZess1OUSNwfB8pZhMkjvgmkkSUlZgyQx5+PRW9cZsf4POO9vCAFRL\nOyNlPMAqT1vvGbtatnHc6iY0v1Gl5J0NJfrzpd6b/Cr619NflpSUw6nEd0PLaGl7\naTqCPdMb5Fh7iISmysfSgVavZo5nIvRNY8vVQX8MBaQdmTKXXfYFbiYgZ+uL4hWg\nlTYXdQGQlIx+RwKCAQAjCKVfSl3vo7SJKXAQmS+PHOwvMvVX5/eE07trlWGZqNeh\nE8olkOcpj466XXBA4eIR3COHzuYY+PAyGaZ0zH6L3JyUBlpIcxIQYZUq0NLLVdvE\nxLD58lhjUBRYCtwNXX3oUqs4Pw1uSd4YKpg+dTifQFmEOBZ7Sa6d4AtcFKN5llTt\nek18zoFofwyGN+6BnAmmRhvKUCzW3TsoteDJq1f8AhHTOmaV6Zb4w31d5drq8fIX\nNHG4wcYVDaoUMNB06+Bh+BgF3Iy7jHKgQcxwQXLFVza+h88O/+F1caiNDKJqMvVw\nvdK5Ig3oTP2ZN9BDZe0di5OqxSWARuM20uGCuEsxAoIBABMLXLU6wushUo1ooxAM\n/vF2RnLqrUY35PgsRByUWDJ2Ii0U8KN29+l2v4zcKb+aPeumAf7Vnp9YvGxUg0Ia\nfsbudwp1NfnJAS7gZCZPMlRW6Q6zC/RQY3+LyWye9oOnfVU6WMb5QUCmtia2c09K\n2drv05xt345+/TET2yjRQfzT+D6kw4Hk/mghO/98D0/Ii3m+2xE9LL3zkAqIn5py\n2sYhU5VTPM6IPdAXI6le0dJM31Xwlj/p0+0Wddo7XPBkwRkIP/NNnQuE9QcmhSum\nmy2WCtj5ANQ0raHRerQoPwjq/UcSLRLAIUTBdZtyWsWSZMjEd0D77F+qklCWfpSH\nyDECggEAEaCankeqpmPcSBDdvHZ9TP42aYqvvgrb36bK8A4HdGujx2dWafPcLojm\nizEtUPv2nVU2sGjGmPct5gSCS0oSwjVoIj7UKjT1dLN2QA115mFuZXNsz7UEifdU\n6XuIHztTcDTmhsDGx/XtsnZFyfEl9z3zZIkO4aJ9lbBiyw5LamGD1ykQ2DavxCFE\neFalDX9PGS/VERX9foHLLXDyEXYuoo8pf3ltupYmqbxMSX5Hf1NvtqYBSTvYiaCv\nmQJ3EuuxjzxXcCuI0YWPcAxlAViz9NAzgk+gxbOB6kEHvq/GWWRebQdvGdSHE9zV\ng5HfdOn7snl93cZxCP+JcOFG55h0Dg==\n-----END PRIVATE KEY-----\n" --troubleshooting_log True

The pods take some time to initialize and stabilize after running this command. Verify the status of the pods using the kubectl get pods -n pty-insightcommand. Avoid updating any more configurations till the pods are ready.

Removing the log forwarding settings

The command stops external SIEM log forwarding, removes the associated configuration, and deletes the certificate-related secrets.

insight delete syslog 

The pods take some time to initialize and stabilize after running this command. Verify the status of the pods using the kubectl get pods -n pty-insightcommand. Avoid updating any more configurations till the pods are ready.

fluentd commands

The commands provided here are used for sending logs to the Audit Store, retaining the default storage location, and an external fluentd SIEM.

Viewing the current configuration

The command to view the log forwarding configurations.

insight list fluentd

Verifying connectivity

The command to verify that the external fluentd SIEM is accessible.

insight test fluentd --host <fluentd_address> --port <fluentd_port>

Example:

insight test fluentd --host 192.168.1.100 --port 24284

Forwarding logs to the fluentd server

The command to forward logs to the fluentd server.

insight configure fluentd --host <fluentd_address> --port <fluentd_port> --ca_content "<ca.crt_content>"  --cert_content "<client.crt_content>" --key_content "<client.key_content>"

Example:

insight configure fluentd --host 192.168.1.110 --port 24284 --ca_content "-----BEGIN CERTIFICATE-----\nMIIFmDCCA4CgAwIBAgIIWF8OX+P4jAAwDQYJKoZIhvcNAQELBQAwVzEYMBYGA1UE\nCgwPUHJvdGVncml0eSBJbmMuMQswCQYDVQQGEwJVUzEuMCwGA1UEAwwlUHJvdGVn\ncml0eSBSb290IENBIC0gWklTbkdKRE5tekdPdGEyQzAgGA8yMDI1MTIyMTAwMDAw\nMFoXDTM1MTIyMDA3NDE1MFowVzEYMBYGA1UECgwPUHJvdGVncml0eSBJbmMuMQsw\nCQYDVQQGEwJVUzEuMCwGA1UEAwwlUHJvdGVncml0eSBSb290IENBIC0gWklTbkdK\nRE5tekdPdGEyQzCCAiIwDQYJKoZIhvcNAQEBBQADggIPADCCAgoCggIBAL6nK47Y\n/hs1nBnHxg2/S6ieL/JH9H6M9321qHaSIbqAS2KBy2iNDoy3EhKvHXOgd4TgWc7+\nMGiREDK9QsOZ1UKFn5p5cXt0lkGsRSVB5sh2GurGxCtKEwtXlK8OGAWhz46dmjEr\nT02SH7H6WQA+Zh8+OTdzjpo/aujdI6pGVslSY/ulFcqQF16U7aRTmobPpdSZuFWN\nuBcoAXLhDBLutCWQaYSodksRha6I6olrlSditoHHGOnMWC6S4/+NT1XtSvBEIhVn\nMDRym6UKLNlhR+bb3lyGK5HgA2frXduNIL244z931Ii+JAnvpIsZrQ9k1UghG0L7\n3zLTMSCf1y3yWKhXWnPcN41zWeqiF+gk0zFoIQiaDPjhqNyjzTheXX8YqiTf226E\nxTg1Xrac3LF5Ju+3gCioUzpOo3WbphDmZfDTMBj0cWn7GszLkiNd/AX5bLf/+OdJ\n9KaZSOQcit4A9bxERWFS0vT8aGfN43mUFXrpKLmpltZkmtt4XloEeGndZbHF60hy\n+nRzJVNs9B63xP9+NdpWgvoiRVOBKB04XVcNC6nMCMwYjJRLmBzQQ9PT3dQ2dnpj\nj0TuU/44bj5S5t6aVvEOeKanHHeVqRQm8Kzt4WfDvjp1ASOkApvA5+Xs+DpcKbWH\nMCAZDQpi2vWu8d+c569FvN4e0SbP0qM26NgvAgMBAAGjZjBkMBIGA1UdEwEB/wQI\nMAYBAf8CAQAwDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBSnfq6PGf8AwEL9XGyQ\nM1I6087OzjAfBgNVHSMEGDAWgBSnfq6PGf8AwEL9XGyQM1I6087OzjANBgkqhkiG\n9w0BAQsFAAOCAgEALXZZNaa60cpYNFEXgr780IqKUdZa995OvRUs1dCYd4WqzzJD\nVad8Z48GJX3/u/XAk2UM+mUSGaFowqhek58YX0b24O0PG+y3O0XT0EX/+80Fu+Kt\nkPSbiaPyeYxGqEjwed/Y9X5AJig68NA/FRcT5dq2sWA8hcej8Ghm6D3gu9PdBWpk\nRstITsdaSfx6N+avJ0keGMHqLDLSr948XbehRHH9FnvkPfDtkwKzNwhYmeB6/c+v\nal/JLfPy6VWi3fK37XmuhSh2aZ/vsjT7sxvfFTndUVBeumvCS4wW+bByxpC5XBHW\nB1TrPCczqaDqDD/ib1YCLfY6Qgi8IINEsDDkDgpevW2JxSjTywGGYea4J3M5oOdg\nNhjNWt00H/rugEzkB9hP4po9QHSFX5qWgzT/ws01mOcaOr4UQ8msSyVZmfpJkdHy\nx4n4jhvdlsQKhKM7OmpuXGIA7r/lqU5WDQl1Erj/6cNeWp4vx+606mvbjpzk2Lcp\ni0wBnz27jvN4Xvw+zBMzMBMm5iPwKDMKUyo3q87DFC6lBvBwF0kbPom+yLhHH/rF\n0hr21PATUrHHutFebZ3ZqZwusiKKOoD6fpQrF2mwnVGHQPwTUamSFKQZsf9jw3ic\n4zY2nruXc0OSWS2gf1FKRDxpgpMUjthA3nO1YJuiP4I7fB5mqSoYY8bsyhc=\n-----END CERTIFICATE-----\n"  --cert_content "-----BEGIN CERTIFICATE-----\nMIIFHDCCAwSgAwIBAgIIcePfAqBgEAAwDQYJKoZIhvcNAQELBQAwVzEYMBYGA1UE\nCgwPUHJvdGVncml0eSBJbmMuMQswCQYDVQQGEwJVUzEuMCwGA1UEAwwlUHJvdGVn\ncml0eSBSb290IENBIC0gWkldeedKRE5tekdPdGEyQzAgGA8yMDI1MTIyMTAwMDAw\nMFoXDTM1MTIyMDA3NDE1MlowQzEYMBYGA1UECgwPUHJvdGVncml0eSBJbmMuMQsw\nCQYDVQQGEwJVUzEaMBgGA1UEAwwRUHJvdGVncml0eSBDbGllbnQwggIiMA0GCSqG\nSIb3DQEBAQUAA4ICDwAwggIKAoICAQCn7/6ZMkJkt1/9iOj+0S8aE64w69iSpEUH\ns/wlCJG5mx7QhMKwTeJSjXO+oVSDH7Kr+eoIpTh4Zt6aC9oUaynJ4tLpE1/xb5V9\n2Brafthx6b49/kgeCEvDQtFbmwJPOZ9f2W71oK8s6zgM/dASpH4LgAu3Y7vfJ9eH\nZB63MuDFc429WyDuXQ4xnQ07RUKd40Q7JSKt4WNIdl7IVlAdAwTg+/4+xhYohSgi\ndi82XJRD0MCs0EQg6K5G0Do8DcAmdBsE3LTjJr55G1Juscv6qfh0BCTuyhJpS3dI\nQa5YiSuTIDiO45h8V4BS/+AB42tYSejvQKVmCbaCb9aqwn9LjrM0G4GYU0llvVi0\nvi8d76s9wb1V0Au0lkr/xFMCXebYWGr1I48kKlFKf0l11fP0rjAQO+qWwNJI1ax8\n7g1dh49NwBJbnZJvlv1Hb5KlrOvwHfr8UkFBZ1GVBZum0wbwFirZXxuU43AZp2S\nnwVDl+i3fP4FEu8SMIijhU3NQeA8PbVcyx3xgsOiNO3wXp2Rt380D4Ynw5A7pF6Y\nUD4TefMzUCgDFEykuUzZlnT9mBR34F4bYUQSLPPqWDXedAHfuUh9na2ws3BltpAV\nvpNM9xWl2NQN6Xsp+gAuMwIHcj0FTiJ38UFyzvPCJ/e+FsW3qWQkgDNhUYlOAplf\np8o/+1Fm7wIDAQABMA0GCSqGSIb3DQEBCwUAA4ICAQB+s91FIrthptvdBygBsen4\nLaQpfAGIEyeiG1VdTeXtlev2HjPk0p3FnbjZVQhyT00SCWPHa7Vd6ypIqlIFYvnq\nUvUc0fkUqnpAeRWK9p1bif32Qs3rS6Q8mDDVbe2BP/gxOdrPkKPZLZ/rA4cYQAh0\nx/RsdxXtiBkOQpNjZO+UUbyPqohRKek/yLEiltsdBcXeFzcUbZMxks8CAmKVB3Pn\n69NmqZOcJtcj0ydBKL1MdUxPSHXks0z8afVa5IlbJaeaa+Ef0dMDzL/JdH7FslaZ\ntHvgJpq2RinHx1emIlmAk1ji0L/4MCqRrCdNU1rVIob7amyd6gkAkEIYUlsHFEp1\nBdVU8hh4F9UQ6dQvZ6etO4/Pus8t4DjdY8Xllsgot4NXL94r/asG+z3QjIIokUfu\nEDRorE82P809hWhRVbZ1A66/3XERD4BGmn3PML94YdC+vOxricqkrZ4oJDD3gbow\nfJWQIZ96hMndAG0H055qvgoWNqjifw9KXLHqelHWOiyJftJrchCOwZ3gRlA8WaOy\nHvCNN1VzCOfaNw9YJlJ4c3DLzwwRxo/KinycCvDaYGhBLTkWjZFqqkdwm4cqK9cf\n3joxQKh51a5ENZ2hoJUEvlcfjerQGPMRMUR4n3GwPf7Vca3fd+S1+qA7tcldEKx9\nHte3R2N5rYd/obrdkh5J0A==\n-----END CERTIFICATE-----\n" --key_content "-----BEGIN PRIVATE KEY-----\nMIIJQgIBADANBgkqhkiG9w0BAQEFAASCCSwwggkoAgEAAoICAQCn7/6ZMkJkt1/9\niOj+0S8aE64w69iSpEUHs/wlCJG5mx7QhMKwTeJSjXO+oVSDH7Kr+eoIpTh4Zt6a\nC9oUaynJ4tLpE1/xb5V92Brafthx6b49/kgeCEvDQtFbmwJPOZ9f2W71oK8s6zgM\n/dASpH4LgAu3Y7vfJ9eHZB63MuDFc429WyDuXQ4xnQ07RUKd40Q7JSKt4WNIdl7I\nVlAdAwTg+/4+xhYohSgidi82XJRD0MCs0EQg6K5G0Do8DcAmdBsE3LTjJr55G1Ju\nscv6qfh0BCTuyhJpS3dIQa5YiSuTIDiO45h8V4BS/+AB42tYSejvQKVmCbaCb9aq\nwn9LjrM0G4GYU0llvVi0vi8d76s9wb1V0Au0lkr/xFMCXebYWGr1I48kKlFKf0l1\n1fP0rjAQO+qWwNJI1ax87g1dh49NwBJbnZJvlv1Hb5Kls2rvwHVcp4UkFBZ1GVBZu\nm0wbwFirZXxuU43AZp2SnwVDl+i3fP4FEu8SMIijhU3NQeA8PbVcyx3xgsOiNO3w\nXp2Rt380D4Ynw5A7pF6YUD4TefMzUCgDFEykuUzZlnT9mBR34F4bYUQSLPPqWDXe\ndAHfuUh9na2ws3BltpAVvpNM9xWl2NQN6Xsp+gAuMwIHcj0FTiJ38UFyzvPCJ/e+\nFsW3qWQkgDNhUYlOAplfp8o/+1Fm7wIDAQABAoICAQCbaiSpzbNX1cRFs7A8MYZv\nkYsAxyJ0AwXHLS/Jbfa+V+naeyJZWpp6X2GgJ1k4x9roAK4vNgfelQSodxNpFgtk\nRD9/Z2jA3Mzx205uqjjQospmQK6o7HCA0ZNCPV+TxfXSFDz1n7C91yjWDQXEWuoy\n5lrxaqDw0cRKDcPHMpSE5n1jobQGI6QBEiCum1gdGbeJLMK9O/pPkwwARrB5SNP5\nCfuuSE81TJVp3wmuO1sSr1vAEjUaZ3rxGb7q2Kbcb1KZ206jcLWRClHtEyl8XlQJ\nudQcEHGddDN9cRtR4A+tZoIw6juxxqCBLz81QCuVV0D0OVVX6uE2MR3uhXSawwgEU\nVWIcWvgXkTgEbg/KgrZ3R9VN7XjawMLVv+3dLQp4idD7keoKWCOHXZtdEXalCmLV\nQQxNtwHkjF0yG+mu6nFEiy89onvTLJtzwriu16BYf8kVnUyd3F94LYQZDWRxCuuG\nNppl0VfikZGM+0P0PpKGy3Yn+qR6d4NhaYFxbrgezRg0KlshWpM/N6ZISBj9QjsZ\nPID4oVDNiTk0nEiHlz4SYqsGrTmPdEIwLTO0QL2SFrcNwqh+qT50s7QFqu+Mwl8E\nieRXdEc5mV0qTQvUWPjNh0l6oEwsKi0dxUL5j4utr3WQgk1Fq/1LNgVFL/rBbAIX\ncI3hmU3UQBiTUtzJ3iDytQKCAQEA3LpDbn7TAwr7DMwA1nBTrv5bwGKN7SGan6fN\nL9BI0uyW3H9EZtlhE2kxapF20//gMlvIYO1kW+vySvXTK6IrBzb9s8dzycqbhpyP\n1Z7HQHJeRjNuExTHlX8hU2kW/evmWeRswJwSo37zf6XWMBN4D/i78OEbNDpTLFDA\n2iYWGx2+Cex7nzsSI1omOhek4UyejKsk4Iv2621ezH2mTsHfyxajP/GsCUIHDB6r\nB2nL8YzY/u4nzOVXu5N+sSthQTn3L4KiFavlOd00cCL22J7Dk15CyXn11MHxdo1p\npXZD/sEJfgmiWvroFlHBDRQRzHhPO7j0SzrssOkysNq/aW1eGQKCAQEAwsYkdUWt\nx0fRSaKyC4IJhsKiFcceZdbmHXPd1iaK+oAGhTzz3xDBDlQYbwy6ej8uk8/3PqBW\nfZPOWD9DszTE7k/Rsd4jwVFMD2daE09JVGyPZ7bq4X3qQ7oL120b6Oi1ZuYIXMPs\nlJzgQbOyPzUZess1OUSNwfB8pZhMkjvgmkkSUlZgyQx5+PRW9cZsf4POO9vCAFRL\nOyNlPMAqT1vvGbtatnHc6iY0v1Gl5J0NJfrzpd6b/Cr619NflpSUw6nEd0PLaGl7\naTqCPdMb5Fh7iISmysfSgVavZo5nIvRNY8vVQX8MBaQdmTKXXfYFbiYgZ+uL4hWg\nlTYXdQGQlIx+RwKCAQAjCKVfSl3vo7SJKXAQmS+PHOwvMvVX5/eE07trlWGZqNeh\nE8olkOcpj466XXBA4eIR3COHzuYY+PAyGaZ0zH6L3JyUBlpIcxIQYZUq0NLLVdvE\nxLD58lhjUBRYCtwNXX3oUqs4Pw1uSd4YKpg+dTifQFmEOBZ7Sa6d4AtcFKN5llTt\nek18zoFofwyGN+6BnAmmRhvKUCzW3TsoteDJq1f8AhHTOmaV6Zb4w31d5drq8fIX\nNHG4wcYVDaoUMNB06+Bh+BgF3Iy7jHKgQcxwQXLFVza+h88O/+F1caiNDKJqMvVw\nvdK5Ig3oTP2ZN9BDZe0di5OqxSWARuM20uGCuEsxAoIBABMLXLU6wushUo1ooxAM\n/vF2RnLqrUY35PgsRByUWDJ2Ii0U8KN29+l2v4zcKb+aPeumAf7Vnp9YvGxUg0Ia\nfsbudwp1NfnJAS7gZCZPMlRW6Q6zC/RQY3+LyWye9oOnfVU6WMb5QUCmtia2c09K\n2drv05xt345+/TET2yjRQfzT+D6kw4Hk/mghO/98D0/Ii3m+2xE9LL3zkAqIn5py\n2sYhU5VTPM6IPdAXI6le0dJM31Xwlj/p0+0Wddo7XPBkwRkIP/NNnQuE9QcmhSum\nmy2WCtj5ANQ0raHRerQoPwjq/UcSLRLAIUTBdZtyWsWSZMjEd0D77F+qklCWfpSH\nyDECggEAEaCankeqpmPcSBDdvHZ9TP42aYqvvgrb36bK8A4HdGujx2dWafPcLojm\nizEtUPv2nVU2sGjGmPct5gSCS0oSwjVoIj7UKjT1dLN2QA115mFuZXNsz7UEifdU\n6XuIHztTcDTmhsDGx/XtsnZFyfEl9z3zZIkO4aJ9lbBiyw5LamGD1ykQ2DavxCFE\neFalDX9PGS/VERX9foHLLXDyEXYuoo8pf3ltupYmqbxMSX5Hf1NvtqYBSTvYiaCv\nmQJ3EuuxjzxXcCuI0YWPcAxlAViz9NAzgk+gxbOB6kEHvq/GWWRebQdvGdSHE9zV\ng5HfdOn7snl93cZxCP+JcOFG55h0Dg==\n-----END PRIVATE KEY-----\n"
insight configure fluentd --host <fluentd_IP_address> --port <fluentd_port> --ca_content "<ca.crt_content>"  --cert_content "<client.crt_content>" --key_content "<client.key_content>" --troubleshooting_log True

Example:

insight configure fluentd --host 192.168.1.110 --port 24284 --ca_content "-----BEGIN CERTIFICATE-----\nMIIFmDCCA4CgAwIBAgIIWF8OX+P4jAAwDQYJKoZIhvcNAQELBQAwVzEYMBYGA1UE\nCgwPUHJvdGVncml0eSBJbmMuMQswCQYDVQQGEwJVUzEuMCwGA1UEAwwlUHJvdGVn\ncml0eSBSb290IENBIC0gWklTbkdKRE5tekdPdGEyQzAgGA8yMDI1MTIyMTAwMDAw\nMFoXDTM1MTIyMDA3NDE1MFowVzEYMBYGA1UECgwPUHJvdGVncml0eSBJbmMuMQsw\nCQYDVQQGEwJVUzEuMCwGA1UEAwwlUHJvdGVncml0eSBSb290IENBIC0gWklTbkdK\nRE5tekdPdGEyQzCCAiIwDQYJKoZIhvcNAQEBBQADggIPADCCAgoCggIBAL6nK47Y\n/hs1nBnHxg2/S6ieL/JH9H6M9321qHaSIbqAS2KBy2iNDoy3EhKvHXOgd4TgWc7+\nMGiREDK9QsOZ1UKFn5p5cXt0lkGsRSVB5sh2GurGxCtKEwtXlK8OGAWhz46dmjEr\nT02SH7H6WQA+Zh8+OTdzjpo/aujdI6pGVslSY/ulFcqQF16U7aRTmobPpdSZuFWN\nuBcoAXLhDBLutCWQaYSodksRha6I6olrlSditoHHGOnMWC6S4/+NT1XtSvBEIhVn\nMDRym6UKLNlhR+bb3lyGK5HgA2frXduNIL244z931Ii+JAnvpIsZrQ9k1UghG0L7\n3zLTMSCf1y3yWKhXWnPcN41zWeqiF+gk0zFoIQiaDPjhqNyjzTheXX8YqiTf226E\nxTg1Xrac3LF5Ju+3gCioUzpOo3WbphDmZfDTMBj0cWn7GszLkiNd/AX5bLf/+OdJ\n9KaZSOQcit4A9bxERWFS0vT8aGfN43mUFXrpKLmpltZkmtt4XloEeGndZbHF60hy\n+nRzJVNs9B63xP9+NdpWgvoiRVOBKB04XVcNC6nMCMwYjJRLmBzQQ9PT3dQ2dnpj\nj0TuU/44bj5S5t6aVvEOeKanHHeVqRQm8Kzt4WfDvjp1ASOkApvA5+Xs+DpcKbWH\nMCAZDQpi2vWu8d+c569FvN4e0SbP0qM26NgvAgMBAAGjZjBkMBIGA1UdEwEB/wQI\nMAYBAf8CAQAwDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBSnfq6PGf8AwEL9XGyQ\nM1I6087OzjAfBgNVHSMEGDAWgBSnfq6PGf8AwEL9XGyQM1I6087OzjANBgkqhkiG\n9w0BAQsFAAOCAgEALXZZNaa60cpYNFEXgr780IqKUdZa995OvRUs1dCYd4WqzzJD\nVad8Z48GJX3/u/XAk2UM+mUSGaFowqhek58YX0b24O0PG+y3O0XT0EX/+80Fu+Kt\nkPSbiaPyeYxGqEjwed/Y9X5AJig68NA/FRcT5dq2sWA8hcej8Ghm6D3gu9PdBWpk\nRstITsdaSfx6N+avJ0keGMHqLDLSr948XbehRHH9FnvkPfDtkwKzNwhYmeB6/c+v\nal/JLfPy6VWi3fK37XmuhSh2aZ/vsjT7sxvfFTndUVBeumvCS4wW+bByxpC5XBHW\nB1TrPCczqaDqDD/ib1YCLfY6Qgi8IINEsDDkDgpevW2JxSjTywGGYea4J3M5oOdg\nNhjNWt00H/rugEzkB9hP4po9QHSFX5qWgzT/ws01mOcaOr4UQ8msSyVZmfpJkdHy\nx4n4jhvdlsQKhKM7OmpuXGIA7r/lqU5WDQl1Erj/6cNeWp4vx+606mvbjpzk2Lcp\ni0wBnz27jvN4Xvw+zBMzMBMm5iPwKDMKUyo3q87DFC6lBvBwF0kbPom+yLhHH/rF\n0hr21PATUrHHutFebZ3ZqZwusiKKOoD6fpQrF2mwnVGHQPwTUamSFKQZsf9jw3ic\n4zY2nruXc0OSWS2gf1FKRDxpgpMUjthA3nO1YJuiP4I7fB5mqSoYY8bsyhc=\n-----END CERTIFICATE-----\n"  --cert_content "-----BEGIN CERTIFICATE-----\nMIIFHDCCAwSgAwIBAgIIcePfAqBgEAAwDQYJKoZIhvcNAQELBQAwVzEYMBYGA1UE\nCgwPUHJvdGVncml0eSBJbmMuMQswCQYDVQQGEwJVUzEuMCwGA1UEAwwlUHJvdGVn\ncml0eSBSb290IENBIC0gWkldeedKRE5tekdPdGEyQzAgGA8yMDI1MTIyMTAwMDAw\nMFoXDTM1MTIyMDA3NDE1MlowQzEYMBYGA1UECgwPUHJvdGVncml0eSBJbmMuMQsw\nCQYDVQQGEwJVUzEaMBgGA1UEAwwRUHJvdGVncml0eSBDbGllbnQwggIiMA0GCSqG\nSIb3DQEBAQUAA4ICDwAwggIKAoICAQCn7/6ZMkJkt1/9iOj+0S8aE64w69iSpEUH\ns/wlCJG5mx7QhMKwTeJSjXO+oVSDH7Kr+eoIpTh4Zt6aC9oUaynJ4tLpE1/xb5V9\n2Brafthx6b49/kgeCEvDQtFbmwJPOZ9f2W71oK8s6zgM/dASpH4LgAu3Y7vfJ9eH\nZB63MuDFc429WyDuXQ4xnQ07RUKd40Q7JSKt4WNIdl7IVlAdAwTg+/4+xhYohSgi\ndi82XJRD0MCs0EQg6K5G0Do8DcAmdBsE3LTjJr55G1Juscv6qfh0BCTuyhJpS3dI\nQa5YiSuTIDiO45h8V4BS/+AB42tYSejvQKVmCbaCb9aqwn9LjrM0G4GYU0llvVi0\nvi8d76s9wb1V0Au0lkr/xFMCXebYWGr1I48kKlFKf0l11fP0rjAQO+qWwNJI1ax8\n7g1dh49NwBJbnZJvlv1Hb5KlrOvwHfr8UkFBZ1GVBZum0wbwFirZXxuU43AZp2S\nnwVDl+i3fP4FEu8SMIijhU3NQeA8PbVcyx3xgsOiNO3wXp2Rt380D4Ynw5A7pF6Y\nUD4TefMzUCgDFEykuUzZlnT9mBR34F4bYUQSLPPqWDXedAHfuUh9na2ws3BltpAV\nvpNM9xWl2NQN6Xsp+gAuMwIHcj0FTiJ38UFyzvPCJ/e+FsW3qWQkgDNhUYlOAplf\np8o/+1Fm7wIDAQABMA0GCSqGSIb3DQEBCwUAA4ICAQB+s91FIrthptvdBygBsen4\nLaQpfAGIEyeiG1VdTeXtlev2HjPk0p3FnbjZVQhyT00SCWPHa7Vd6ypIqlIFYvnq\nUvUc0fkUqnpAeRWK9p1bif32Qs3rS6Q8mDDVbe2BP/gxOdrPkKPZLZ/rA4cYQAh0\nx/RsdxXtiBkOQpNjZO+UUbyPqohRKek/yLEiltsdBcXeFzcUbZMxks8CAmKVB3Pn\n69NmqZOcJtcj0ydBKL1MdUxPSHXks0z8afVa5IlbJaeaa+Ef0dMDzL/JdH7FslaZ\ntHvgJpq2RinHx1emIlmAk1ji0L/4MCqRrCdNU1rVIob7amyd6gkAkEIYUlsHFEp1\nBdVU8hh4F9UQ6dQvZ6etO4/Pus8t4DjdY8Xllsgot4NXL94r/asG+z3QjIIokUfu\nEDRorE82P809hWhRVbZ1A66/3XERD4BGmn3PML94YdC+vOxricqkrZ4oJDD3gbow\nfJWQIZ96hMndAG0H055qvgoWNqjifw9KXLHqelHWOiyJftJrchCOwZ3gRlA8WaOy\nHvCNN1VzCOfaNw9YJlJ4c3DLzwwRxo/KinycCvDaYGhBLTkWjZFqqkdwm4cqK9cf\n3joxQKh51a5ENZ2hoJUEvlcfjerQGPMRMUR4n3GwPf7Vca3fd+S1+qA7tcldEKx9\nHte3R2N5rYd/obrdkh5J0A==\n-----END CERTIFICATE-----\n" --key_content "-----BEGIN PRIVATE KEY-----\nMIIJQgIBADANBgkqhkiG9w0BAQEFAASCCSwwggkoAgEAAoICAQCn7/6ZMkJkt1/9\niOj+0S8aE64w69iSpEUHs/wlCJG5mx7QhMKwTeJSjXO+oVSDH7Kr+eoIpTh4Zt6a\nC9oUaynJ4tLpE1/xb5V92Brafthx6b49/kgeCEvDQtFbmwJPOZ9f2W71oK8s6zgM\n/dASpH4LgAu3Y7vfJ9eHZB63MuDFc429WyDuXQ4xnQ07RUKd40Q7JSKt4WNIdl7I\nVlAdAwTg+/4+xhYohSgidi82XJRD0MCs0EQg6K5G0Do8DcAmdBsE3LTjJr55G1Ju\nscv6qfh0BCTuyhJpS3dIQa5YiSuTIDiO45h8V4BS/+AB42tYSejvQKVmCbaCb9aq\nwn9LjrM0G4GYU0llvVi0vi8d76s9wb1V0Au0lkr/xFMCXebYWGr1I48kKlFKf0l1\n1fP0rjAQO+qWwNJI1ax87g1dh49NwBJbnZJvlv1Hb5Kls2rvwHVcp4UkFBZ1GVBZu\nm0wbwFirZXxuU43AZp2SnwVDl+i3fP4FEu8SMIijhU3NQeA8PbVcyx3xgsOiNO3w\nXp2Rt380D4Ynw5A7pF6YUD4TefMzUCgDFEykuUzZlnT9mBR34F4bYUQSLPPqWDXe\ndAHfuUh9na2ws3BltpAVvpNM9xWl2NQN6Xsp+gAuMwIHcj0FTiJ38UFyzvPCJ/e+\nFsW3qWQkgDNhUYlOAplfp8o/+1Fm7wIDAQABAoICAQCbaiSpzbNX1cRFs7A8MYZv\nkYsAxyJ0AwXHLS/Jbfa+V+naeyJZWpp6X2GgJ1k4x9roAK4vNgfelQSodxNpFgtk\nRD9/Z2jA3Mzx205uqjjQospmQK6o7HCA0ZNCPV+TxfXSFDz1n7C91yjWDQXEWuoy\n5lrxaqDw0cRKDcPHMpSE5n1jobQGI6QBEiCum1gdGbeJLMK9O/pPkwwARrB5SNP5\nCfuuSE81TJVp3wmuO1sSr1vAEjUaZ3rxGb7q2Kbcb1KZ206jcLWRClHtEyl8XlQJ\nudQcEHGddDN9cRtR4A+tZoIw6juxxqCBLz81QCuVV0D0OVVX6uE2MR3uhXSawwgEU\nVWIcWvgXkTgEbg/KgrZ3R9VN7XjawMLVv+3dLQp4idD7keoKWCOHXZtdEXalCmLV\nQQxNtwHkjF0yG+mu6nFEiy89onvTLJtzwriu16BYf8kVnUyd3F94LYQZDWRxCuuG\nNppl0VfikZGM+0P0PpKGy3Yn+qR6d4NhaYFxbrgezRg0KlshWpM/N6ZISBj9QjsZ\nPID4oVDNiTk0nEiHlz4SYqsGrTmPdEIwLTO0QL2SFrcNwqh+qT50s7QFqu+Mwl8E\nieRXdEc5mV0qTQvUWPjNh0l6oEwsKi0dxUL5j4utr3WQgk1Fq/1LNgVFL/rBbAIX\ncI3hmU3UQBiTUtzJ3iDytQKCAQEA3LpDbn7TAwr7DMwA1nBTrv5bwGKN7SGan6fN\nL9BI0uyW3H9EZtlhE2kxapF20//gMlvIYO1kW+vySvXTK6IrBzb9s8dzycqbhpyP\n1Z7HQHJeRjNuExTHlX8hU2kW/evmWeRswJwSo37zf6XWMBN4D/i78OEbNDpTLFDA\n2iYWGx2+Cex7nzsSI1omOhek4UyejKsk4Iv2621ezH2mTsHfyxajP/GsCUIHDB6r\nB2nL8YzY/u4nzOVXu5N+sSthQTn3L4KiFavlOd00cCL22J7Dk15CyXn11MHxdo1p\npXZD/sEJfgmiWvroFlHBDRQRzHhPO7j0SzrssOkysNq/aW1eGQKCAQEAwsYkdUWt\nx0fRSaKyC4IJhsKiFcceZdbmHXPd1iaK+oAGhTzz3xDBDlQYbwy6ej8uk8/3PqBW\nfZPOWD9DszTE7k/Rsd4jwVFMD2daE09JVGyPZ7bq4X3qQ7oL120b6Oi1ZuYIXMPs\nlJzgQbOyPzUZess1OUSNwfB8pZhMkjvgmkkSUlZgyQx5+PRW9cZsf4POO9vCAFRL\nOyNlPMAqT1vvGbtatnHc6iY0v1Gl5J0NJfrzpd6b/Cr619NflpSUw6nEd0PLaGl7\naTqCPdMb5Fh7iISmysfSgVavZo5nIvRNY8vVQX8MBaQdmTKXXfYFbiYgZ+uL4hWg\nlTYXdQGQlIx+RwKCAQAjCKVfSl3vo7SJKXAQmS+PHOwvMvVX5/eE07trlWGZqNeh\nE8olkOcpj466XXBA4eIR3COHzuYY+PAyGaZ0zH6L3JyUBlpIcxIQYZUq0NLLVdvE\nxLD58lhjUBRYCtwNXX3oUqs4Pw1uSd4YKpg+dTifQFmEOBZ7Sa6d4AtcFKN5llTt\nek18zoFofwyGN+6BnAmmRhvKUCzW3TsoteDJq1f8AhHTOmaV6Zb4w31d5drq8fIX\nNHG4wcYVDaoUMNB06+Bh+BgF3Iy7jHKgQcxwQXLFVza+h88O/+F1caiNDKJqMvVw\nvdK5Ig3oTP2ZN9BDZe0di5OqxSWARuM20uGCuEsxAoIBABMLXLU6wushUo1ooxAM\n/vF2RnLqrUY35PgsRByUWDJ2Ii0U8KN29+l2v4zcKb+aPeumAf7Vnp9YvGxUg0Ia\nfsbudwp1NfnJAS7gZCZPMlRW6Q6zC/RQY3+LyWye9oOnfVU6WMb5QUCmtia2c09K\n2drv05xt345+/TET2yjRQfzT+D6kw4Hk/mghO/98D0/Ii3m+2xE9LL3zkAqIn5py\n2sYhU5VTPM6IPdAXI6le0dJM31Xwlj/p0+0Wddo7XPBkwRkIP/NNnQuE9QcmhSum\nmy2WCtj5ANQ0raHRerQoPwjq/UcSLRLAIUTBdZtyWsWSZMjEd0D77F+qklCWfpSH\nyDECggEAEaCankeqpmPcSBDdvHZ9TP42aYqvvgrb36bK8A4HdGujx2dWafPcLojm\nizEtUPv2nVU2sGjGmPct5gSCS0oSwjVoIj7UKjT1dLN2QA115mFuZXNsz7UEifdU\n6XuIHztTcDTmhsDGx/XtsnZFyfEl9z3zZIkO4aJ9lbBiyw5LamGD1ykQ2DavxCFE\neFalDX9PGS/VERX9foHLLXDyEXYuoo8pf3ltupYmqbxMSX5Hf1NvtqYBSTvYiaCv\nmQJ3EuuxjzxXcCuI0YWPcAxlAViz9NAzgk+gxbOB6kEHvq/GWWRebQdvGdSHE9zV\ng5HfdOn7snl93cZxCP+JcOFG55h0Dg==\n-----END PRIVATE KEY-----\n" --troubleshooting_log True

The pods take some time to initialize and stabilize after running this command. Verify the status of the pods using the kubectl get pods -n pty-insightcommand. Avoid updating any more configurations till the pods are ready.

Configuring the fluentd that receives the logs

The logs forwarded to the SIEM are captured by fluentd on the SIEM. Ensure that the fluentd on the SIEM is configured to send the logs to the required location, such as, a file or another system. The steps provided here store the logs to a file. For more information about the forwarding logs to various systems, refer to the Fluentd documentation.

To configure the external fluentd:

  1. Log in to the external fluentd.
  2. Create a directory for storing the logs.
mkdir fluentd
  1. Update the required permissions for the directory.

For example:

chown -R td-agent:td-agent fluentd
chmod -R 755 fluentd
  1. Open the output configuration using a text edition. The file might be in one of the following locations.
  • /etc/fluent/
  • /etc/td-agent/conf.d/
  • /fluentd/etc/
  1. Optional: Update the code to forward the protector logs to the existing location.

    1. Locate the match tag in the file.
    2. Add the logdata flulog code to the tag to forward the protector logs.
    <match logdata flulog>
    
  2. Add a match tag with the configuration to the required location. This example sends the logs to a file on the external SIEM. A sample code is provided here. Customize and use the code for your system.

<match kubernetes.**>
  @type copy

  <store>
   @type file
   @log_level info

   # MUST include ${tag}
   path /fluentd/log/out/audit.${tag}
   append true

   <format>
     @type json
   </format>

   # MUST include tag because we used ${tag} above
   <buffer tag,time>
     @type file
     path /fluentd/log/buffer/file_out

     timekey 1m
     timekey_wait 10s

     flush_mode interval
     flush_interval 10s
     flush_thread_count 2

     retry_forever true
     retry_type periodic
     retry_wait 5s
   </buffer>
  </store>

  # keep your existing label routing behavior (optional but usually intended)

</match>
  1. Save and close the file.
  2. Restart the fluentd service.

Updating the log forwarding configuration

The command to update the logs forwarding settings to the syslog server.

insight update fluentd --host <fluentd_IP_address> --port <fluentd_port> --ca_content "<ca.crt_content>"  --cert_content "<client.crt_content>" --key_content "<client.key_content>"

Example:

insight update fluentd --host 192.168.1.110 --port 24284 --ca_content "-----BEGIN CERTIFICATE-----\nMIIFmDCCA4CgAwIBAgIIWF8OX+P4jAAwDQYJKoZIhvcNAQELBQAwVzEYMBYGA1UE\nCgwPUHJvdGVncml0eSBJbmMuMQswCQYDVQQGEwJVUzEuMCwGA1UEAwwlUHJvdGVn\ncml0eSBSb290IENBIC0gWklTbkdKRE5tekdPdGEyQzAgGA8yMDI1MTIyMTAwMDAw\nMFoXDTM1MTIyMDA3NDE1MFowVzEYMBYGA1UECgwPUHJvdGVncml0eSBJbmMuMQsw\nCQYDVQQGEwJVUzEuMCwGA1UEAwwlUHJvdGVncml0eSBSb290IENBIC0gWklTbkdK\nRE5tekdPdGEyQzCCAiIwDQYJKoZIhvcNAQEBBQADggIPADCCAgoCggIBAL6nK47Y\n/hs1nBnHxg2/S6ieL/JH9H6M9321qHaSIbqAS2KBy2iNDoy3EhKvHXOgd4TgWc7+\nMGiREDK9QsOZ1UKFn5p5cXt0lkGsRSVB5sh2GurGxCtKEwtXlK8OGAWhz46dmjEr\nT02SH7H6WQA+Zh8+OTdzjpo/aujdI6pGVslSY/ulFcqQF16U7aRTmobPpdSZuFWN\nuBcoAXLhDBLutCWQaYSodksRha6I6olrlSditoHHGOnMWC6S4/+NT1XtSvBEIhVn\nMDRym6UKLNlhR+bb3lyGK5HgA2frXduNIL244z931Ii+JAnvpIsZrQ9k1UghG0L7\n3zLTMSCf1y3yWKhXWnPcN41zWeqiF+gk0zFoIQiaDPjhqNyjzTheXX8YqiTf226E\nxTg1Xrac3LF5Ju+3gCioUzpOo3WbphDmZfDTMBj0cWn7GszLkiNd/AX5bLf/+OdJ\n9KaZSOQcit4A9bxERWFS0vT8aGfN43mUFXrpKLmpltZkmtt4XloEeGndZbHF60hy\n+nRzJVNs9B63xP9+NdpWgvoiRVOBKB04XVcNC6nMCMwYjJRLmBzQQ9PT3dQ2dnpj\nj0TuU/44bj5S5t6aVvEOeKanHHeVqRQm8Kzt4WfDvjp1ASOkApvA5+Xs+DpcKbWH\nMCAZDQpi2vWu8d+c569FvN4e0SbP0qM26NgvAgMBAAGjZjBkMBIGA1UdEwEB/wQI\nMAYBAf8CAQAwDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBSnfq6PGf8AwEL9XGyQ\nM1I6087OzjAfBgNVHSMEGDAWgBSnfq6PGf8AwEL9XGyQM1I6087OzjANBgkqhkiG\n9w0BAQsFAAOCAgEALXZZNaa60cpYNFEXgr780IqKUdZa995OvRUs1dCYd4WqzzJD\nVad8Z48GJX3/u/XAk2UM+mUSGaFowqhek58YX0b24O0PG+y3O0XT0EX/+80Fu+Kt\nkPSbiaPyeYxGqEjwed/Y9X5AJig68NA/FRcT5dq2sWA8hcej8Ghm6D3gu9PdBWpk\nRstITsdaSfx6N+avJ0keGMHqLDLSr948XbehRHH9FnvkPfDtkwKzNwhYmeB6/c+v\nal/JLfPy6VWi3fK37XmuhSh2aZ/vsjT7sxvfFTndUVBeumvCS4wW+bByxpC5XBHW\nB1TrPCczqaDqDD/ib1YCLfY6Qgi8IINEsDDkDgpevW2JxSjTywGGYea4J3M5oOdg\nNhjNWt00H/rugEzkB9hP4po9QHSFX5qWgzT/ws01mOcaOr4UQ8msSyVZmfpJkdHy\nx4n4jhvdlsQKhKM7OmpuXGIA7r/lqU5WDQl1Erj/6cNeWp4vx+606mvbjpzk2Lcp\ni0wBnz27jvN4Xvw+zBMzMBMm5iPwKDMKUyo3q87DFC6lBvBwF0kbPom+yLhHH/rF\n0hr21PATUrHHutFebZ3ZqZwusiKKOoD6fpQrF2mwnVGHQPwTUamSFKQZsf9jw3ic\n4zY2nruXc0OSWS2gf1FKRDxpgpMUjthA3nO1YJuiP4I7fB5mqSoYY8bsyhc=\n-----END CERTIFICATE-----\n"  --cert_content "-----BEGIN CERTIFICATE-----\nMIIFHDCCAwSgAwIBAgIIcePfAqBgEAAwDQYJKoZIhvcNAQELBQAwVzEYMBYGA1UE\nCgwPUHJvdGVncml0eSBJbmMuMQswCQYDVQQGEwJVUzEuMCwGA1UEAwwlUHJvdGVn\ncml0eSBSb290IENBIC0gWkldeedKRE5tekdPdGEyQzAgGA8yMDI1MTIyMTAwMDAw\nMFoXDTM1MTIyMDA3NDE1MlowQzEYMBYGA1UECgwPUHJvdGVncml0eSBJbmMuMQsw\nCQYDVQQGEwJVUzEaMBgGA1UEAwwRUHJvdGVncml0eSBDbGllbnQwggIiMA0GCSqG\nSIb3DQEBAQUAA4ICDwAwggIKAoICAQCn7/6ZMkJkt1/9iOj+0S8aE64w69iSpEUH\ns/wlCJG5mx7QhMKwTeJSjXO+oVSDH7Kr+eoIpTh4Zt6aC9oUaynJ4tLpE1/xb5V9\n2Brafthx6b49/kgeCEvDQtFbmwJPOZ9f2W71oK8s6zgM/dASpH4LgAu3Y7vfJ9eH\nZB63MuDFc429WyDuXQ4xnQ07RUKd40Q7JSKt4WNIdl7IVlAdAwTg+/4+xhYohSgi\ndi82XJRD0MCs0EQg6K5G0Do8DcAmdBsE3LTjJr55G1Juscv6qfh0BCTuyhJpS3dI\nQa5YiSuTIDiO45h8V4BS/+AB42tYSejvQKVmCbaCb9aqwn9LjrM0G4GYU0llvVi0\nvi8d76s9wb1V0Au0lkr/xFMCXebYWGr1I48kKlFKf0l11fP0rjAQO+qWwNJI1ax8\n7g1dh49NwBJbnZJvlv1Hb5KlrOvwHfr8UkFBZ1GVBZum0wbwFirZXxuU43AZp2S\nnwVDl+i3fP4FEu8SMIijhU3NQeA8PbVcyx3xgsOiNO3wXp2Rt380D4Ynw5A7pF6Y\nUD4TefMzUCgDFEykuUzZlnT9mBR34F4bYUQSLPPqWDXedAHfuUh9na2ws3BltpAV\nvpNM9xWl2NQN6Xsp+gAuMwIHcj0FTiJ38UFyzvPCJ/e+FsW3qWQkgDNhUYlOAplf\np8o/+1Fm7wIDAQABMA0GCSqGSIb3DQEBCwUAA4ICAQB+s91FIrthptvdBygBsen4\nLaQpfAGIEyeiG1VdTeXtlev2HjPk0p3FnbjZVQhyT00SCWPHa7Vd6ypIqlIFYvnq\nUvUc0fkUqnpAeRWK9p1bif32Qs3rS6Q8mDDVbe2BP/gxOdrPkKPZLZ/rA4cYQAh0\nx/RsdxXtiBkOQpNjZO+UUbyPqohRKek/yLEiltsdBcXeFzcUbZMxks8CAmKVB3Pn\n69NmqZOcJtcj0ydBKL1MdUxPSHXks0z8afVa5IlbJaeaa+Ef0dMDzL/JdH7FslaZ\ntHvgJpq2RinHx1emIlmAk1ji0L/4MCqRrCdNU1rVIob7amyd6gkAkEIYUlsHFEp1\nBdVU8hh4F9UQ6dQvZ6etO4/Pus8t4DjdY8Xllsgot4NXL94r/asG+z3QjIIokUfu\nEDRorE82P809hWhRVbZ1A66/3XERD4BGmn3PML94YdC+vOxricqkrZ4oJDD3gbow\nfJWQIZ96hMndAG0H055qvgoWNqjifw9KXLHqelHWOiyJftJrchCOwZ3gRlA8WaOy\nHvCNN1VzCOfaNw9YJlJ4c3DLzwwRxo/KinycCvDaYGhBLTkWjZFqqkdwm4cqK9cf\n3joxQKh51a5ENZ2hoJUEvlcfjerQGPMRMUR4n3GwPf7Vca3fd+S1+qA7tcldEKx9\nHte3R2N5rYd/obrdkh5J0A==\n-----END CERTIFICATE-----\n" --key_content "-----BEGIN PRIVATE KEY-----\nMIIJQgIBADANBgkqhkiG9w0BAQEFAASCCSwwggkoAgEAAoICAQCn7/6ZMkJkt1/9\niOj+0S8aE64w69iSpEUHs/wlCJG5mx7QhMKwTeJSjXO+oVSDH7Kr+eoIpTh4Zt6a\nC9oUaynJ4tLpE1/xb5V92Brafthx6b49/kgeCEvDQtFbmwJPOZ9f2W71oK8s6zgM\n/dASpH4LgAu3Y7vfJ9eHZB63MuDFc429WyDuXQ4xnQ07RUKd40Q7JSKt4WNIdl7I\nVlAdAwTg+/4+xhYohSgidi82XJRD0MCs0EQg6K5G0Do8DcAmdBsE3LTjJr55G1Ju\nscv6qfh0BCTuyhJpS3dIQa5YiSuTIDiO45h8V4BS/+AB42tYSejvQKVmCbaCb9aq\nwn9LjrM0G4GYU0llvVi0vi8d76s9wb1V0Au0lkr/xFMCXebYWGr1I48kKlFKf0l1\n1fP0rjAQO+qWwNJI1ax87g1dh49NwBJbnZJvlv1Hb5Kls2rvwHVcp4UkFBZ1GVBZu\nm0wbwFirZXxuU43AZp2SnwVDl+i3fP4FEu8SMIijhU3NQeA8PbVcyx3xgsOiNO3w\nXp2Rt380D4Ynw5A7pF6YUD4TefMzUCgDFEykuUzZlnT9mBR34F4bYUQSLPPqWDXe\ndAHfuUh9na2ws3BltpAVvpNM9xWl2NQN6Xsp+gAuMwIHcj0FTiJ38UFyzvPCJ/e+\nFsW3qWQkgDNhUYlOAplfp8o/+1Fm7wIDAQABAoICAQCbaiSpzbNX1cRFs7A8MYZv\nkYsAxyJ0AwXHLS/Jbfa+V+naeyJZWpp6X2GgJ1k4x9roAK4vNgfelQSodxNpFgtk\nRD9/Z2jA3Mzx205uqjjQospmQK6o7HCA0ZNCPV+TxfXSFDz1n7C91yjWDQXEWuoy\n5lrxaqDw0cRKDcPHMpSE5n1jobQGI6QBEiCum1gdGbeJLMK9O/pPkwwARrB5SNP5\nCfuuSE81TJVp3wmuO1sSr1vAEjUaZ3rxGb7q2Kbcb1KZ206jcLWRClHtEyl8XlQJ\nudQcEHGddDN9cRtR4A+tZoIw6juxxqCBLz81QCuVV0D0OVVX6uE2MR3uhXSawwgEU\nVWIcWvgXkTgEbg/KgrZ3R9VN7XjawMLVv+3dLQp4idD7keoKWCOHXZtdEXalCmLV\nQQxNtwHkjF0yG+mu6nFEiy89onvTLJtzwriu16BYf8kVnUyd3F94LYQZDWRxCuuG\nNppl0VfikZGM+0P0PpKGy3Yn+qR6d4NhaYFxbrgezRg0KlshWpM/N6ZISBj9QjsZ\nPID4oVDNiTk0nEiHlz4SYqsGrTmPdEIwLTO0QL2SFrcNwqh+qT50s7QFqu+Mwl8E\nieRXdEc5mV0qTQvUWPjNh0l6oEwsKi0dxUL5j4utr3WQgk1Fq/1LNgVFL/rBbAIX\ncI3hmU3UQBiTUtzJ3iDytQKCAQEA3LpDbn7TAwr7DMwA1nBTrv5bwGKN7SGan6fN\nL9BI0uyW3H9EZtlhE2kxapF20//gMlvIYO1kW+vySvXTK6IrBzb9s8dzycqbhpyP\n1Z7HQHJeRjNuExTHlX8hU2kW/evmWeRswJwSo37zf6XWMBN4D/i78OEbNDpTLFDA\n2iYWGx2+Cex7nzsSI1omOhek4UyejKsk4Iv2621ezH2mTsHfyxajP/GsCUIHDB6r\nB2nL8YzY/u4nzOVXu5N+sSthQTn3L4KiFavlOd00cCL22J7Dk15CyXn11MHxdo1p\npXZD/sEJfgmiWvroFlHBDRQRzHhPO7j0SzrssOkysNq/aW1eGQKCAQEAwsYkdUWt\nx0fRSaKyC4IJhsKiFcceZdbmHXPd1iaK+oAGhTzz3xDBDlQYbwy6ej8uk8/3PqBW\nfZPOWD9DszTE7k/Rsd4jwVFMD2daE09JVGyPZ7bq4X3qQ7oL120b6Oi1ZuYIXMPs\nlJzgQbOyPzUZess1OUSNwfB8pZhMkjvgmkkSUlZgyQx5+PRW9cZsf4POO9vCAFRL\nOyNlPMAqT1vvGbtatnHc6iY0v1Gl5J0NJfrzpd6b/Cr619NflpSUw6nEd0PLaGl7\naTqCPdMb5Fh7iISmysfSgVavZo5nIvRNY8vVQX8MBaQdmTKXXfYFbiYgZ+uL4hWg\nlTYXdQGQlIx+RwKCAQAjCKVfSl3vo7SJKXAQmS+PHOwvMvVX5/eE07trlWGZqNeh\nE8olkOcpj466XXBA4eIR3COHzuYY+PAyGaZ0zH6L3JyUBlpIcxIQYZUq0NLLVdvE\nxLD58lhjUBRYCtwNXX3oUqs4Pw1uSd4YKpg+dTifQFmEOBZ7Sa6d4AtcFKN5llTt\nek18zoFofwyGN+6BnAmmRhvKUCzW3TsoteDJq1f8AhHTOmaV6Zb4w31d5drq8fIX\nNHG4wcYVDaoUMNB06+Bh+BgF3Iy7jHKgQcxwQXLFVza+h88O/+F1caiNDKJqMvVw\nvdK5Ig3oTP2ZN9BDZe0di5OqxSWARuM20uGCuEsxAoIBABMLXLU6wushUo1ooxAM\n/vF2RnLqrUY35PgsRByUWDJ2Ii0U8KN29+l2v4zcKb+aPeumAf7Vnp9YvGxUg0Ia\nfsbudwp1NfnJAS7gZCZPMlRW6Q6zC/RQY3+LyWye9oOnfVU6WMb5QUCmtia2c09K\n2drv05xt345+/TET2yjRQfzT+D6kw4Hk/mghO/98D0/Ii3m+2xE9LL3zkAqIn5py\n2sYhU5VTPM6IPdAXI6le0dJM31Xwlj/p0+0Wddo7XPBkwRkIP/NNnQuE9QcmhSum\nmy2WCtj5ANQ0raHRerQoPwjq/UcSLRLAIUTBdZtyWsWSZMjEd0D77F+qklCWfpSH\nyDECggEAEaCankeqpmPcSBDdvHZ9TP42aYqvvgrb36bK8A4HdGujx2dWafPcLojm\nizEtUPv2nVU2sGjGmPct5gSCS0oSwjVoIj7UKjT1dLN2QA115mFuZXNsz7UEifdU\n6XuIHztTcDTmhsDGx/XtsnZFyfEl9z3zZIkO4aJ9lbBiyw5LamGD1ykQ2DavxCFE\neFalDX9PGS/VERX9foHLLXDyEXYuoo8pf3ltupYmqbxMSX5Hf1NvtqYBSTvYiaCv\nmQJ3EuuxjzxXcCuI0YWPcAxlAViz9NAzgk+gxbOB6kEHvq/GWWRebQdvGdSHE9zV\ng5HfdOn7snl93cZxCP+JcOFG55h0Dg==\n-----END PRIVATE KEY-----\n"
insight update fluentd --host <fluentd_IP_address> --port <fluentd_port> --ca_content "<ca.crt_content>"  --cert_content "<client.crt_content>" --key_content "<client.key_content>" --troubleshooting_log True

Example:

insight update fluentd --host 192.168.1.110 --port 24284 --ca_content "-----BEGIN CERTIFICATE-----\nMIIFmDCCA4CgAwIBAgIIWF8OX+P4jAAwDQYJKoZIhvcNAQELBQAwVzEYMBYGA1UE\nCgwPUHJvdGVncml0eSBJbmMuMQswCQYDVQQGEwJVUzEuMCwGA1UEAwwlUHJvdGVn\ncml0eSBSb290IENBIC0gWklTbkdKRE5tekdPdGEyQzAgGA8yMDI1MTIyMTAwMDAw\nMFoXDTM1MTIyMDA3NDE1MFowVzEYMBYGA1UECgwPUHJvdGVncml0eSBJbmMuMQsw\nCQYDVQQGEwJVUzEuMCwGA1UEAwwlUHJvdGVncml0eSBSb290IENBIC0gWklTbkdK\nRE5tekdPdGEyQzCCAiIwDQYJKoZIhvcNAQEBBQADggIPADCCAgoCggIBAL6nK47Y\n/hs1nBnHxg2/S6ieL/JH9H6M9321qHaSIbqAS2KBy2iNDoy3EhKvHXOgd4TgWc7+\nMGiREDK9QsOZ1UKFn5p5cXt0lkGsRSVB5sh2GurGxCtKEwtXlK8OGAWhz46dmjEr\nT02SH7H6WQA+Zh8+OTdzjpo/aujdI6pGVslSY/ulFcqQF16U7aRTmobPpdSZuFWN\nuBcoAXLhDBLutCWQaYSodksRha6I6olrlSditoHHGOnMWC6S4/+NT1XtSvBEIhVn\nMDRym6UKLNlhR+bb3lyGK5HgA2frXduNIL244z931Ii+JAnvpIsZrQ9k1UghG0L7\n3zLTMSCf1y3yWKhXWnPcN41zWeqiF+gk0zFoIQiaDPjhqNyjzTheXX8YqiTf226E\nxTg1Xrac3LF5Ju+3gCioUzpOo3WbphDmZfDTMBj0cWn7GszLkiNd/AX5bLf/+OdJ\n9KaZSOQcit4A9bxERWFS0vT8aGfN43mUFXrpKLmpltZkmtt4XloEeGndZbHF60hy\n+nRzJVNs9B63xP9+NdpWgvoiRVOBKB04XVcNC6nMCMwYjJRLmBzQQ9PT3dQ2dnpj\nj0TuU/44bj5S5t6aVvEOeKanHHeVqRQm8Kzt4WfDvjp1ASOkApvA5+Xs+DpcKbWH\nMCAZDQpi2vWu8d+c569FvN4e0SbP0qM26NgvAgMBAAGjZjBkMBIGA1UdEwEB/wQI\nMAYBAf8CAQAwDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBSnfq6PGf8AwEL9XGyQ\nM1I6087OzjAfBgNVHSMEGDAWgBSnfq6PGf8AwEL9XGyQM1I6087OzjANBgkqhkiG\n9w0BAQsFAAOCAgEALXZZNaa60cpYNFEXgr780IqKUdZa995OvRUs1dCYd4WqzzJD\nVad8Z48GJX3/u/XAk2UM+mUSGaFowqhek58YX0b24O0PG+y3O0XT0EX/+80Fu+Kt\nkPSbiaPyeYxGqEjwed/Y9X5AJig68NA/FRcT5dq2sWA8hcej8Ghm6D3gu9PdBWpk\nRstITsdaSfx6N+avJ0keGMHqLDLSr948XbehRHH9FnvkPfDtkwKzNwhYmeB6/c+v\nal/JLfPy6VWi3fK37XmuhSh2aZ/vsjT7sxvfFTndUVBeumvCS4wW+bByxpC5XBHW\nB1TrPCczqaDqDD/ib1YCLfY6Qgi8IINEsDDkDgpevW2JxSjTywGGYea4J3M5oOdg\nNhjNWt00H/rugEzkB9hP4po9QHSFX5qWgzT/ws01mOcaOr4UQ8msSyVZmfpJkdHy\nx4n4jhvdlsQKhKM7OmpuXGIA7r/lqU5WDQl1Erj/6cNeWp4vx+606mvbjpzk2Lcp\ni0wBnz27jvN4Xvw+zBMzMBMm5iPwKDMKUyo3q87DFC6lBvBwF0kbPom+yLhHH/rF\n0hr21PATUrHHutFebZ3ZqZwusiKKOoD6fpQrF2mwnVGHQPwTUamSFKQZsf9jw3ic\n4zY2nruXc0OSWS2gf1FKRDxpgpMUjthA3nO1YJuiP4I7fB5mqSoYY8bsyhc=\n-----END CERTIFICATE-----\n"  --cert_content "-----BEGIN CERTIFICATE-----\nMIIFHDCCAwSgAwIBAgIIcePfAqBgEAAwDQYJKoZIhvcNAQELBQAwVzEYMBYGA1UE\nCgwPUHJvdGVncml0eSBJbmMuMQswCQYDVQQGEwJVUzEuMCwGA1UEAwwlUHJvdGVn\ncml0eSBSb290IENBIC0gWkldeedKRE5tekdPdGEyQzAgGA8yMDI1MTIyMTAwMDAw\nMFoXDTM1MTIyMDA3NDE1MlowQzEYMBYGA1UECgwPUHJvdGVncml0eSBJbmMuMQsw\nCQYDVQQGEwJVUzEaMBgGA1UEAwwRUHJvdGVncml0eSBDbGllbnQwggIiMA0GCSqG\nSIb3DQEBAQUAA4ICDwAwggIKAoICAQCn7/6ZMkJkt1/9iOj+0S8aE64w69iSpEUH\ns/wlCJG5mx7QhMKwTeJSjXO+oVSDH7Kr+eoIpTh4Zt6aC9oUaynJ4tLpE1/xb5V9\n2Brafthx6b49/kgeCEvDQtFbmwJPOZ9f2W71oK8s6zgM/dASpH4LgAu3Y7vfJ9eH\nZB63MuDFc429WyDuXQ4xnQ07RUKd40Q7JSKt4WNIdl7IVlAdAwTg+/4+xhYohSgi\ndi82XJRD0MCs0EQg6K5G0Do8DcAmdBsE3LTjJr55G1Juscv6qfh0BCTuyhJpS3dI\nQa5YiSuTIDiO45h8V4BS/+AB42tYSejvQKVmCbaCb9aqwn9LjrM0G4GYU0llvVi0\nvi8d76s9wb1V0Au0lkr/xFMCXebYWGr1I48kKlFKf0l11fP0rjAQO+qWwNJI1ax8\n7g1dh49NwBJbnZJvlv1Hb5KlrOvwHfr8UkFBZ1GVBZum0wbwFirZXxuU43AZp2S\nnwVDl+i3fP4FEu8SMIijhU3NQeA8PbVcyx3xgsOiNO3wXp2Rt380D4Ynw5A7pF6Y\nUD4TefMzUCgDFEykuUzZlnT9mBR34F4bYUQSLPPqWDXedAHfuUh9na2ws3BltpAV\nvpNM9xWl2NQN6Xsp+gAuMwIHcj0FTiJ38UFyzvPCJ/e+FsW3qWQkgDNhUYlOAplf\np8o/+1Fm7wIDAQABMA0GCSqGSIb3DQEBCwUAA4ICAQB+s91FIrthptvdBygBsen4\nLaQpfAGIEyeiG1VdTeXtlev2HjPk0p3FnbjZVQhyT00SCWPHa7Vd6ypIqlIFYvnq\nUvUc0fkUqnpAeRWK9p1bif32Qs3rS6Q8mDDVbe2BP/gxOdrPkKPZLZ/rA4cYQAh0\nx/RsdxXtiBkOQpNjZO+UUbyPqohRKek/yLEiltsdBcXeFzcUbZMxks8CAmKVB3Pn\n69NmqZOcJtcj0ydBKL1MdUxPSHXks0z8afVa5IlbJaeaa+Ef0dMDzL/JdH7FslaZ\ntHvgJpq2RinHx1emIlmAk1ji0L/4MCqRrCdNU1rVIob7amyd6gkAkEIYUlsHFEp1\nBdVU8hh4F9UQ6dQvZ6etO4/Pus8t4DjdY8Xllsgot4NXL94r/asG+z3QjIIokUfu\nEDRorE82P809hWhRVbZ1A66/3XERD4BGmn3PML94YdC+vOxricqkrZ4oJDD3gbow\nfJWQIZ96hMndAG0H055qvgoWNqjifw9KXLHqelHWOiyJftJrchCOwZ3gRlA8WaOy\nHvCNN1VzCOfaNw9YJlJ4c3DLzwwRxo/KinycCvDaYGhBLTkWjZFqqkdwm4cqK9cf\n3joxQKh51a5ENZ2hoJUEvlcfjerQGPMRMUR4n3GwPf7Vca3fd+S1+qA7tcldEKx9\nHte3R2N5rYd/obrdkh5J0A==\n-----END CERTIFICATE-----\n" --key_content "-----BEGIN PRIVATE KEY-----\nMIIJQgIBADANBgkqhkiG9w0BAQEFAASCCSwwggkoAgEAAoICAQCn7/6ZMkJkt1/9\niOj+0S8aE64w69iSpEUHs/wlCJG5mx7QhMKwTeJSjXO+oVSDH7Kr+eoIpTh4Zt6a\nC9oUaynJ4tLpE1/xb5V92Brafthx6b49/kgeCEvDQtFbmwJPOZ9f2W71oK8s6zgM\n/dASpH4LgAu3Y7vfJ9eHZB63MuDFc429WyDuXQ4xnQ07RUKd40Q7JSKt4WNIdl7I\nVlAdAwTg+/4+xhYohSgidi82XJRD0MCs0EQg6K5G0Do8DcAmdBsE3LTjJr55G1Ju\nscv6qfh0BCTuyhJpS3dIQa5YiSuTIDiO45h8V4BS/+AB42tYSejvQKVmCbaCb9aq\nwn9LjrM0G4GYU0llvVi0vi8d76s9wb1V0Au0lkr/xFMCXebYWGr1I48kKlFKf0l1\n1fP0rjAQO+qWwNJI1ax87g1dh49NwBJbnZJvlv1Hb5Kls2rvwHVcp4UkFBZ1GVBZu\nm0wbwFirZXxuU43AZp2SnwVDl+i3fP4FEu8SMIijhU3NQeA8PbVcyx3xgsOiNO3w\nXp2Rt380D4Ynw5A7pF6YUD4TefMzUCgDFEykuUzZlnT9mBR34F4bYUQSLPPqWDXe\ndAHfuUh9na2ws3BltpAVvpNM9xWl2NQN6Xsp+gAuMwIHcj0FTiJ38UFyzvPCJ/e+\nFsW3qWQkgDNhUYlOAplfp8o/+1Fm7wIDAQABAoICAQCbaiSpzbNX1cRFs7A8MYZv\nkYsAxyJ0AwXHLS/Jbfa+V+naeyJZWpp6X2GgJ1k4x9roAK4vNgfelQSodxNpFgtk\nRD9/Z2jA3Mzx205uqjjQospmQK6o7HCA0ZNCPV+TxfXSFDz1n7C91yjWDQXEWuoy\n5lrxaqDw0cRKDcPHMpSE5n1jobQGI6QBEiCum1gdGbeJLMK9O/pPkwwARrB5SNP5\nCfuuSE81TJVp3wmuO1sSr1vAEjUaZ3rxGb7q2Kbcb1KZ206jcLWRClHtEyl8XlQJ\nudQcEHGddDN9cRtR4A+tZoIw6juxxqCBLz81QCuVV0D0OVVX6uE2MR3uhXSawwgEU\nVWIcWvgXkTgEbg/KgrZ3R9VN7XjawMLVv+3dLQp4idD7keoKWCOHXZtdEXalCmLV\nQQxNtwHkjF0yG+mu6nFEiy89onvTLJtzwriu16BYf8kVnUyd3F94LYQZDWRxCuuG\nNppl0VfikZGM+0P0PpKGy3Yn+qR6d4NhaYFxbrgezRg0KlshWpM/N6ZISBj9QjsZ\nPID4oVDNiTk0nEiHlz4SYqsGrTmPdEIwLTO0QL2SFrcNwqh+qT50s7QFqu+Mwl8E\nieRXdEc5mV0qTQvUWPjNh0l6oEwsKi0dxUL5j4utr3WQgk1Fq/1LNgVFL/rBbAIX\ncI3hmU3UQBiTUtzJ3iDytQKCAQEA3LpDbn7TAwr7DMwA1nBTrv5bwGKN7SGan6fN\nL9BI0uyW3H9EZtlhE2kxapF20//gMlvIYO1kW+vySvXTK6IrBzb9s8dzycqbhpyP\n1Z7HQHJeRjNuExTHlX8hU2kW/evmWeRswJwSo37zf6XWMBN4D/i78OEbNDpTLFDA\n2iYWGx2+Cex7nzsSI1omOhek4UyejKsk4Iv2621ezH2mTsHfyxajP/GsCUIHDB6r\nB2nL8YzY/u4nzOVXu5N+sSthQTn3L4KiFavlOd00cCL22J7Dk15CyXn11MHxdo1p\npXZD/sEJfgmiWvroFlHBDRQRzHhPO7j0SzrssOkysNq/aW1eGQKCAQEAwsYkdUWt\nx0fRSaKyC4IJhsKiFcceZdbmHXPd1iaK+oAGhTzz3xDBDlQYbwy6ej8uk8/3PqBW\nfZPOWD9DszTE7k/Rsd4jwVFMD2daE09JVGyPZ7bq4X3qQ7oL120b6Oi1ZuYIXMPs\nlJzgQbOyPzUZess1OUSNwfB8pZhMkjvgmkkSUlZgyQx5+PRW9cZsf4POO9vCAFRL\nOyNlPMAqT1vvGbtatnHc6iY0v1Gl5J0NJfrzpd6b/Cr619NflpSUw6nEd0PLaGl7\naTqCPdMb5Fh7iISmysfSgVavZo5nIvRNY8vVQX8MBaQdmTKXXfYFbiYgZ+uL4hWg\nlTYXdQGQlIx+RwKCAQAjCKVfSl3vo7SJKXAQmS+PHOwvMvVX5/eE07trlWGZqNeh\nE8olkOcpj466XXBA4eIR3COHzuYY+PAyGaZ0zH6L3JyUBlpIcxIQYZUq0NLLVdvE\nxLD58lhjUBRYCtwNXX3oUqs4Pw1uSd4YKpg+dTifQFmEOBZ7Sa6d4AtcFKN5llTt\nek18zoFofwyGN+6BnAmmRhvKUCzW3TsoteDJq1f8AhHTOmaV6Zb4w31d5drq8fIX\nNHG4wcYVDaoUMNB06+Bh+BgF3Iy7jHKgQcxwQXLFVza+h88O/+F1caiNDKJqMvVw\nvdK5Ig3oTP2ZN9BDZe0di5OqxSWARuM20uGCuEsxAoIBABMLXLU6wushUo1ooxAM\n/vF2RnLqrUY35PgsRByUWDJ2Ii0U8KN29+l2v4zcKb+aPeumAf7Vnp9YvGxUg0Ia\nfsbudwp1NfnJAS7gZCZPMlRW6Q6zC/RQY3+LyWye9oOnfVU6WMb5QUCmtia2c09K\n2drv05xt345+/TET2yjRQfzT+D6kw4Hk/mghO/98D0/Ii3m+2xE9LL3zkAqIn5py\n2sYhU5VTPM6IPdAXI6le0dJM31Xwlj/p0+0Wddo7XPBkwRkIP/NNnQuE9QcmhSum\nmy2WCtj5ANQ0raHRerQoPwjq/UcSLRLAIUTBdZtyWsWSZMjEd0D77F+qklCWfpSH\nyDECggEAEaCankeqpmPcSBDdvHZ9TP42aYqvvgrb36bK8A4HdGujx2dWafPcLojm\nizEtUPv2nVU2sGjGmPct5gSCS0oSwjVoIj7UKjT1dLN2QA115mFuZXNsz7UEifdU\n6XuIHztTcDTmhsDGx/XtsnZFyfEl9z3zZIkO4aJ9lbBiyw5LamGD1ykQ2DavxCFE\neFalDX9PGS/VERX9foHLLXDyEXYuoo8pf3ltupYmqbxMSX5Hf1NvtqYBSTvYiaCv\nmQJ3EuuxjzxXcCuI0YWPcAxlAViz9NAzgk+gxbOB6kEHvq/GWWRebQdvGdSHE9zV\ng5HfdOn7snl93cZxCP+JcOFG55h0Dg==\n-----END PRIVATE KEY-----\n" --troubleshooting_log True

The pods take some time to initialize and stabilize after running this command. Verify the status of the pods using the kubectl get pods -n pty-insightcommand. Avoid updating any more configurations till the pods are ready.

Removing the log forwarding settings

The command stops external SIEM log forwarding, removes the associated configuration, and deletes the certificate-related secrets.

insight delete fluentd 

The pods take some time to initialize and stabilize after running this command. Verify the status of the pods using the kubectl get pods -n pty-insightcommand. Avoid updating any more configurations till the pods are ready.

3 - Policy Management Command Line Interface (CLI) Reference

Policy Management CLI documentation.

Important: The Policy Management CLI will work only after you have installed the workbench.

Main Pim Command

The following command shows to access the help for the pim commands.

pim --help
Usage: pim [OPTIONS] COMMAND [ARGS]...

  Policy Information Management commands.

Options:
  --help  Show this message and exit.

Commands:
  create  Create a resource.
  delete  Delete a resource.
  get     Display one or many resources.
  invoke  Invoke resource by operation defined by the API.
  set     Update fields of a resource.

Invoke Commands

The following section lists the invoke commands.

Main Invoke Command

The following command shows how to access help for the invoke command.

pim invoke --help
Usage: pim invoke [OPTIONS] COMMAND [ARGS]...

  Invoke resource by operation defined by the API.

Options:
  --help  Show this message and exit.

Commands:
  datastores  Commands for deploying datastore resources.
  init        Bootstrap PIM - Initialize the Policy Information system.
  roles       Commands for synchronizing role resources.
  sources     Commands for testing source resources.

Invoke Datastores

The following command shows how to access help for the invoke datastores command. It also provides examples on how to deploy datastore resources.

pim invoke datastores --help
Usage: pim invoke datastores [OPTIONS] COMMAND [ARGS]...

  Commands for deploying datastore resources.

Options:
  --help  Show this message and exit.

Commands:
  deploy  Deploy policies and/or trusted applications to a specific datastore.

Invoke Datastores Types

The following commands show how to access help for the invoke datastores <type> command.

Invoke Datastores Deploy

The following command shows how to access help for the invoke datastores deploy command. It also provides examples on how to deploy policies or trusted applications or both to a specific datastore.

pim invoke datastores deploy --help
Usage: pim invoke datastores deploy [OPTIONS] DATASTORE_UID

  Deploy policies and/or trusted applications to a specific datastore.

  EXAMPLES:

  # Deploy single policy to datastore
  pim invoke datastores deploy 15 --policies 1

  # Deploy multiple policies to datastore
  pim invoke datastores deploy 15 --policies 1 --policies 2 --policies 3

  # Deploy trusted applications to datastore
  pim invoke datastores deploy 15 --applications 1 --applications 2

  # Deploy both policies and applications together
  pim invoke datastores deploy "<datastore-uid>" --policies 1 --policies 2 --applications 1 --applications 2

  # Clear all deployments (deploy empty configuration)
  pim invoke datastores deploy 42

  WORKFLOW:
  # Step 1: Verify datastore exists and is accessible
  pim get datastores datastore <datastore-uid>

  # Step 2: List available policies and applications
  pim get policies policy
  pim get applications application

  # Step 3: Deploy to  datastore
  pim invoke datastores deploy <datastore-uid> --policies <policy-uid> --applications <app-uid>

Options:
  --policies TEXT      UIDs of policies to deploy (can be specified multiple
                       times).
  --applications TEXT  UIDs of trusted applications to deploy (can be
                       specified multiple times).
  --help               Show this message and exit.

Invoke Init

The following command shows how to access help for the invoke init command. It also provides examples on how to initialize the Policy Information Management system.

pim invoke init --help
Usage: pim invoke init [OPTIONS]

  Bootstrap PIM - Initialize the Policy Information Management system.

  EXAMPLES:

  # Initialize PIM system for first-time setup
  pim invoke init

Options:
  --help  Show this message and exit.

Invoke Roles

The following command shows how to access help for the invoke roles command. It also provides examples on how to synchronize role resources.

pim invoke roles --help
Usage: pim invoke roles [OPTIONS] COMMAND [ARGS]...

  Commands for synchronizing role resources.

Options:
  --help  Show this message and exit.

Commands:
  sync  Synchronize all group members for a role with external identity sources.

Roles Types

The following commands show how to access help for the invoke roles <type> command.

Invoke Roles Sync

The following command shows how to access help for the invoke roles sync command. It also provides examples on how to synchronize all group members for a role.

pim invoke roles sync --help
Usage: pim invoke roles sync [OPTIONS] ROLE_UID

  Synchronize all group members for a role with external identity sources.

  EXAMPLES:

  # Synchronize role members with LDAP/AD source
  pim invoke roles sync 15

Options:
  --help  Show this message and exit.

Invoke Sources

The following command shows how to access help for the invoke sources command. It also provides examples on how to test source resources.

pim invoke sources --help
Usage: pim invoke sources [OPTIONS] COMMAND [ARGS]...

  Commands for testing source resources.

Options:
  --help  Show this message and exit.

Commands:
  test  Tests the connection and functionality of a source.

Invoke Sources Types

The following commands show how to access help for the invoke sources <type> command.

Invoke Sources Test

The following command shows how to access help for the invoke sources test command. It also provides examples on how to test the connection to a member source.

pim invoke sources test --help
Usage: pim invoke sources test [OPTIONS] UID

  Tests the connection and functionality of a source.

  EXAMPLES:

  # Basic connectivity test
  pim invoke sources test 15

Options:
  --help  Show this message and exit.

Create Commands

The following section lists the create commands.

Main Create Command

The following command shows how to access help for the create command.

pim create --help
Usage: pim create [OPTIONS] COMMAND [ARGS]...

  Create a resource.

Options:
  --help  Show this message and exit.

Commands:
  alphabets     Creates a new alphabet.
  applications  Creates a new application.
  dataelements  Creates a new data element of a specific type.
  datastores    Commands for creating datastore resources.
  deploy        Deploys policies and/or trusted applications to a datastore.
  masks         Creates a new mask with specified masking pattern and configuration.
  policies      Creates a new policy or rule.
  roles         Creates a new role or adds members to a role.
  sources       Creates a new source.

Create Alphabets

The following command shows how to access help for the create alphabets command. It also provides examples on how to create an alphabet.

pim create alphabets --help
Usage: pim create alphabets [OPTIONS]

  Creates a new alphabet.

  EXAMPLES:

  # Create alphabet combining existing alphabets (use numeric UIDs from 'pim get alphabets')
  pim create alphabets --label "LatinExtended" --alphabets "1,2"

  # Create alphabet with Unicode ranges (Basic Latin + punctuation)
  pim create alphabets --label "ASCIIPrintable" --ranges '[{"from": "0020", "to": "007E"}]'

  # Create alphabet with specific code points (more than 10 examples)
  pim create alphabets --label "SpecialChars" --code-points "00A9,00AE,2122,2603,2615,20AC,00A3,00A5,00B5,00B6,2020,2021,2030,2665,2660"

  # Create complex alphabet with multiple options (use numeric UIDs)
  pim create alphabets --label "CompleteSet" --alphabets "1,3,5"  --ranges '[{"from": "0100", "to": "017F"}, {"from": "1E00", "to": "1EFF"}]' --code-points "20AC,00A3,00A5"

  # Create mathematical symbols alphabet
  pim create alphabets --label "MathSymbols" --ranges '[{"from": "2200", "to": "22FF"}, {"from": "2190", "to": "21FF"}]'

Options:
  --label TEXT        The label for the custom alphabet.  [required]
  --alphabets TEXT    Comma-separated list of alphabet UIDs.
  --ranges TEXT       JSON string of code point ranges. For example, '[{"from":
                      "0020", "to": "007E"}]'.
  --code-points TEXT  Comma-separated list of code points.
  --help              Show this message and exit.

Create Applications

The following command shows how to access help for the create applications command. It also provides examples on how to create a trusted application.

pim create applications --help
Usage: pim create applications [OPTIONS]

  Creates a new application.

  EXAMPLES:

  # Create a basic application with required fields
  pim create applications --name "WebApp" --application-name "mywebapp" --application-user "webuser"

  # Create application with description
  pim create applications --name "DatabaseApp" --description "Main database application" --application-name "dbapp" --application-user "dbuser"

Options:
  --name TEXT              Name of the application.  [required]
  --description TEXT       Description of the application.
  --application-name TEXT  The application name or the application loading the
                           API jar file.  [required]
  --application-user TEXT  The application user or the OS user.  [required]
  --help                   Show this message and exit.

Create Dataelements

The following command shows how to access help for the create dataelements command. It also provides examples on how to create a data element.

pim create dataelements --help
Usage: pim create dataelements [OPTIONS] COMMAND [ARGS]...

  Creates a new data element of a specific type.

  AVAILABLE PROTECTION TYPES:

  # Encryption Methods:
  - aes128-cbc-enc       # AES-128 CBC encryption
  - aes128-cusp-enc      # AES-128 CUSP encryption  
  - aes256-cbc-enc       # AES-256 CBC encryption
  - aes256-cusp-enc      # AES-256 CUSP encryption
  - triple-des-cbc-enc   # 3DES CBC encryption
  - triple-des-cusp-enc  # 3DES CUSP encryption
  - sha1-hmac-enc        # SHA1 HMAC encryption (deprecated)
  - sha256-hmac-enc      # SHA256 HMAC encryption
  - no-enc               # No encryption (clear text)

  # Tokenization Methods:
  - token numeric        # Numeric tokens
  - token alphabetic     # Alphabetic tokens
  - token alpha-numeric  # Alphanumeric tokens
  - token printable      # Printable character tokens
  - token unicode        # Unicode tokens
  - token credit-card    # Credit card specific tokens
  - token email          # Email specific tokens

  # Format Preserving Encryption (FPE):
  - fpe numeric          # Numeric FPE
  - fpe alphabetic       # Alphabetic FPE
  - fpe alpha-numeric    # Alphanumeric FPE

  # Special Protection Types:
  - masking              # Data masking using NoEnc
  - monitor              # Data monitoring using NoEnc

Options:
  --help  Show this message and exit.

Commands:
  aes128-cbc-enc       Creates a new AES-128-CBC-ENC data element.
  aes128-cusp-enc      Creates a new AES-128-CUSP-ENC data element.
  aes256-cbc-enc       Creates a new AES-256-CBC-ENC data element.
  aes256-cusp-enc      Creates a new AES-256-CUSP-ENC data element.
  fpe                  Creates a new FPE (Format Preserving Encryption)...
  masking              Creates a new masking data element using NoEnc...
  monitor              Creates a new monitoring data element using NoEnc...
  no-enc               Creates a new No-Enc data element.
  sha1-hmac-enc        Creates a new SHA1-HMAC-ENC data element...
  sha256-hmac-enc      Creates a new SHA256-HMAC-ENC data element.
  token                Creates a new token data element of a specific type.
  triple-des-cbc-enc   Creates a new 3DES-CBC-ENC data element.
  triple-des-cusp-enc  Creates a new 3DES-CUSP-ENC data element.

Create Dataelements Types

The following commands show how to access help for the create dataelements <type> command. It also provides examples on how to create a data element of a specific type.

Create Dataelements aes128 cbc enc

The following command shows how to access help for the create dataelements aes128-cbc-enc command. It also provides examples on how to create a AES-128-CBC-ENC data element.

pim create dataelements aes128-cbc-enc --help
Usage: pim create dataelements aes128-cbc-enc [OPTIONS]

  Creates a new AES-128-CBC-ENC data element.

  EXAMPLES:

  # Create basic AES-128 encryption data element
  pim create dataelements aes128-cbc-enc --name "BasicEncryption" --description "Basic data encryption"

  # Create with all security features enabled
  pim create dataelements aes128-cbc-enc --name "FullSecurityEnc" --description "Full security encryption" --iv-type "SYSTEM_APPEND" --checksum-type "CRC32" --cipher-format "INSERT_KEYID_V1"

Options:
  --name TEXT                               The name for the data element.  [required]
  --description TEXT                        An optional description for the data element.
  --iv-type [NONE|SYSTEM_APPEND]            Initialization Vector type.
  --checksum-type [NONE|CRC32]              Checksum type.
  --cipher-format [NONE|INSERT_KEYID_V1]    Cipher format.
  --help                                    Show this message and exit.
Create Dataelements aes128 cusp enc

The following command shows how to access help for the create dataelements aes128-cusp-enc command. It also provides examples on how to create a AES-128-CUSP-ENC data element.

pim create dataelements aes128-cusp-enc --help
Usage: pim create dataelements aes128-cusp-enc [OPTIONS]

  Creates a new AES-128-CUSP-ENC data element.      EXAMPLES:

  # Create with key rotation support
  pim create dataelements aes128-cusp-enc --name "RotatingCUSP" --description "CUSP with key rotation" --cipher-format "INSERT_KEYID_V1"

Options:
  --name TEXT                               The name for the data element.  [required]
  --description TEXT                        An optional description for the data element.
  --iv-type [NONE|SYSTEM_APPEND]            Initialization Vector type.
  --checksum-type [NONE|CRC32]              Checksum type.
  --cipher-format [NONE|INSERT_KEYID_V1]    Cipher format.
  --help                                    Show this message and exit.
Create Dataelements aes256 cbc enc

The following command shows how to access help for the create dataelements aes256-cbc-enc command. It also provides examples on how to create a AES-256-CBC-ENC data element.

pim create dataelements aes256-cbc-enc --help
Usage: pim create dataelements aes256-cbc-enc [OPTIONS]

  Creates a new AES-256-CBC-ENC data element.

  EXAMPLES:

  # Create with system-generated IV and CRC32 checksum
  pim create dataelements aes256-cbc-enc --name "CreditCardEnc" --description "Credit card encryption" --iv-type "SYSTEM_APPEND" --checksum-type "CRC32"    

Options:
  --name TEXT                               The name for the data element.  [required]
  --description TEXT                        An optional description for the data element.
  --iv-type [NONE|SYSTEM_APPEND]            Initialization Vector type.
  --checksum-type [NONE|CRC32]              Checksum type.
  --cipher-format [NONE|INSERT_KEYID_V1]    Cipher format.
  --help                                    Show this message and exit.
Create Dataelements aes256 cusp enc

The following command shows how to access help for the create dataelements aes256-cusp-enc command. It also provides examples on how to create a AES-256-CUSP-ENC data element.

pim create dataelements aes256-cusp-enc --help
Usage: pim create dataelements aes256-cusp-enc [OPTIONS]

  Creates a new AES-256-CUSP-ENC data element.

  EXAMPLES:

  # Create basic AES-256 CUSP encryption
  pim create dataelements aes256-cusp-enc --name "HighSecurityEnc" --description "High security data encryption"

  # Create with key ID insertion for key management
  pim create dataelements aes256-cusp-enc --name "EnterpriseEnc" --description "Enterprise encryption with key tracking" --cipher-format "INSERT_KEYID_V1"

Options:
  --name TEXT                               The name for the data element.  [required]
  --description TEXT                        An optional description for the data element.
  --iv-type [NONE|SYSTEM_APPEND]            Initialization Vector type.
  --checksum-type [NONE|CRC32]              Checksum type.
  --cipher-format [NONE|INSERT_KEYID_V1]    Cipher format.
  --help                                    Show this message and exit.
Create Dataelements triple des cbc enc

The following command shows how to access help for the create dataelements triple-des-cbc-enc command. It also provides examples on how to create a 3DES-CBC-ENC data element.

pim create dataelements triple-des-cbc-enc --help
Usage: pim create dataelements triple-des-cbc-enc [OPTIONS]

  Creates a new 3DES-CBC-ENC data element.

  EXAMPLES:

  # Create basic 3DES-CBC encryption
  pim create dataelements triple-des-cbc-enc --name "Legacy3DESEnc" --description "Legacy 3DES encryption for compatibility"

  # Create with key ID insertion for key management
  pim create dataelements triple-des-cbc-enc --name "Managed3DES" --description "3DES with key tracking" --cipher-format "INSERT_KEYID_V1"

Options:
  --name TEXT                     The name for the data element.  [required]
  --description TEXT              An optional description for the data
                                  element.
  --iv-type [NONE|SYSTEM_APPEND]  Initialization Vector type.
  --checksum-type [NONE|CRC32]    Checksum type.
  --cipher-format [NONE|INSERT_KEYID_V1]
                                  Cipher format.
  --help                          Show this message and exit.
Create Dataelements triple des cusp enc

The following command shows how to access help for the create dataelements triple-des-cusp-enc command. It also provides examples on how to create a 3DES-CUSP-ENC data element.

pim create dataelements triple-des-cusp-enc --help
Usage: pim create dataelements triple-des-cusp-enc [OPTIONS]

  Creates a new 3DES-CUSP-ENC data element.

  EXAMPLES:

  # Create with system-generated IV and integrity checking
  pim create dataelements triple-des-cusp-enc --name "Secure3DESCusp" --description "3DES CUSP with enhanced security" --iv-type "SYSTEM_APPEND" --checksum-type "CRC32"

Options:
  --name TEXT                     The name for the data element.  [required]
  --description TEXT              An optional description for the data
                                  element.
  --iv-type [NONE|SYSTEM_APPEND]  Initialization Vector type.
  --checksum-type [NONE|CRC32]    Checksum type.
  --cipher-format [NONE|INSERT_KEYID_V1]
                                  Cipher format.
  --help                          Show this message and exit.
Create Dataelements fpe

The following command shows how to access help for the create dataelements fpe command. It also provides examples on how to create a Format Preserving Encryption (FPE) data element.

pim create dataelements fpe --help
Usage: pim create dataelements fpe [OPTIONS] COMMAND [ARGS]...

  Creates a new FPE (Format Preserving Encryption) data element of a specific
  type.

  AVAILABLE FPE TYPES:

  - numeric                           # Numeric data (0-9)
  - alphabetic                        # Alphabetic data (a-z, A-Z)  
  - alpha-numeric                     # Alphanumeric data (0-9, a-z, A-Z)
  - unicode-basic-latin-alphabetic    # Unicode Basic Latin alphabetic
  - unicode-basic-latin-alpha-numeric # Unicode Basic Latin alphanumeric

Options:
  --help  Show this message and exit.

Commands:
  alpha-numeric                        Creates a new Alpha Numeric FPE data element.
  alphabetic                           Creates a new Alphabetic FPE data element.
  numeric                              Creates a new Numeric FPE data element.
  unicode-basic-latin-alpha-numeric    Creates a new Unicode Basic Latin Alpha Numeric (Format Preserving Encryption) FPE data element.
  unicode-basic-latin-alphabetic       Creates a new Unicode Basic Latin Alphabetic FPE data element.
Create Dataelements fpe alpha numeric

The following command shows how to access help for the create dataelements fpe alpha numeric command. It also provides examples on how to create an alpha numeric (FPE) data element.

pim create dataelements fpe alpha-numeric --help
Usage: pim create dataelements fpe alpha-numeric [OPTIONS]

  Creates a new Alpha Numeric FPE data element.

  EXAMPLES:

  # Create basic alphanumeric FPE for user IDs
  pim create dataelements fpe alpha-numeric --name "UserIDFPE" --description "User ID alphanumeric format-preserving encryption"

  # Create for product codes with flexible length handling
  pim create dataelements fpe alpha-numeric --name "ProductCodeFPE" --description "Product code alphanumeric FPE" --from-left 2 --min-length 5 --allow-short "NOINPUTVALUE"

  # Create for mixed case identifiers
  pim create dataelements fpe alpha-numeric --name "MixedCaseIDFPE" --description "Mixed case identifier encryption"  --from-left 1 --from-right 2 --min-length 7

Options:
  --name TEXT                     The name for the data element.  [required]
  --description TEXT              An optional description for the data
                                  element.
  --plain-text-encoding TEXT      Kept for backwards compatibility, will be
                                  ignored if sent in. Removed in later
                                  releases.
  --from-left INTEGER             Number of characters to retain in clear from
                                  the left.
  --from-right INTEGER            Number of characters to retain in clear from
                                  the right.
  --min-length INTEGER            The minimum supported input length is 2
                                  bytes and is configurable up to 10 bytes.
  --tweak-mode [EXT_API|EXT_INPUT]
                                  The tweak input is derived from either the
                                  API (EXT_API) or the input message
                                  (EXT_INPUT).
  --allow-short [NOWITHERROR|NOINPUTVALUE]
                                  Specifies whether the short data must be
                                  supported or not.
  --help                          Show this message and exit.
Create Dataelements fpe alphabetic

The following command shows how to access help for the create dataelements fpe alphabetic command. It also provides examples on how to create an alphabetic (FPE) data element.

pim create dataelements fpe alphabetic --help
Usage: pim create dataelements fpe alphabetic [OPTIONS]

  Creates a new Alphabetic FPE data element.

  EXAMPLES:

  # Create with partial clear text (preserve first 2 and last 2 chars)
  pim create dataelements fpe alphabetic --name "PartialAlphaFPE" --description "Partial alphabetic FPE with clear boundaries" --from-left 2 --from-right 2

Options:
  --name TEXT                     The name for the data element.  [required]
  --description TEXT              An optional description for the data
                                  element.
  --plain-text-encoding TEXT      Kept for backwards compatibility, will be
                                  ignored if sent in. Removed in later
                                  releases.
  --from-left INTEGER             Number of characters to retain in clear from
                                  the left.
  --from-right INTEGER            Number of characters to retain in clear from
                                  the right.
  --min-length INTEGER            The minimum supported input length is 2
                                  bytes and is configurable up to 10 bytes.
  --allow-short [NOWITHERROR|NOINPUTVALUE]
                                  Specifies whether the short data must be
                                  supported or not.
  --tweak-mode [EXT_API|EXT_INPUT]
                                  The tweak input is derived from either the
                                  API (EXT_API) or the input message
                                  (EXT_INPUT).
  --help                          Show this message and exit.
Create Dataelements fpe numeric

The following command shows how to access help for the create dataelements fpe numeric command. It also provides examples on how to create a numeric (FPE) data element.

pim create dataelements fpe numeric --help
Usage: pim create dataelements fpe numeric [OPTIONS]

  Creates a new Numeric FPE data element.

  EXAMPLES:

  # Create basic numeric FPE for account numbers
  pim create dataelements fpe numeric --name "AccountFPE" --description "Account number format-preserving encryption" --min-length 6

  # Create FPE with partial masking (show first 4 digits)
  pim create dataelements fpe numeric --name "PartialFPE" --description "Partial numeric FPE" --min-length 8 --from-left 4

  # Create credit card FPE with BIN preservation
  pim create dataelements fpe numeric --name "CreditCardFPE" --description "Credit card FPE with BIN visible" --min-length 8 --from-left 6 --from-right 4 --special-numeric-handling "CCN"

Options:
  --name TEXT                     The name for the data element.  [required]
  --description TEXT              An optional description for the data
                                  element.
  --plain-text-encoding TEXT      Kept for backwards compatibility, will be
                                  ignored if sent in. Removed in later
                                  releases.
  --from-left INTEGER             Number of characters to retain in clear from
                                  the left.
  --from-right INTEGER            Number of characters to retain in clear from
                                  the right.
  --min-length INTEGER            The minimum supported input length is 2
                                  bytes and is configurable up to 10 bytes.
                                  The default minimum supported input length
                                  for Credit Card Number (CCN) is 8 bytes and
                                  is configurable up to 10 bytes.
  --tweak-mode [EXT_API|EXT_INPUT]
                                  The tweak input is derived from either the
                                  API (EXT_API) or the input message
                                  (EXT_INPUT).
  --allow-short [NOWITHERROR|NOINPUTVALUE]
                                  Specifies whether the short data must be
                                  supported or not.
  --special-numeric-handling [NONE|CCN]
                                  The Format Preserving Encryption (FPE) for
                                  Credit Card Number (CCN) is handled by
                                  configuring numeric data type as the
                                  plaintext alphabet.
  --help                          Show this message and exit.
Create Dataelements fpe unicode basic latin alpha numeric

The following command shows how to access help for the create dataelements fpe unicode-basic-latin-alpha-numeric command. It also provides examples on how to create a unicode basic latin alpha numeric (FPE) data element.

pim create dataelements fpe unicode-basic-latin-alpha-numeric --help
Usage: pim create dataelements fpe unicode-basic-latin-alpha-numeric 
           [OPTIONS]

  Creates a new Unicode Basic Latin Alpha Numeric (Format Preserving
  Encryption) FPE data element.

  EXAMPLES:

  # Create basic Unicode Latin alphanumeric FPE
  pim create dataelements fpe unicode-basic-latin-alpha-numeric --name "UnicodeLatinFPE"  --description "Unicode Latin alphanumeric format-preserving encryption"

  # Create with partial clear text for international IDs
  pim create dataelements fpe unicode-basic-latin-alpha-numeric --name "IntlIDFPE" --description "International ID with clear prefix,suffix" --from-left 2 --from-right 2 --min-length 6

  # Create for international user IDs with flexible length
  pim create dataelements fpe unicode-basic-latin-alpha-numeric --name "GlobalUserIDFPE" --description "Global user ID format-preserving encryption" --min-length 4 --allow-short "NOINPUTVALUE"

Options:
  --name TEXT                     The name for the data element.  [required]
  --description TEXT              An optional description for the data
                                  element.
  --plain-text-encoding TEXT      Kept for backwards compatibility, will be
                                  ignored if sent in. Removed in later
                                  releases.
  --from-left INTEGER             Number of characters to retain in clear from
                                  the left.
  --from-right INTEGER            Number of characters to retain in clear from
                                  the right.
  --min-length INTEGER            The minimum supported input length is 2
                                  bytes and is configurable up to 10 bytes.
  --tweak-mode [EXT_API|EXT_INPUT]
                                  The tweak input is derived from either the
                                  API (EXT_API) or the input message
                                  (EXT_INPUT).
  --allow-short [NOWITHERROR|NOINPUTVALUE]
                                  Specifies whether the short data must be
                                  supported or not.
  --help                          Show this message and exit.
Create Dataelements fpe unicode basic latin alpha alphabetic

The following command shows how to access help for the create dataelements fpe unicode-basic-latin-alphabetic command. It also provides examples on how to create a unicode basic latin alphabetic (FPE) data element.

pim create dataelements fpe unicode-basic-latin-alphabetic --help
Usage: pim create dataelements fpe unicode-basic-latin-alphabetic 
           [OPTIONS]

  Creates a new Unicode Basic Latin Alphabetic FPE data element.

  EXAMPLES:

  # Create basic Unicode Basic Latin alphabetic FPE
  pim create dataelements fpe unicode-basic-latin-alphabetic --name "UnicodeAlphaFPE"  --description "Unicode Basic Latin alphabetic FPE"

  # Create for European customer names
  pim create dataelements fpe unicode-basic-latin-alphabetic --name "EuropeanNameFPE" --description "European customer name FPE" --from-left 1 --min-length 3 --allow-short "NOWITHERROR"

Options:
  --name TEXT                     The name for the data element.  [required]
  --description TEXT              An optional description for the data
                                  element.
  --plain-text-encoding TEXT      Kept for backwards compatibility, will be
                                  ignored if sent in. Removed in later
                                  releases.
  --from-left INTEGER             Number of characters to retain in clear from
                                  the left.
  --from-right INTEGER            Number of characters to retain in clear from
                                  the right.
  --min-length INTEGER            The minimum supported input length is 2
                                  bytes and is configurable up to 10 bytes.
  --tweak-mode [EXT_API|EXT_INPUT]
                                  The tweak input is derived from either the
                                  API (EXT_API) or the input message
                                  (EXT_INPUT).
  --allow-short [NOWITHERROR|NOINPUTVALUE]
                                  Specifies whether the short data must be
                                  supported or not.
  --help                          Show this message and exit.
Create Dataelements masking

The following command shows how to access help for the create dataelements masking command. It also provides examples on how to create a masking data element using no encryption with masking enabled.

pim create dataelements masking --help
Usage: pim create dataelements masking [OPTIONS]

  Creates a new masking data element using NoEnc with masking enabled.

  EXAMPLES:

  # Create basic data masking with a specific mask
  pim create dataelements masking --name "SSNMasking" --description "Social Security Number masking"  --mask-uid "1"

  # Create email masking for development environment
  pim create dataelements masking --name "EmailMasking" --description "Email masking for dev environment" --mask-uid "2"

Options:
  --name TEXT         The name for the data element.  [required]
  --description TEXT  An optional description for the data element.
  --mask-uid TEXT     The UID of the mask to apply for masking data.
                      [required]
  --help              Show this message and exit.
Create Dataelements monitor

The following command shows how to access help for the create dataelements monitor command. It also provides examples on how to create a monitoring data element using NoEnc with monitoring enabled.

pim create dataelements monitor --help
Usage: pim create dataelements monitor [OPTIONS]

  Creates a new monitoring data element using no encryption with monitoring enabled.

  EXAMPLES:

  # Create basic monitoring for sensitive database fields
  pim create dataelements monitor --name "CustomerDataMonitor"  --description "Monitor customer data access"

Options:
  --name TEXT         The name for the data element.  [required]
  --description TEXT  An optional description for the data element.
  --help              Show this message and exit.
Create Dataelements no enc

The following command shows how to access help for the create dataelements no-enc command. It also provides examples on how to create a no encryption data element.

pim create dataelements no-enc --help
Usage: pim create dataelements no-enc [OPTIONS]

  Creates a new No-Enc data element.

  EXAMPLES:

  # Create basic no-encryption element for testing
  pim create dataelements no-enc --name "TestNoEnc" --description "Test data element with no encryption"

Options:
  --name TEXT         The name for the data element.  [required]
  --description TEXT  An optional description for the data element.
  --help              Show this message and exit.
Create Dataelements sha1 hmac enc

The following command shows how to access help for the create dataelements sha1-hmac-enc command. It also provides examples on how to create a SHA1-HMAC-ENC data element.

Note: The SHA1-HMAC-ENC data element is deprecated.

pim create dataelements sha1-hmac-enc --help
Usage: pim create dataelements sha1-hmac-enc [OPTIONS]

  Creates a new SHA1-HMAC-ENC data element (deprecated).

  EXAMPLES:

  # Create basic SHA1-HMAC encryption (legacy support)
  pim create dataelements sha1-hmac-enc --name "LegacyHashEnc" --description "SHA1 HMAC for legacy system compatibility"

Options:
  --name TEXT         The name for the data element.  [required]
  --description TEXT  An optional description for the data element.
  --help              Show this message and exit.
Create Dataelements sha256 hmac enc

The following command shows how to access help for the create dataelements sha256-hmac-enc command. It also provides examples on how to create a SHA256-HMAC-ENC data element.

pim create dataelements sha256-hmac-enc --help
Usage: pim create dataelements sha256-hmac-enc [OPTIONS]

  Creates a new SHA256-HMAC-ENC data element.

  EXAMPLES:

  # Create basic SHA256-HMAC encryption
  pim create dataelements sha256-hmac-enc --name "SecureHashEnc" --description "Strong SHA256 HMAC encryption"

Options:
  --name TEXT         The name for the data element.  [required]
  --description TEXT  An optional description for the data element.
  --help              Show this message and exit.
Create Dataelements token

The following command shows how to access help for the create dataelements token command. It also provides examples on how to create a token data element.

pim create dataelements token --help
Usage: pim create dataelements token [OPTIONS] COMMAND [ARGS]...

  Creates a new token data element of a specific type.

  AVAILABLE TOKEN TYPES:

  - numeric              # Numeric data tokenization (0-9)
  - alphabetic           # Alphabetic data tokenization (a-z, A-Z)
  - alpha-numeric        # Alphanumeric tokenization (0-9, a-z, A-Z)
  - printable            # Printable ASCII characters
  - unicode              # Unicode character tokenization
  - unicode-base64       # Base64 encoded Unicode tokens
  - unicode-gen2         # Generation 2 Unicode tokens with custom alphabets
  - binary               # Binary data tokenization
  - lower-ascii          # Lowercase ASCII tokenization
  - upper-alphabetic     # Uppercase alphabetic tokens
  - upper-alpha-numeric  # Uppercase alphanumeric tokens

  # Specialized Token Types:
  - credit-card          # Credit card number tokenization
  - email                # Email address tokenization
  - integer              # Integer value tokenization
  - decimal              # Decimal number tokenization
  - date-yyyymmdd        # Date in YYYY-MM-DD format
  - date-ddmmyyyy        # Date in DD-MM-YYYY format
  - date-mmddyyyy        # Date in MM-DD-YYYY format
  - date-time            # Date and time tokenization

  COMMON OPTIONS:

  --tokenizer            # Lookup table type (SLT_1_3, SLT_2_3, SLT_1_6, SLT_2_6)
  --from-left            # Characters to keep in clear from left
  --from-right           # Characters to keep in clear from right
  --length-preserving    # Maintain original data length
  --allow-short          # Handle short input data (YES, NO, ERROR)

Options:
  --help  Show this message and exit.

Commands:
  alpha-numeric        Creates a new Alpha Numeric Token data element.
  alphabetic           Creates a new Alphabetic Token data element.
  binary               Creates a new Binary Token data element.
  credit-card          Creates a new Credit Card Token data element.
  date-ddmmyyyy        Creates a new Date DDMMYYYY Token data element.
  date-mmddyyyy        Creates a new Date MMDDYYYY Token data element.
  date-time            Creates a new Date Time Token data element.
  date-yyyymmdd        Creates a new Date YYYYMMDD Token data element.
  decimal              Creates a new Decimal Token data element.
  email                Creates a new Email Token data element.
  integer              Creates a new Integer Token data element.
  lower-ascii          Creates a new Lower ASCII Token data element.
  numeric              Creates a new Numeric Token data element.
  printable            Creates a new Printable Token data element.
  unicode              Creates a new Unicode Token data element.
  unicode-base64       Creates a new Unicode Base64 Token data element.
  unicode-gen2         Creates a new Unicode Gen2 Token data element.
  upper-alpha-numeric  Creates a new Upper Alpha Numeric Token data element.
  upper-alphabetic     Creates a new Upper Alphabetic Token data element.
Create Dataelements token alpha numeric

The following command shows how to access help for the create dataelements token alpa-numeric command. It also provides examples on how to create an alpha-numeric token data element.

pim create dataelements token alpha-numeric --help
Usage: pim create dataelements token alpha-numeric [OPTIONS]

  Creates a new Alpha Numeric Token data element.

  EXAMPLES:     # Create for reference codes pim create dataelements token
  alpha-numeric --name "RefCodeToken" --description "Reference code
  alphanumeric tokenization" --tokenizer "SLT_1_3" --from-left 2 --allow-short
  NOWITHERROR

Options:
  --name TEXT                     The name for the data element.  [required]
  --description TEXT              An optional description for the data
                                  element.
  --tokenizer [SLT_1_3|SLT_2_3|SLT_1_6|SLT_2_6]
                                  The lookup tables to be generated.
                                  [required]
  --from-left INTEGER             Number of characters to keep in clear from
                                  the left.
  --from-right INTEGER            Number of characters to keep in clear from
                                  the right.
  --length-preserving             Specifies whether the output must be of the
                                  same length as the input.
  --allow-short [YES|NOINPUTVALUE|NOWITHERROR]
                                  Allow short tokens.
  --help                          Show this message and exit.
Create Dataelements token alphabetic

The following command shows how to access help for the create dataelements token alpabetic command. It also provides examples on how to create an alphabetic token data element.

pim create dataelements token alphabetic --help
Usage: pim create dataelements token alphabetic [OPTIONS]

  Creates a new Alphabetic Token data element.

  EXAMPLES:

  # Create length-preserving alphabetic token
  pim create dataelements token alphabetic --name "ExactLengthAlpha" --description "Length-preserving alphabetic token" --tokenizer "SLT_2_3" --length-preserving

  # Create for name tokenization with short value support
  pim create dataelements token alphabetic --name "NameToken" --description "Name tokenization with short support" --tokenizer "SLT_2_3" --allow-short YES --length-preserving

Options:
  --name TEXT                     The name for the data element.  [required]
  --description TEXT              An optional description for the data
                                  element.
  --tokenizer [SLT_1_3|SLT_2_3]   The lookup tables to be generated.
                                  [required]
  --from-left INTEGER             Number of characters to keep in clear from
                                  the left.
  --from-right INTEGER            Number of characters to keep in clear from
                                  the right.
  --length-preserving             Specifies whether the output must be of the
                                  same length as the input.
  --allow-short [YES|NOINPUTVALUE|NOWITHERROR]
                                  Allow short tokens.
  --help                          Show this message and exit.
Create Dataelements token binary

The following command shows how to access help for the create dataelements token binary command. It also provides examples on how to create a binary token data element.

pim create dataelements token binary --help
Usage: pim create dataelements token binary [OPTIONS]

  Creates a new Binary Token data element.

  EXAMPLES:

  # Create basic binary tokenization
  pim create dataelements token binary --name "BinaryToken" --description "Binary data tokenization" --tokenizer "SLT_1_3"

Options:
  --name TEXT                    The name for the data element.  [required]
  --description TEXT             An optional description for the data element.
  --tokenizer [SLT_1_3|SLT_2_3]  The lookup tables to be generated.
                                 [required]
  --from-left INTEGER            Number of characters to keep in clear from
                                 the left.
  --from-right INTEGER           Number of characters to keep in clear from
                                 the right.
  --help                         Show this message and exit.
Create Dataelements token credit card

The following command shows how to access help for the create dataelements token credit-card command. It also provides examples on how to create a credit card token data element.

pim create dataelements token credit-card --help
Usage: pim create dataelements token credit-card [OPTIONS]

  Creates a new Credit Card Token data element.

  EXAMPLES:

  # Create basic credit card tokenization
  pim create dataelements token credit-card --name "CCTokenBasic" --description "Basic credit card tokenization" --tokenizer "SLT_1_6"

Options:
  --name TEXT                     The name for the data element.  [required]
  --description TEXT              An optional description for the data
                                  element.
  --tokenizer [SLT_1_3|SLT_2_3|SLT_1_6|SLT_2_6]
                                  The lookup tables to be generated.
                                  [required]
  --from-left INTEGER             Number of characters to keep in clear from
                                  the left.
  --from-right INTEGER            Number of characters to keep in clear from
                                  the right.
  --invalid-card-type             Token values will not begin with digits that
                                  real credit card numbers begin with.
  --invalid-luhn-digit            Validate Luhn checksum (requires valid
                                  credit cards as input).
  --alphabetic-indicator          Include one alphabetic character in the
                                  token.
  --alphabetic-indicator-position INTEGER
                                  Position for the alphabetic indicator
                                  (required when alphabetic-indicator is
                                  enabled).
  --help                          Show this message and exit.
Create Dataelements token date ddmmyyyy

The following command shows how to access help for the create dataelements token date-ddmmyyyy command. It also provides examples on how to create a DDMMYYYY date token data element.

pim create dataelements token date-ddmmyyyy --help
Usage: pim create dataelements token date-ddmmyyyy [OPTIONS]

  Creates a new Date DDMMYYYY Token data element.

  EXAMPLES:

  # Create basic DDMMYYYY date tokenization
  pim create dataelements token date-ddmmyyyy --name "DateDDMMYYYY" --description "European date format DD-MM-YYYY tokenization" --tokenizer "SLT_1_3"

  # Create for compliance reporting dates
  pim create dataelements token date-ddmmyyyy --name "ComplianceDate" --description "Compliance reporting DD-MM-YYYY dates" --tokenizer "SLT_2_3"

Options:
  --name TEXT                     The name for the data element.  [required]
  --description TEXT              An optional description for the data
                                  element.
  --tokenizer [SLT_1_3|SLT_2_3|SLT_1_6|SLT_2_6]
                                  The lookup tables to be generated.
                                  [required]
  --help                          Show this message and exit.
Create Dataelements token date mmddyyyy

The following command shows how to access help for the create dataelements token date-mmddyyyy command. It also provides examples on how to create a MMDDYYYY date token data element.

pim create dataelements token date-mmddyyyy --help
Usage: pim create dataelements token date-mmddyyyy [OPTIONS]

  Creates a new Date MMDDYYYY Token data element.

  EXAMPLES:

  # Create for financial reporting dates
  pim create dataelements token date-mmddyyyy --name "FinancialReportDate" --description "Financial reporting MM-DD-YYYY format" --tokenizer "SLT_2_3"

Options:
  --name TEXT                     The name for the data element.  [required]
  --description TEXT              An optional description for the data
                                  element.
  --tokenizer [SLT_1_3|SLT_2_3|SLT_1_6|SLT_2_6]
                                  The lookup tables to be generated.
                                  [required]
  --help                          Show this message and exit.
Create Dataelements token date time

The following command shows how to access help for the create dataelements token date-time command. It also provides examples on how to create a date-time token data element.

pim create dataelements token date-time --help
Usage: pim create dataelements token date-time [OPTIONS]

  Creates a new Date Time Token data element.

  EXAMPLES:

  # Create basic date-time tokenization
  pim create dataelements token date-time --name "DateTimeToken" --description "Basic date-time tokenization" --tokenizer "SLT_8_DATETIME"

Options:
  --name TEXT                     The name for the data element.  [required]
  --description TEXT              An optional description for the data
                                  element.
  --tokenizer [SLT_8_DATETIME]    The lookup tables to be generated.
                                  [required]
  --tokenize-time                 Whether to tokenize time (HH:MM:SS).
  --distinguishable-date          Whether date tokens should be
                                  distinguishable from real dates.
  --date-in-clear [NONE|YEAR|MONTH]
                                  Which date parts to keep in clear.
  --help                          Show this message and exit.
Create Dataelements token date yyyymmdd

The following command shows how to access help for the create dataelements token date-yyyymmdd command. It also provides examples on how to create a YYYYMMDD date token data element.

pim create dataelements token date-yyyymmdd --help
Usage: pim create dataelements token date-yyyymmdd [OPTIONS]

  Creates a new Date YYYYMMDD Token data element.

  EXAMPLES:

  # Create basic YYYYMMDD date tokenization
  pim create dataelements token date-yyyymmdd --name "DateYYYYMMDD" --description "Date tokenization in YYYY-MM-DD format" --tokenizer "SLT_1_3"

  # Create for event date tracking
  pim create dataelements token date-yyyymmdd --name "EventDateToken" --description "Event date in YYYY-MM-DD format" --tokenizer "SLT_2_3"

Options:
  --name TEXT                     The name for the data element.  [required]
  --description TEXT              An optional description for the data
                                  element.
  --tokenizer [SLT_1_3|SLT_2_3|SLT_1_6|SLT_2_6]
                                  The lookup tables to be generated.
                                  [required]
  --help                          Show this message and exit.
Create Dataelements token decimal

The following command shows how to access help for the create dataelements token decimal command. It also provides examples on how to create a decimal token data element.

pim create dataelements token decimal --help
Usage: pim create dataelements token decimal [OPTIONS]

  Creates a new Decimal Token data element.

  EXAMPLES:

  # Create basic decimal tokenization for amounts
  pim create dataelements token decimal --name "DecimalToken" --description "Financial decimal amount tokenization" --tokenizer "SLT_6_DECIMAL" --max-length 15

Options:
  --name TEXT                  The name for the data element.  [required]
  --description TEXT           An optional description for the data element.
  --tokenizer [SLT_6_DECIMAL]  The lookup tables to be generated.  [required]
  --min-length INTEGER         Minimum length of the token element that can be
                               protected.
  --max-length INTEGER         Maximum length of the token element that can be
                               protected (max 38).  [required]
  --help                       Show this message and exit.
Create Dataelements token email

The following command shows how to access help for the create dataelements token email command. It also provides examples on how to create a email token data element.

pim create dataelements token email --help
Usage: pim create dataelements token email [OPTIONS]

  Creates a new Email Token data element.

  EXAMPLES:

  # Create basic email tokenization
  pim create dataelements token email --name "EmailTokenBasic" --description "Basic email tokenization" --tokenizer "SLT_1_3"  --allow-short NOWITHERROR

  # Create email tokenization with error on short input
  pim create dataelements token email --name "EmailTokenError" --description "Email tokenization with short input errors" --tokenizer "SLT_1_3" --length-preserving  --allow-short NOWITHERROR

Options:
  --name TEXT                     The name for the data element.  [required]
  --description TEXT              An optional description for the data
                                  element.
  --tokenizer [SLT_1_3|SLT_2_3]   The lookup tables to be generated.
                                  [required]
  --length-preserving             Specifies whether the output must be of the
                                  same length as the input.
  --allow-short [YES|NOINPUTVALUE|NOWITHERROR]
                                  Allow short tokens.
  --help                          Show this message and exit.
Create Dataelements token integer

The following command shows how to access help for the create dataelements token integer command. It also provides examples on how to create a integer token data element.

pim create dataelements token integer --help
Usage: pim create dataelements token integer [OPTIONS]

  Creates a new Integer Token data element.

  EXAMPLES:

  # Create basic integer tokenization (default 4-byte)
  pim create dataelements token integer --name "IntegerToken" --description "Basic integer tokenization" --tokenizer "SLT_1_3"

  # Create short integer tokenization for small numbers
  pim create dataelements token integer --name "ShortIntegerToken" --description "Short integer (2-byte) tokenization" --tokenizer "SLT_1_3" --integer-size "SHORT"

Options:
  --name TEXT                     The name for the data element.  [required]
  --description TEXT              An optional description for the data
                                  element.
  --tokenizer [SLT_1_3]           The lookup tables to be generated.
                                  [required]
  --integer-size [SHORT|INT|LONG]
                                  Integer size: 2 bytes (SHORT), 4 bytes
                                  (INT), or 8 bytes (LONG).
  --help                          Show this message and exit.
Create Dataelements token lower ascii

The following command shows how to access help for the create dataelements token lower-ascii command. It also provides examples on how to create a lower-ascii token data element.

pim create dataelements token lower-ascii --help
Usage: pim create dataelements token lower-ascii [OPTIONS]

  Creates a new Lower ASCII Token data element.

  EXAMPLES:

  # Create strict ASCII tokenization (error on short input)
  pim create dataelements token lower-ascii --name "StrictAsciiToken" --description "Strict ASCII tokenization" --tokenizer "SLT_1_3" --allow-short "NOWITHERROR"

Options:
  --name TEXT                     The name for the data element.  [required]
  --description TEXT              An optional description for the data
                                  element.
  --tokenizer [SLT_1_3]           The lookup tables to be generated.
                                  [required]
  --from-left INTEGER             Number of characters to keep in clear from
                                  the left.
  --from-right INTEGER            Number of characters to keep in clear from
                                  the right.
  --length-preserving             Specifies whether the output must be of the
                                  same length as the input.
  --allow-short [YES|NOINPUTVALUE|NOWITHERROR]
                                  Allow short tokens.
  --help                          Show this message and exit.
Create Dataelements token numeric

The following command shows how to access help for the create dataelements token numeric command. It also provides examples on how to create a numeric token data element.

pim create dataelements token numeric --help
Usage: pim create dataelements token numeric [OPTIONS]

  Creates a new Numeric Token data element.

  EXAMPLES:

  # Create basic numeric token for SSN
  pim create dataelements token numeric --name "SSNToken" --description "Social Security Number tokenization" --tokenizer "SLT_1_6" --length-preserving

  # Create high-security token for financial data
  pim create dataelements token numeric --name "FinancialToken" --description "Financial account tokenization" --tokenizer "SLT_2_6" --length-preserving --allow-short "NOWITHERROR"

Options:
  --name TEXT                     The name for the data element.  [required]
  --description TEXT              An optional description for the data
                                  element.
  --tokenizer [SLT_1_3|SLT_2_3|SLT_1_6|SLT_2_6]
                                  The lookup tables to be generated.
                                  [required]
  --from-left INTEGER             Number of characters to keep in clear from
                                  the left.
  --from-right INTEGER            Number of characters to keep in clear from
                                  the right.
  --length-preserving             Specifies whether the output must be of the
                                  same length as the input.
  --allow-short [YES|NOINPUTVALUE|NOWITHERROR]
                                  Allow short tokens.
  --help                          Show this message and exit.
Create Dataelements token printable

The following command shows how to access help for the create dataelements token printable command. It also provides examples on how to create a printable token data element.

pim create dataelements token printable --help
Usage: pim create dataelements token printable [OPTIONS]

  Creates a new Printable Token data element.

  EXAMPLES:

  # Create length-preserving printable token
  pim create dataelements token printable --name "ExactLengthPrintable" --description "Length-preserving printable tokenization" --tokenizer "SLT_1_3" --length-preserving

Options:
  --name TEXT                     The name for the data element.  [required]
  --description TEXT              An optional description for the data
                                  element.
  --tokenizer [SLT_1_3]           The lookup tables to be generated.
                                  [required]
  --from-left INTEGER             Number of characters to keep in clear from
                                  the left.
  --from-right INTEGER            Number of characters to keep in clear from
                                  the right.
  --length-preserving             Specifies whether the output must be of the
                                  same length as the input.
  --allow-short [YES|NOINPUTVALUE|NOWITHERROR]
                                  Allow short tokens.
  --help                          Show this message and exit.
Create Dataelements token unicode

The following command shows how to access help for the create dataelements token unicode command. It also provides examples on how to create a Unicode token data element.

pim create dataelements token unicode --help
Usage: pim create dataelements token unicode [OPTIONS]

  Creates a new Unicode Token data element.

  EXAMPLES:

  # Create with short value support for names
  pim create dataelements token unicode --name "IntlNameToken" --description "International name tokenization" --tokenizer "SLT_2_3" --allow-short "YES"

Options:
  --name TEXT                     The name for the data element.  [required]
  --description TEXT              An optional description for the data
                                  element.
  --tokenizer [SLT_1_3|SLT_2_3]   The lookup tables to be generated.
                                  [required]
  --allow-short [NOWITHERROR|YES|NOINPUTVALUE]
                                  Allow short tokens.
  --help                          Show this message and exit.
Create Dataelements token unicode base64

The following command shows how to access help for the create dataelements token unicode-base64 command. It also provides examples on how to create a Unicode Base64 token data element.

pim create dataelements token unicode-base64 --help
Usage: pim create dataelements token unicode-base64 [OPTIONS]

  Creates a new Unicode Base64 Token data element.

  EXAMPLES:

  # Create basic Unicode Base64 tokenization
  pim create dataelements token unicode-base64 --name "UnicodeBase64Token" --description "Base64 encoded Unicode tokenization" --tokenizer "SLT_1_3"

Options:
  --name TEXT                     The name for the data element.  [required]
  --description TEXT              An optional description for the data
                                  element.
  --tokenizer [SLT_1_3|SLT_2_3|SLT_1_6|SLT_2_6]
                                  The lookup tables to be generated.
                                  [required]
  --help                          Show this message and exit.
Create Dataelements token unicode gen2

The following command shows how to access help for the create dataelements token unicode-gen2 command. It also provides examples on how to create a Unicode Gen2 token data element.

pim create dataelements token unicode-gen2 --help
Usage: pim create dataelements token unicode-gen2 [OPTIONS]

  Creates a new Unicode Gen2 Token data element.

  EXAMPLES:

  # Create basic Unicode Gen2 token with custom alphabet
  pim create dataelements token unicode-gen2 --name "UnicodeGen2Token" --description "Unicode Gen2 with custom alphabet" --tokenizer "SLT_1_3" --alphabet-uid "1"

Options:
  --name TEXT                     The name for the data element.  [required]
  --description TEXT              An optional description for the data
                                  element.
  --tokenizer [SLT_1_3|SLT_X_1]   The lookup tables to be generated.
                                  [required]
  --alphabet-uid TEXT             The UID of the alphabet to use for
                                  tokenization.  [required]
  --from-left INTEGER             Number of characters to keep in clear from
                                  the left.
  --from-right INTEGER            Number of characters to keep in clear from
                                  the right.
  --length-preserving             Specifies whether the output must be of the
                                  same length as the input.
  --allow-short [YES|NOINPUTVALUE|NOWITHERROR]
                                  Allow short tokens.
  --default-encoding TEXT         Default encoding (kept for backwards
                                  compatibility).
  --help                          Show this message and exit.
Create Dataelements token upper alpha numeric

The following command shows how to access help for the create dataelements token upper-alpha-numeric command. It also provides examples on how to create an upper alpha-numeic token data element.

pim create dataelements token upper-alpha-numeric --help
Usage: pim create dataelements token upper-alpha-numeric 
           [OPTIONS]

  Creates a new Upper Alpha Numeric Token data element.

  EXAMPLES:

  # Create for product codes
  pim create dataelements token upper-alpha-numeric --name "ProductCodeToken" --description "Product code uppercase tokenization" --tokenizer "SLT_1_3" --from-left 2 --length-preserving

Options:
  --name TEXT                     The name for the data element.  [required]
  --description TEXT              An optional description for the data
                                  element.
  --tokenizer [SLT_1_3|SLT_2_3]   The lookup tables to be generated.
                                  [required]
  --from-left INTEGER             Number of characters to keep in clear from
                                  the left.
  --from-right INTEGER            Number of characters to keep in clear from
                                  the right.
  --length-preserving             Specifies whether the output must be of the
                                  same length as the input.
  --allow-short [YES|NOINPUTVALUE|NOWITHERROR]
                                  Allow short tokens.
  --help                          Show this message and exit.
Create Dataelements token upper alphabetic

he following command shows how to access help for the create dataelements token upper-alphabetic command. It also provides examples on how to create an upper alphabetic token data element.

pim create dataelements token upper-alphabetic --help
Usage: pim create dataelements token upper-alphabetic [OPTIONS]

  Creates a new Upper Alphabetic Token data element.

  EXAMPLES:

  # Create for organization names with short support
  pim create dataelements token upper-alphabetic --name "OrgNameToken" --description "Organization name tokenization"  --tokenizer "SLT_2_3" --allow-short "NOINPUTVALUE" --length-preserving

Options:
  --name TEXT                     The name for the data element.  [required]
  --description TEXT              An optional description for the data
                                  element.
  --tokenizer [SLT_1_3|SLT_2_3]   The lookup tables to be generated.
                                  [required]
  --from-left INTEGER             Number of characters to keep in clear from
                                  the left.
  --from-right INTEGER            Number of characters to keep in clear from
                                  the right.
  --length-preserving             Specifies whether the output must be of the
                                  same length as the input.
  --allow-short [YES|NOINPUTVALUE|NOWITHERROR]
                                  Allow short tokens.
  --help                          Show this message and exit.

Create Datastores

The following command shows how to access help for the create datastores command. It also provides examples on how to create a datastore resource.

pim create datastores --help
Usage: pim create datastores [OPTIONS] COMMAND [ARGS]...

  Commands for creating datastore resources.

Options:
  --help  Show this message and exit.

Commands:
  datastore  Creates a new datastore with the specified name and configuration.
  key        Creates and exports a datastore key for secure data operations.
  range      Adds an IP address range to a datastore for network access control.

Create Datastores Types

The following commands show how to access help for the create datastores <type> command. It also provides examples on how to manage datastore resources.

Create Datastores Datastore

The following command shows how to access help for the create datastores datastore command. It also provides examples on how to create a datastore.

pim create datastores datastore --help
Usage: pim create datastores datastore [OPTIONS]

  Creates a new datastore with the specified name and configuration.

  Datastores represent physical or logical storage systems that host protected
  data. They define where data protection policies are applied and provide the
  foundation for implementing encryption, tokenization, and access controls.

  EXAMPLES:

  # Create a simple datastore for development
  pim create datastores datastore --name "dev-database" --description "Development PostgreSQL database"

  # Create production datastore with detailed description
  pim create datastores datastore --name "prod-customer-db" --description "Production customer data warehouse with PII protection"

  # Create datastore and set as default
  pim create datastores datastore --name "primary-db" --description "Primary application database" --default

  WORKFLOW:
  # Step 1: Plan your datastore configuration
  # - Choose descriptive name for identification
  # - Decide if this should be the default datastore

  # Step 2: Create the datastore
  pim create datastores datastore --name <name> --description <description> [--default]

  # Step 3: Configure IP ranges and access controls
  pim create datastores range <datastore-uid> --from-ip <start> --to <end>

  # Step 4: Set up encryption keys if needed
  pim create datastores key <datastore-uid> --name <key-name>

Options:
  --name TEXT         Name of the datastore.  [required]
  --description TEXT  Description for the datastore.
  --default           Set this datastore as the default.
  --help              Show this message and exit.
Create Datastores Key

The following command shows how to access help for the create datastores key command. It also provides examples on how to export a datastore key.

pim create datastores key --help
Usage: pim create datastores key [OPTIONS] DATASTORE_UID

  Creates and exports a datastore key for secure data operations.

  EXAMPLES:

  # Create RSA export key for datastore
  pim create datastores key 15 --algorithm "RSA-OAEP-512" --description "export key" --pem "-----BEGIN PUBLIC KEY-----\nMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQ...\n-----END PUBLIC KEY-----"

  WORKFLOW:
  # Step 1: Generate a key pair (outside of PIM)
  openssl genrsa -out private_key.pem 2048
  openssl rsa -in private_key.pem -pubout -out public_key.pem

  # Step 2: Prepare the PEM content (escape newlines for command line)
  awk 'NF {sub(/
  /, ""); printf "%s\n",$0;}' public_key.pem

  # Step 3: Create the export key in PIM
  pim create datastores key <datastore-uid> --algorithm <algorithm> --description <description> --pem <pem-content>

  # Step 4: Verify the key was created
  pim get datastores keys <datastore-uid>

Options:
  --algorithm [RSA-OAEP-256|RSA-OAEP-512]
                                  Algorithm for the key.  [required]
  --description TEXT              Description of the key.
  --pem TEXT                      PEM formatted public key.  [required]
  --help                          Show this message and exit.
Create Datastores Range

The following command shows how to access help for the create datastores range command. It also provides examples on how to add a range of IP addresses to a datastore.

pim create datastores range --help
Usage: pim create datastores range [OPTIONS] DATASTORE_UID

  Adds an IP address range to a datastore for network access control.

  IP ranges define which network addresses are allowed to access the
  datastore. This provides network-level security by restricting datastore
  access to specific IP addresses or CIDR blocks.

  EXAMPLES:

  # Add single IP address access
  pim create datastores range 15 --from "192.168.1.100" --to "192.168.1.100"

  # Add corporate network access range
  pim create datastores range <datastore-uid> --from "10.0.0.1" --to "10.0.255.255"

  WORKFLOW:
  # Step 1: Get datastore UID
  pim get datastores datastore

  # Step 2: Plan your IP range requirements
  # - Identify source networks that need access
  # - Define start and end IP addresses

  # Step 3: Create the IP range
  pim create datastores range <datastore-uid> --from <start-ip> --to <end-ip>

  # Step 4: Verify the range was created
  pim get datastores ranges <datastore-uid>

Options:
  --from TEXT  Start IP address of the range.  [required]
  --to TEXT    End IP address of the range.  [required]
  --help       Show this message and exit.

Create Deploy

The following command shows how to access help for the create deploy command. It also provides examples on how to deploy policies or trusted applications or both to a datastore.

pim create deploy --help
Usage: pim create deploy [OPTIONS]

  Deploys policies and/or trusted applications to a data store.

  Creates a deployment that pushes data protection policies and trusted
  application configurations to the specified datastore.

  EXAMPLES:

  # Deploy single policy to a datastore
  pim create deploy --data-store-uid 15 --policy-uids 1

  # Deploy multiple policies to a datastore
  pim create deploy --data-store-uid 15 --policy-uids 1 --policy-uids 2 --policy-uids 3

  # Deploy trusted applications to grant access
  pim create deploy --data-store-uid 15 --trusted-application-uids 1 --trusted-application-uids 2

  # Deploy both policies and applications together
  pim create deploy --data-store-uid 15 --policy-uids 1 --policy-uids 2 --trusted-application-uids 1 --trusted-application-uids 2

  WORKFLOW:
  # Step 1: Verify datastore exists and is accessible
  pim get datastores datastore <data-store-uid>

  # Step 2: List available policies and applications
  pim get policies policy
  pim get applications application

  # Step 3: Deploy to a datastore
  pim create deploy --data-store-uid <datastore-uid> --policy-uids <policy-uid> --trusted-application-uids <app-uid>

  # Step 4: Verify deployment was successful
  pim get deploy

Options:
  --data-store-uid TEXT                UID of the data store to deploy.  [required]
  --policy-uids TEXT                   UIDs of the policies to deploy.
  --trusted-application-uids TEXT      UIDs of the trusted applications to deploy.
  --help                               Show this message and exit.

Create Masks

The following command shows how to access help for the create masks command. It also provides examples on how to create a mask.

pim create masks --help
Usage: pim create masks [OPTIONS]

  Creates a new mask with specified masking pattern and configuration.

  EXAMPLES:

  # Create mask for credit card numbers (show last 4 digits)
  pim create masks --name "credit-card-mask" --description "Mask credit card showing last 4 digits" --from-left 0 --from-right 4 --character "*"

  MASKING PATTERNS:

  Credit Card Masking (****-****-****-1234):
  --from-left 0 --from-right 4 --character "*"

  Email Masking (j***@example.com):
  --from-left 1 --from-right 0 --character "*"

  Full Masking (***********):
  --from-left 0 --from-right 0 --character "*" --masked

Options:
  --name TEXT           The name for the mask.  [required]
  --description TEXT    An optional description for the mask.
  --from-left INTEGER   Number of characters to be masked or kept in clear
                        from the left.  [required]
  --from-right INTEGER  Number of characters to be masked or kept in clear
                        from the right.  [required]
  --masked              Specifies whether the left and right characters should
                        be masked or kept in clear.
  --character TEXT      Specifies the mask character (*,#,-,0,1,2,3,4,5,6,7,8,
                        or 9).  [required]
  --help                Show this message and exit.

Create Policies

The following command shows how to access help for the create policies command. It also provides examples on how to create a policy.

pim create policies --help
Usage: pim create policies [OPTIONS] COMMAND [ARGS]...

  Creates a new policy or rule.

Options:
  --help  Show this message and exit.

Commands:
  policy  Creates a new data protection policy with specified access permissions.
  rules   Creates multiple rules and adds them to a policy in bulk.

Create Policies Types

The following commands show how to access help for the create policies <type> command. It also provides examples on how to manage policy resources.

Create Policies Policy

The following command shows how to access help for the create policies policy command. It also provides examples on how to create a policy.

Important: Ensure that you mandatorily add a description while creating a policy. If you do not add the description, then the pim get policies command fails.

pim create policies policy --help
Usage: pim create policies policy [OPTIONS]

  Creates a new data protection policy with specified access permissions.

    EXAMPLES:

  # Create basic policy with all protection operations enabled
  pim create policies policy --name "full-protection-policy" --description "Complete data protection with all operations" --protect --re-protect --un-protect

  # Create read-only policy (no protection operations)
  pim create policies policy --name "read-only-policy" --description "Read-only access without protection operations"

Options:
  --name TEXT         Name of the policy.  [required]
  --description TEXT  Description of the policy.  [required]
  --protect           Allow protect operation.
  --re-protect        Allow re-protect operation.
  --un-protect        Allow un-protect operation.
  --help              Show this message and exit.
Create Policies Rules

The following command shows how to access help for the create policies rules command. It also provides examples on how to create multiple rules and them to a policy.

pim create policies rules --help
Usage: pim create policies rules [OPTIONS] POLICY_UID

  Creates multiple rules and adds them to a policy in bulk.

  Rules define the mapping between roles and data elements with specific
  protection methods and access permissions. Each rule specifies how a role
  can access a data element, what masking to apply, and which protection
  operations are allowed.

  RULE FORMAT: role_uid,data_element_uid[,mask][,no_access_operation][,protect
  ][,re_protect][,un_protect]

  EXAMPLES:

  # Create rules for different roles accessing PII data elements
  pim create policies rules 15  --rule "1,3,1,NULL_VALUE,true,true,true" --rule "3,3,1,PROTECTED_VALUE,false,false,false" --rule "4,2,,NULL_VALUE,true,false,false"

  WORKFLOW:
  # Step 1: Verify policy exists and review its configuration
  pim get policies <policy-uid>

  # Step 2: Identify required roles and data elements
  pim get applications application  # for roles
  pim get data_elements data_element  # for data elements
  pim get masks  # for available masks

  # Step 3: Create rules in bulk
  pim create policies rules <policy-uid> --rule "..." --rule "..." --rule "..."

  # Step 4: Verify rules were created successfully
  pim get policies <policy-uid> --rules

  PARAMETER DESCRIPTIONS:

  role_uid (Required): UID of the role/application that will access data
  - References trusted applications or user roles
  - Must exist in the system before creating rules
  - Determines who can perform operations on data elements

  data_element_uid (Required): UID of the data element 
  - References specific data fields or columns
  - Must exist before creating rules
  - Defines what data is being protected

  mask (Optional): UID of mask to apply for data obfuscation
  - Empty/omitted: No masking applied
  - Must reference existing mask configuration
  - Controls how data appears when accessed

  no_access_operation (Optional, Default: NULL_VALUE):
  - NULL_VALUE: Return null when access denied
  - PROTECTED_VALUE: Return masked/protected format
  - EXCEPTION: Throw exception when access denied

  protect (Optional, Default: false): Allow data protection operations
  - true: Role can encrypt/tokenize/mask data
  - false: Role cannot perform protection operations

  re_protect (Optional, Default: false): Allow data re-protection
  - true: Role can change protection methods/keys
  - false: Role cannot re-protect data

  un_protect (Optional, Default: false): Allow data un-protection
  - true: Role can decrypt/detokenize/unmask data
  - false: Role cannot remove protection

  Examples: --rule "role1,de1,mask1,NULL_VALUE,true,false,false" --rule
  "role2,de2,,EXCEPTION,false,true,true"  --rule "role3,de3"

Options:
  --rule TEXT  Rule specification in format: "role_uid,data_element_uid[,mask]
               [,no_access_operation][,protect][,re_protect][,un_protect]".
               Can be specified multiple times.  [required]
  --help       Show this message and exit.

Create Roles

The following command shows how to access help for the create roles command. It also provides examples on how to create a role.

pim create roles --help
Usage: pim create roles [OPTIONS] COMMAND [ARGS]...

  Creates a new role or adds members to a role.

Options:
  --help  Show this message and exit.

Commands:
  members  Adds members to a role in bulk.
  role     Creates a new role with specified configuration and access mode.

Create Roles Types

The following commands show how to access help for the create roles <type> command. It also provides examples on how to manage roles.

Create Roles Members

The following command shows how to access help for the create roles members command. It also provides examples on how to add members to a role.

pim create roles members --help
Usage: pim create roles members [OPTIONS] ROLE_UID

  Adds members to a role in bulk.

  Members can be individual users or groups from various identity sources.
  This command allows adding multiple members at once with proper validation
  and error handling for each member specification.

  MEMBER FORMAT: name,source,sync_id,type  OR  name,source,type (sync_id
  optional)

  EXAMPLES:

  # Add individual users from LDAP
  pim create roles members 15  --member "john.doe,1,12345,USER" --member "jane.smith,1,67890,USER"

  Examples: --member "john.doe,ldap,12345,USER" --member
  "admin_group,ldap,67890,GROUP" --member "jane.smith,ad,USER"  (sync_id
  omitted)

Options:
  --member TEXT  Member specification in format: "name,source,sync_id,type" or
                 "name,source,type". Can be specified multiple times. Where
                 name is the member name (required, min_length=1), source is
                 the source of the member (required), sync_id is the
                 synchronization ID (optional), and type is the member type
                 (required: USER or GROUP).
  --help         Show this message and exit.
Create Roles Role

The following command shows how to access help for the create roles role command. It also provides examples on how to create a role.

pim create roles role --help
Usage: pim create roles role [OPTIONS]

  Creates a new role with specified configuration and access mode.

  EXAMPLES:

  # Create semiautomatic role for project team
  pim create roles role --name "project-alpha-team" --description "Project Alpha mixed access" --mode "SEMIAUTOMATIC"

Options:
  --name TEXT                               Name of the role.  [required]
  --description TEXT                        Description of the role.
  --mode [MANUAL|SEMIAUTOMATIC|AUTOMATIC]   Role mode.  [required]
  --allow-all                               Allow access to all users for this role.
  --help                                    Show this message and exit.

Create Sources

The following command shows how to access help for the create sources command. It also provides examples on how to create a member source.

pim create sources --help
Usage: pim create sources [OPTIONS] COMMAND [ARGS]...

  Creates a new source.

Options:
  --help  Show this message and exit.

Commands:
  ad        Creates a new Active Directory source for Windows domain integration.
  azure     Creates a new AZURE AD source for Microsoft cloud identity integration.
  database  Creates a new DATABASE source for relational database user repositories.
  file      Creates a new FILE source for static user and group management.
  ldap      Creates a new LDAP source for directory-based authentication and user management.
  posix     Creates a new POSIX source for Unix/Linux system account integration.

Create Sources Types

The following commands show how to access help for the create source <type> command. It also provides examples on how to create a member source of a specific type.

Create Source Ad

The following command shows how to access help for the create source ad command. It also provides examples on how to create an active directory member source.

pim create sources ad --help
Usage: pim create sources ad [OPTIONS]

  Creates a new Active Directory source for Windows domain integration.

  EXAMPLES:

  Note: The following commands use line continuation (\) for readability.
  In practice, run each command as a single line or use your shell's
  line continuation syntax

  # Create basic AD source with domain controller
  pim create sources ad --name "corporate-ad" --description "Corporate Active Directory" \
      --host "dc1.company.com" --port 389 \
      --user-name "service@company.com" --pass-word "password123" \
      --base-dn "dc=company,dc=com"

Options:
  --name TEXT         Name of the source.  [required]
  --description TEXT  Description of the source.
  --user-name TEXT    Authentication user.
  --pass-word TEXT    Authentication password.
  --host TEXT         The Fully Qualified Domain Name (FQDN) or IP address of
                      the directory server.
  --port INTEGER      The network port on the directory server where the
                      service is listening.
  --tls               The TLS protocol is enabled to create a secure
                      communication to the directory server.
  --base-dn TEXT      The Base DN for the server to search for users.
  --recursive         Enables recursive search for active directory or Azure
                      AD.
  --ldaps             Use LDAPS instead of startTLS.
  --help              Show this message and exit.
Create Source Azure

The following command shows how to access help for the create source azure command. It also provides examples on how to create an Azure member source.

pim create sources azure --help
Usage: pim create sources azure [OPTIONS]

  Creates a new AZURE AD source for Microsoft cloud identity integration.

  EXAMPLES:

  Note: The following commands use line continuation (\) for readability.
  In practice, run each command as a single line or use your shell's
  line continuation syntax.

  # Create basic Azure AD source for corporate tenant
  pim create sources azure --name "corporate-azure" --description "Corporate Azure AD" \
      --client-id "12345678-1234-1234-1234-123456789012" \
      --tenant-id "87654321-4321-4321-4321-210987654321" \
      --environment "PUBLIC"

  # Create Azure AD source with service principal authentication
  pim create sources azure --name "sp-azure" --description "Service Principal Azure AD" \
      --user-name "service-principal@company.onmicrosoft.com" \
      --pass-word "sp-secret-key" \
      --client-id "app-registration-id" \
      --tenant-id "company-tenant-id" \
      --environment "PUBLIC" --recursive

  # Create Azure Government cloud source
  pim create sources azure --name "gov-azure" --description "Azure Government Cloud" \
      --client-id "gov-app-id" \
      --tenant-id "gov-tenant-id" \
      --environment "USGOVERNMENT" \
      --user-attribute "userPrincipalName" \
      --group-attribute "displayName"

  # Create Azure China cloud source
  pim create sources azure --name "china-azure" --description "Azure China Cloud" \
      --client-id "china-app-id" \
      --tenant-id "china-tenant-id" \
      --environment "CHINA" \
      --recursive

  # Create Azure AD with custom attributes
  pim create sources azure --name "custom-azure" --description "Custom Azure AD Configuration" \
      --client-id "custom-app-id" \
      --tenant-id "custom-tenant-id" \
      --environment "PUBLIC" \
      --user-attribute "mail" \
      --group-attribute "displayName" \
      --group-members-attribute "members" \
      --recursive

  # Create multi-tenant Azure AD source
  pim create sources azure --name "partner-azure" --description "Partner Tenant Azure AD" \
      --client-id "partner-app-id" \
      --tenant-id "partner-tenant-id" \
      --environment "PUBLIC" \
      --user-name "guest@partner.onmicrosoft.com" \
      --pass-word "guest-credentials"

Options:
  --name TEXT                     Name of the source.  [required]
  --description TEXT              Description of the source.
  --user-name TEXT                Authentication user.
  --pass-word TEXT                Authentication password.
  --recursive                     Enables recursive search for active
                                  directory or Azure AD.
  --user-attribute TEXT           The Relative Distinguished Name (RDN)
                                  attribute of the user distinguished name.
  --group-attribute TEXT          The Relative Distinguished Name (RDN)
                                  attribute of the group distinguished name.
  --group-members-attribute TEXT  The attribute that enumerates members of the
                                  group.
  --client-id TEXT                The client id for AZURE AD.
  --tenant-id TEXT                The tenant id for the AZURE AD.
  --environment [CHINA|CANARY|PUBLIC|USGOVERNMENT|USGOVERNMENTL5]
                                  The AZURE AD environment that should be used.
  --help                          Show this message and exit.
Create Source Database

The following command shows how to access help for the create source database command. It also provides examples on how to create a database member source.

pim create sources database --help
Usage: pim create sources database [OPTIONS]

  Creates a new DATABASE source for relational database user repositories.

  EXAMPLES:

  Note: The following commands use line continuation (\) for readability.
  In practice, run each command as a single line or use your shell's
  line continuation syntax

  # Create Oracle database source with DSN
  pim create sources database --name "oracle-hr" --description "Oracle HR Database" \
      --user-name "pim_service" --pass-word "oracle123" \
      --host "oracle.company.com" --port 1521 \
      --dsn "XE" --vendor "ORACLE"

Options:
  --name TEXT                     Name of the source.  [required]
  --description TEXT              Description of the source.
  --user-name TEXT                Authentication user.
  --pass-word TEXT                Authentication password.
  --host TEXT                     The Fully Qualified Domain Name (FQDN) or IP
                                  address of the database server.
  --port INTEGER                  The network port on the directory server
                                  where the service is listening.
  --dsn TEXT                      The Data Source Name (DSN) for ODBC
                                  connection.
  --vendor [TERADATA|ORACLE|DATABASE|SQLSERVER|DB2|POSTGRESQLX]
                                  The vendor of the ODBC driver.
  --help                          Show this message and exit.
Create Source File

The following command shows how to access help for the create source file command. It also provides examples on how to create a file member source.

pim create sources file --help
Usage: pim create sources file [OPTIONS]

  Creates a new FILE source for static user and group management.

  EXAMPLES:

  # Create basic file source with user list
  pim create sources file --name "dev-users" --description "environment users" --user-file exampleusers.txt --group-file examplegroups.txt

Options:
  --name TEXT         Name of the source.  [required]
  --description TEXT  Description of the source.
  --user-file TEXT    A sample file that contains a list of individual
                      members.
  --group-file TEXT   A sample file that contains groups of members.
  --help              Show this message and exit.
Create Source Ldap

The following command shows how to access help for the create source ldap command. It also provides examples on how to create an LDAP member source.

pim create sources ldap --help
Usage: pim create sources ldap [OPTIONS]

  Creates a new LDAP source for directory-based authentication and user
  management.

  EXAMPLES:

  Note: The following commands use line continuation (\) for readability.
  In practice, run each command as a single line or use your shell's
  line continuation syntax

  # Create basic LDAP source with minimal configuration
  pim create sources ldap --name "company-ldap" --description "Company LDAP directory" \
      --host "ldap.company.com" --port 389 \
      --user-name "cn=admin,dc=company,dc=com" --pass-word "password123" \
      --user-base-dn "ou=users,dc=company,dc=com" \
      --group-base-dn "ou=groups,dc=company,dc=com"

  # Create OpenLDAP source with detailed configuration
  pim create sources ldap --name "openldap-prod" --description "Production OpenLDAP" \
      --host "openldap.company.com" --port 389 \
      --user-name "cn=readonly,dc=company,dc=com" --pass-word "readonly123" \
      --user-base-dn "ou=employees,dc=company,dc=com" \
      --user-attribute "uid" --user-object-class "posixAccount" \
      --user-login-attribute "uid" \
      --group-base-dn "ou=departments,dc=company,dc=com" \
      --group-attribute "cn" --group-object-class "posixGroup" \
      --group-members-attribute "memberUid" --timeout 60

Options:
  --name TEXT                     Name of the source.  [required]
  --description TEXT              Description of the source.
  --user-name TEXT                Authentication user.
  --pass-word TEXT                Authentication password.
  --host TEXT                     The Fully Qualified Domain Name (FQDN) or IP
                                  address of the directory server.
  --port INTEGER                  The network port on the directory server
                                  where the service is listening.
  --tls                           The TLS protocol is enabled to create a
                                  secure communication to the directory
                                  server.
  --user-base-dn TEXT             The base distinguished name where users can
                                  be found in the directory.
  --user-attribute TEXT           The Relative Distinguished Name (RDN)
                                  attribute of the user distinguished name.
  --user-object-class TEXT        The object class of entries where user
                                  objects are stored.
  --user-login-attribute TEXT     The attribute intended for authentication or
                                  login.
  --group-base-dn TEXT            The base distinguished name where groups can
                                  be found in the directory.
  --group-attribute TEXT          The Relative Distinguished Name (RDN)
                                  attribute of the group distinguished name.
  --group-object-class TEXT       The object class of entries where group
                                  objects are stored.
  --group-members-attribute TEXT  The attribute that enumerates members of the
                                  group.
  --group-member-is-dn            The members may be listed using their fully
                                  qualified name.
  --timeout INTEGER               The timeout value when waiting for a
                                  response from the directory server.
  --help                          Show this message and exit.

Delete Commands

The following section lists the delete commands.

Main Delete Command

The following command shows how to access help for the delete command.

pim delete --help
Usage: pim delete [OPTIONS] COMMAND [ARGS]...

  Delete a resource.

Options:
  --help  Show this message and exit.

Commands:
  alphabets     Deletes a specific alphabet by UID.
  applications  Deletes a specific application by UID.
  dataelements  Deletes a specific data element by UID.
  datastores    Commands for deleting datastore resources.
  masks         Deletes a specific mask by its UID.
  policies      Deletes a policy, a rule from a policy, or a data element from a policy.
  roles         Commands for deleting role resources.
  sources       Permanently deletes a source from the system.

Delete Alphabets

The following command shows how to access help for the delete alphabets command. It also provides examples on how to delete an alphabet.

pim delete alphabets --help
Usage: pim delete alphabets [OPTIONS] UID

  Deletes a specific alphabet by UID.

  WORKFLOW:

  # Step 1: First, list all alphabets to find the UID you want to delete
  pim get alphabets

  # Step 2: Copy the UID from the list and use it to delete the alphabet
  pim delete alphabets <uid-from-list>

  EXAMPLES:

  # Complete workflow example:
  # 1. List all alphabets to see available UIDs
  pim get alphabets

  # 2. Delete a specific alphabet using UID from the list above
  pim delete alphabets 14

Options:
  --help  Show this message and exit.

Delete Applications

The following command shows how to access help for the delete applications command. It also provides examples on how to delete a trusted application.

pim delete applications --help
Usage: pim delete applications [OPTIONS] UID

  Deletes a specific application by UID.

  WORKFLOW:

  # Step 1: First, list all applications to find the UID you want to delete
  pim get applications

  # Step 2: Copy the UID from the list and use it to delete the application
  pim delete applications <uid-from-list>

  EXAMPLES:

  # 1. List all applications to see available UIDs
  pim get applications

  # 2. Delete a specific application using numeric UID from the list above
  pim delete applications 42

Options:
  --help  Show this message and exit.

Delete Dataelements

The following command shows how to access help for the delete dataelements command. It also provides examples on how to delete a dataelement.

pim delete dataelements --help
Usage: pim delete dataelements [OPTIONS] UID

  Deletes a specific data element by UID.

  WORKFLOW:

  # Step 1: First, list all data elements to find the UID you want to delete
  pim get dataelements

  # Step 2: Copy the UID from the list and use it to delete the data element
  pim delete dataelements <uid-from-list>

  EXAMPLES:

  # Complete workflow example: # 1. List all data elements to see available
  UIDs pim get dataelements

  # 2. Delete a specific data element using numeric UID from the list above
  pim delete dataelements 42

Options:
  --help  Show this message and exit.

Delete Datastores

The following command shows how to access help for the delete datastores command. It also provides examples on how to delete a datastore.

pim delete datastores --help
Usage: pim delete datastores [OPTIONS] COMMAND [ARGS]...

  Commands for deleting datastore resources.

Options:
  --help  Show this message and exit.

Commands:
  datastore  Deletes a datastore by UID.
  key        Deletes an export key from a datastore.
  range      Deletes an IP address range from a datastore.

Delete Datastores Types

The following commands show how to access help for the delete datastores <type> command. It also provides examples on how to delete a datastore of a specific type.

Delete Datastores Datastore

The following command shows how to access help for the delete datastores datastore command. It also provides examples on how to delete a datastore by the UID.

pim delete datastores datastore --help
Usage: pim delete datastores datastore [OPTIONS] UID

  Deletes a datastore by UID.

  EXAMPLES:

  # Delete datastore by numeric UID
  pim delete datastores datastore 15

Options:
  --help  Show this message and exit.
Delete Datastores Key

The following command shows how to access help for the delete datastores key command. It also provides examples on how to delete a key from a datastore.

pim delete datastores key --help
Usage: pim delete datastores key [OPTIONS] DATASTORE_UID KEY_UID

  Deletes an export key from a datastore.      
  
  EXAMPLES:

  # Remove specific export key from datastore
  pim delete datastores key 1 2

  WORKFLOW:
  # Step 1: List current keys to identify the key UID
  pim get datastores keys <datastore-uid>

  # Step 2: Verify which processes use this key
  # - Check backup and migration schedules
  # - Verify no active export operations

  # Step 3: Delete the key
  pim delete datastores key <datastore-uid> <key-uid>

  # Step 4: Verify deletion
  pim get datastores keys <datastore-uid>

Options:
  --help  Show this message and exit.
Delete Datastores Range

The following command shows how to access help for the delete datastores range command. It also provides examples on how to delete a range of IP addresses from a datastore.

pim delete datastores range --help
Usage: pim delete datastores range [OPTIONS] DATASTORE_UID RANGE_UID

  Deletes an IP address range from a datastore.

  EXAMPLES:

  # Remove specific IP range from datastore
  pim delete datastores range 15 1

  WORKFLOW:
  # Step 1: List current ranges to identify the range UID
  pim get datastores ranges <datastore-uid>

  # Step 2: Verify which systems use this range
  # - Check with network administrators
  # - Verify no active connections from this range

  # Step 3: Delete the range
  pim delete datastores range <datastore-uid> <range-uid>

  # Step 4: Verify deletion
  pim get datastores ranges <datastore-uid>

Options:
  --help  Show this message and exit.

Delete Masks

The following command shows how to access help for the delete masks command. It also provides examples on how to delete a mask.

pim delete masks --help
Usage: pim delete masks [OPTIONS] UID

  Deletes a specific mask by its UID.

  EXAMPLES:

  # Delete mask by UID
  pim delete masks 15

Options:
  --help  Show this message and exit.

Delete Policies

The following command shows how to access help for the delete policies command. It also provides examples on how to delete a policy, a rule from a policy, or a data element from a policy.

pim delete policies --help
Usage: pim delete policies [OPTIONS] UID

  Deletes a policy, a rule from a policy, or a data element from a policy.

  EXAMPLES:

  # Delete entire policy (removes all rules and deployments)
  pim delete policies 15

  # Remove specific rule from policy
  pim delete policies 15 --rule-uid 23

  # Remove all rules for specific data element from policy
  pim delete policies 42 --data-element-uid 67

Options:
  --rule-uid TEXT          UID of the rule to remove.
  --data-element-uid TEXT  UID of the data element to remove from a policy.
  --help                   Show this message and exit.

Delete Roles

The following command shows how to access help for the delete roles command. It also provides examples on how to delete a role.

pim delete roles --help
Usage: pim delete roles [OPTIONS] COMMAND [ARGS]...

  Commands for deleting role resources.

Options:
  --help  Show this message and exit.

Commands:
  members  Removes a specific member from a role.
  role     Permanently deletes a role from the system.

Delete Roles Types

The following commands show how to access help for the delete roles <type> command.

Delete Roles Members

The following command shows how to access help for the delete roles members command. It also provides examples on how to remove a member from a role.

pim delete roles members --help
Usage: pim delete roles members [OPTIONS] ROLE_UID MEMBER_UID

  Removes a specific member from a role.

  EXAMPLES:

  # Remove specific user from role
  pim delete roles members 15 42
  pim delete roles members <role_uuid> <member_uuid>

Options:
  --help  Show this message and exit.
Delete Roles Role

The following command shows how to access help for the delete roles role command. It also provides examples on how to remove a role by the UID.

pim delete roles role --help
Usage: pim delete roles role [OPTIONS] UID

  Permanently deletes a role from the system.

  EXAMPLES:

  # Remove specific role  
  pim delete roles role 15

Options:
  --help  Show this message and exit.

Delete Sources

The following command shows how to access help for the delete source command. It also provides examples on how to delete a member source by the UID.

pim delete sources --help
Usage: pim delete sources [OPTIONS] UID

  Permanently deletes a source from the system.

  EXAMPLES:

  # Interactive source deletion with confirmation
  pim delete sources 15

Options:
  --help  Show this message and exit.

Get Commands

The following section lists the get commands.

Main Get Command

The following command shows how to access help for the get command.

pim get --help
Usage: pim get [OPTIONS] COMMAND [ARGS]...

  Display one or many resources.

Options:
  --help  Show this message and exit.

Commands:
  alphabets     Gets a specific alphabet by UID, or lists all alphabets if no UID is provided.
  applications  Gets a specific application by UID, or lists all applications if no UID is provided.
  dataelements  Gets a specific data element by UID, or lists all data elements if no UID is provided.
  datastores    Commands for getting datastore resources.
  deploy        List deployment history across all datastores.
  health        Displays the server health information and status.
  log           Gets the current log level configuration.
  masks         Gets a specific mask by UID, or lists all masks if no UID is provided.
  policies      Gets a specific policy by UID, lists all policies, or lists rules of a policy.
  ready         Displays the server readiness information and operational status.
  roles         Commands for getting role resources.
  sources       Gets source information by UID, lists all sources, or lists source members.
  version       Displays the server version information.

Get Alphabets

The following command shows how to access help for the get alphabets command. It also provides examples on how to retrieve all the alphabets or a specific alphabet.

pim get alphabets --help
Usage: pim get alphabets [OPTIONS] [UID]

  Gets a specific alphabet by UID, or lists all alphabets if no UID is
  provided.

  EXAMPLES:

  # List all available alphabets
  pim get alphabets

  # Get details for a specific alphabet by UID
  pim get alphabets 29

Options:
  --help  Show this message and exit.

Get Applications

The following command shows how to access help for the get applications command. It also provides examples on how to retrieve all trusted applications or a specific trusted application.

pim get applications --help
Usage: pim get applications [OPTIONS] [UID]

  Gets a specific application by UID, or lists all applications if no UID is
  provided.

  EXAMPLES:

  # List all available applications
  pim get applications

  # Get details for a specific application by UID
  pim get applications 1

Options:
  --help  Show this message and exit.

Get Dataelements

The following command shows how to access help for the get dataelements command. It also provides examples on how to retrieve all the data elements or a specific data element.

pim get dataelements --help
Usage: pim get dataelements [OPTIONS] [UID]

  Gets a specific data element by UID, or lists all data elements if no UID is
  provided.

  EXAMPLES:

  # List all available data elements pim get dataelements

  # Get details for a specific data element by UID pim get dataelements 15

Options:
  --help  Show this message and exit.

Get Datastores

The following command shows how to access help for the get datastores command. It also provides examples on how to retreive the datastore resources.

pim get datastores --help
Usage: pim get datastores [OPTIONS] COMMAND [ARGS]...

  Commands for getting datastore resources.

Options:
  --help  Show this message and exit.

Commands:
  datastore  Gets a specific datastore by UID, or lists all datastores if no UID is provided.
  keys       Gets a specific key by UID, or lists all keys for a datastore.
  ranges     Gets a specific range by UID, or lists all ranges for a datastore.

Get Datastores Types

The following commands show how to access help for the get datastores <type> command. It also provides examples on how to retrieve specific datastores.

Get Datastores Datastore

The following command shows how to access help for the get datastores datastore command. It also provides examples on how to retrieve all datastores or a specific datastore.

pim get datastores datastore --help
Usage: pim get datastores datastore [OPTIONS] [UID]

  Gets a specific datastore by UID, or lists all datastores if no UID is
  provided.

  Datastores represent the physical or logical storage systems where protected
  data is stored. They contain policies, applications, and IP ranges that
  define access control.

  EXAMPLES:

  # List all available datastores
  pim get datastores datastore

  # Get details for a specific datastore by UID
  pim get datastores datastore 15

Options:
  --help  Show this message and exit.
Get Datastores Keys

The following command shows how to access help for the get datastores key command. It also provides examples on how to retrieve all keys for a datastore or a specific key.

pim get datastores keys --help
Usage: pim get datastores keys [OPTIONS] DATASTORE_UID

  Gets a specific key by UID, or lists all keys for a datastore.

  Datastore keys manage encryption and access credentials for secure data
  operations. Keys can be export keys for data migration or operational keys
  for ongoing protection services. Key management is critical for data
  security.

  EXAMPLES:

  # List all keys for a specific datastore
  pim get datastores keys <datastore-uid>

  # Get details for a specific key within a datastore
  pim get datastores keys 15 --key-uid <key-uid>

  WORKFLOW:

  # Step 1: List all datastores to find the datastore UID
  pim get datastores datastore

  # Step 2: List keys for the specific datastore
  pim get datastores keys <datastore-uid>

  # Step 3: Get specific key details if needed
  pim get datastores keys <datastore-uid> --key-uid <key-uid>

Options:
  --key-uid TEXT  UID of the specific key to get.
  --help          Show this message and exit.
Get Datastores Ranges

The following command shows how to access help for the get datastores ranges command. It also provides examples on how to retrieve all the IP address range for a datastore or a specific range.

pim get datastores ranges --help
Usage: pim get datastores ranges [OPTIONS] DATASTORE_UID

  Gets a specific range by UID, or lists all ranges for a datastore.

  IP ranges define which network addresses are allowed to access the
  datastore. Ranges provide network-level security by restricting datastore
  access to specific IP addresses or CIDR blocks.

  EXAMPLES:

  # List all IP ranges for a specific datastore
  pim get datastores ranges 15

  # Get details for a specific range within a datastore
  pim get datastores ranges 15 --range-uid 1

  WORKFLOW:

  # Step 1: List all datastores to find the datastore UID
  pim get datastores datastore

  # Step 2: List ranges for the specific datastore
  pim get datastores ranges <datastore-uid>

  # Step 3: Get specific range details if needed
  pim get datastores ranges <datastore-uid> --range-uid <range-uid>

Options:
  --range-uid TEXT  UID of the range to get.
  --help            Show this message and exit.

Get Deploy

The following command shows how to access help for the get deploy command. It also provides examples on how to list the deployment history.

pim get deploy --help
Usage: pim get deploy [OPTIONS]

  List deployment history across all datastores.

  EXAMPLES:

  # List all deployment history
  pim get deploy

Options:
  --help  Show this message and exit.

Get Health

The following command shows how to access help for the get health command. It also provides examples on how to display the server health information.

pim get health --help
Usage: pim get health [OPTIONS]

  Displays the server health information and status.

  EXAMPLES:

  # Check current server health status
  pim get health

Options:
  --help  Show this message and exit.

Get Log

The following command shows how to access help for the get log command. It also provides examples on how to retrieve the current log level.

pim get log --help
Usage: pim get log [OPTIONS]

  Gets the current log level configuration.

  EXAMPLES:

  # Check current log level setting
  pim get log

Options:
  --help  Show this message and exit.

Get Masks

The following command shows how to access help for the get masks command. It also provides examples on how to retrieve all masks or a specific mask.

pim get masks --help
Usage: pim get masks [OPTIONS] [UID]

  Gets a specific mask by UID, or lists all masks if no UID is provided.

  EXAMPLES:

  # List all available masks
  pim get masks

  # Get details for a specific mask by UID
  pim get masks 15

Options:
  --help  Show this message and exit.

Get Policies

The following command shows how to access help for the get policies command. It also provides examples on how to retrieve all policies, a specific policy, or all rules of a policy.

pim get policies --help
Usage: pim get policies [OPTIONS] [UID]

  Gets a specific policy by UID, lists all policies, or lists rules of a
  policy.

  EXAMPLES:

  # List all available policies
  pim get policies

  # Get details for a specific policy by UID
  pim get policies 15

  # List all rules within a specific policy
  pim get policies 15 --rules

Options:
  --rules  List rules of the policy.
  --help   Show this message and exit.

Get Ready

The following command shows how to access help for the get ready command. It also provides examples on how to display the server readiness information.

pim get ready --help
Usage: pim get ready [OPTIONS]

  Displays the server readiness information and operational status.

  EXAMPLES:

  # Check if server is ready for requests
  pim get ready

Options:
  --help  Show this message and exit.

Get Roles

The following command shows how to access help for the get roles command. It also provides examples on how to retrieve the resources for a role.

pim get roles --help
Usage: pim get roles [OPTIONS] COMMAND [ARGS]...

  Commands for getting role resources.

Options:
  --help  Show this message and exit.

Commands:
  members  Lists all members of a specific role.
  role     Gets a specific role by UID, or lists all roles if no UID is provided.
  users    Lists users of a specific member in a role.

Get Roles Types

The following commands show how to access help for the get roles <type> command.

Get Roles Members

The following command shows how to access help for the get roles members command. It also provides examples on how to list all members of a role.

pim get roles members --help
Usage: pim get roles members [OPTIONS] ROLE_UID

  Lists all members of a specific role.

  EXAMPLES:

  # List all members of a specific role
  pim get roles members 15

Options:
  --help  Show this message and exit.
Get Roles Role

The following command shows how to access help for the get roles role command. It also provides examples on how to retrieve all roles or a specific role.

pim get roles role --help
Usage: pim get roles role [OPTIONS] [UID]

  Gets a specific role by UID, or lists all roles if no UID is provided.

  EXAMPLES:

  # List all available roles
  pim get roles role

  # Get details for a specific role by UID
  pim get roles role 15

Options:
  --help  Show this message and exit.
Get Roles Users

The following command shows how to access help for the get roles users command. It also provides examples on how to retrieve users of a specific member in a role.

pim get roles users --help
Usage: pim get roles users [OPTIONS] ROLE_UID MEMBER_UID

  Lists users of a specific member in a role.

  EXAMPLES:

  # List users in a specific group member of a role
  pim get roles users 15 23
  pim get roles users "<role-uuid>" "<member-uuid>"

Options:
  --help  Show this message and exit.

Get Sources

The following command shows how to access help for the get sources command. It also provides examples on how to retrieve all source, a specific source, or members of a source.

pim get sources --help
Usage: pim get sources [OPTIONS] [UID]

  Gets source information by UID, lists all sources, or lists source members.

  EXAMPLES:

  # List all configured sources
  pim get sources

  # Get detailed information about a specific source
  pim get sources 15

  # List all members of a specific source
  pim get sources 23 --members

Options:
  --members  List members of the source.
  --help     Show this message and exit.

Get Version

The following command shows how to access help for the get version command. It also provides examples on how to display the version information of the server.

pim get version --help
Usage: pim get version [OPTIONS]

  Displays the server version information.

  EXAMPLES:

  # Display server version information
  pim get version

Options:
  --help  Show this message and exit.

Set Commands

The following section lists the set commands.

Main Set Command

The following command shows how to access help for the set command.

pim set --help
Usage: pim set [OPTIONS] COMMAND [ARGS]...

  Update fields of a resource.

Options:
  --help  Show this message and exit.

Commands:
  log  Sets the log level for the PIM server.

Set Log

The following command shows how to access help for the set log command. It also provides examples on how to set the log level.

pim set log --help
Usage: pim set log [OPTIONS] {ERROR|WARN|INFO|DEBUG|TRACE}

  Sets the log level for the PIM server.

  Higher levels include all lower levels (TRACE includes DEBUG, INFO, WARN,
  ERROR).

  EXAMPLES:

  # Enable debug logging for troubleshooting
  pim set log DEBUG

Options:
  --help  Show this message and exit.

3.1 - Using the Policy Management Command Line Interface (CLI)

Explains the usage of the Policy Management CLI with some generic samples.

The following table provides section references that explain usage of some of the Policy Management CLI. It includes an example workflow to work with the Policy Management functions. If you want to view all the Policy Management CLI, then refer to the section Policy Management Command Line Interface (CLI) Reference.

Policy Management CLISection Reference
Policy Management initializationInitializing the Policy Management
Creating an empty manual role that will accept all usersCreating a Manual Role
Create data elementsCreate Data Elements
Create policyCreate Policy
Add roles and data elements to the policyAdding roles and data elements to the policy
Create a default data storeCreating a default datastore
Deploy the data storeDeploying the Data Store
Get the deployment informationGetting the Deployment Information

Initializing the Policy Management

This section explains how you can initialize Policy Management to create the keys-related data and the policy repository.

pim invoke init

The following output appears:

✅ PIM successfully initialized (bootstrapped).

Creating a Manual Role

This section explains how you can create a manual role that accepts all the users.

pim create roles role --name "project-alpha-team" --description "Project Alpha all access" --mode "MANUAL" --allow-all

The following output appears:

NAME                DESCRIPTION               MODE             ALLOWALL  UID
project-alpha-team  Project Alpha all access  RoleMode.MANUAL  True      1

The command creates a role named project-alpha-team that has the UID as 1.

Creating Data Elements

This section explains how you can create a data element.

pim create dataelements aes128-cbc-enc --name "BasicEncryption" --description "Basic data encryption"

The following output appears:

UID  NAME             DESCRIPTION            IVTYPE       CHECKSUMTYPE       CIPHERFORMAT
1    BasicEncryption  Basic data encryption  IvType.NONE  ChecksumType.NONE  CipherFormat.NONE

The command creates an AES-128-CBC-ENC encryption data element named BasicEncryption that has the UID as 1.

Creating Policy

This section explains how you can create a policy.

pim create policies policy --name "full-protection-policy" --description "Complete data protection with all operations" --protect --re-protect --un-protect

The following output appears:

NAME                     DESCRIPTION                                   ACCESS                                                   UID
 full-protection-policy  Complete data protection with all operations  {'protect': True, 'reProtect': True, 'unProtect': True}  1

The command creates a policy named full-protection-policy that has the UID as 1.

Adding Roles and Data Elements to a Policy

This section explains how you can add roles and data elements to a policy.

pim create policies rules <policy-uid> --rule "1,1,,NULL_VALUE,true,false,false"

The following output appears:

 ROLE  DATAELEMENT  MASK  NOACCESSOPERATION  ACCESS
 1     1            0     NULL_VALUE         {'protect': True, 'reProtect': False, 'unProtect': False}

The command adds the role with the UID 1 and the data element with the UID 1 to the policy with the UID 1.

Creating a Default Data Store

This section explains how you can create a default data store.

pim create datastores datastore --name "primary-db" --description "Primary application database" --default

The following output appears:

NAME        DESCRIPTION                   DEFAULT  UID
primary-db  Primary application database  True     1

The command creates a default data store named primary-db that has the UID as 1.

Deploying a Specific Data Store

This section explains how you can deploy policies and trusted applications linked to a specific data store. The specifications provided for the specific data store are applied and becomes the end-result.

pim invoke datastores deploy 1 --policies 1

The following output appears:

Successfully deployed to datastore '1':
  Policies: 1

The command deploys the policy with the UID 1 to the data store with the UID 1.

Getting the Deployment Information

This section explains how you can check the complete deployment information. This service returns the list of the data stores with the connected policies and trusted applications.

pim get deploy

The following output appears:

 UID  POLICIES  APPLICATIONS
 1    ['1']     []

The command retrieves the deployment information. It displays the UID of the data store and the policy that has been deployed.