Importing asset information from RedCheck

This integration is an example and may require additional configuration depending on the versions used and the specifics of the infrastructure.
Compatibility is confirmed only for KUMA 2.0 or later and RedCheck 2.6.8 or later.
The terms and conditions of premium technical support do not apply to this integration; support requests are processed without a guaranteed response time.

RedCheck is a system for monitoring and managing the information security of an organization.

You can import asset information from RedCheck network device scan reports into KUMA.

Import is available from simple "Vulnerabilities" and "Inventory" reports in CSV format, grouped by hosts.

Imported assets are displayed in the KUMA web interface in the Assets section. If necessary, you can edit the settings of assets.

Data is imported through the API using the redcheck-tool.py utility. The utility requires Python 3.6 or later and the following libraries:

• csv
• re
• json
• requests
• argparse
• sys

To import asset information from a RedCheck report:

1. Generate a network asset scan report in RedCheck in CSV format and copy the report file to the server where the script is located.

   For more details about scan tasks and output file formats, refer to the RedCheck documentation.

2. Create a file with the token for accessing the KUMA REST API.

   The account for which the token is created must satisfy the following requirements:

   • Tenant administrator or Tier 2 analyst role.
   • Access to the tenant into which the assets will be imported.
   • Rights to use API requests: GET /assets, GET /tenants, POST/assets/import.
3. Download the script:

   https://box.kaspersky.com/d/2dfd1d677c7547a7ac1e/

4. Copy the redcheck-tool.py tool to the server hosting the KUMA Core and make the tool's file executable:

   chmod +x <path to the redcheck-tool.py file>

5. Run the redcheck-tool.py utility:

   python3 redcheck-tool.py --kuma-rest <address and port of the KUMA REST API server> --token <API token> --tenant <name of the tenant in which the assets must be placed> --vuln-report <full path to the "Vulnerabilities" report file> --inventory-report <full path to the "Inventory" report file>

   Example: python3 --kuma-rest example.kuma.com:7223 --token 949fc03d97bad5d04b6e231c68be54fb --tenant Main --vuln-report /home/user/vuln.csv --inventory-report /home/user/inventory.csv

   You can use additional flags and commands for import operations. For example, the -v command displays an extended report on the received assets. A detailed description of the available flags and commands is provided in the "Flags and commands of redcheck-tool.py" table. You can also use the --help command to view information on the available flags and commands.

The asset information is imported from the RedCheck report to KUMA. The console displays information on the number of new and updated assets.

The tool works as follows when importing assets:

• KUMA overwrites the data of assets imported through the API, and deletes information about their resolved vulnerabilities.
• KUMA skips assets with invalid data.

  Flags and commands of redcheck-tool.py

  Flags and commands	Mandatory	Description
  --kuma-rest <address and port of the KUMA server>	Yes	Port 7223 is used for API requests by default. You can change the port if necessary.
  --token <token>	Yes	The value of the option must contain only the token. The Tenant administrator or Tier 2 analyst role must be assigned to the user account for which the API token is being generated.
  --tenant <tenant name>	Yes	Name of the KUMA tenant in which the assets from the RedCheck report will be imported.
  --vuln-report <full path to the "Vulnerabilities" report>	Yes	"Vulnerabilities" report file in CSV format.
  --inventory-report <full path to the "Inventory" report file>	No	"Inventory" report file in CSV format.
  -v	No	Display extended information about the import of assets.

  Possible errors

  Error message	Description
  Tenant %w not found	The tenant name was not found.
  Tenant search error: Unexpected status Code: %d	An unexpected HTTP response code was received while searching for the tenant.
  Asset search error: Unexpected status Code: %d	An unexpected HTTP response code was received while searching for an asset.
  [%w import][error] Host: %w Skipped asset with FQDNlocalhost or IP 127.0.0.1	When importing inventory/vulnerabilities information, host cfqdn=localhost or ip=127.0.0.1 was skipped.