The KUMA distribution kit includes the kuma-ptvm utility, which consists of an executable file and a configuration file. The utility is supported on Windows and Linux operating systems. The utility allows you to connect to the MaxPatrol VM API to get data about devices and their attributes, including vulnerabilities, and also lets you edit asset data and import data using the KUMA API. Importing data is supported for MaxPatrol VM 1.1.
Configuring the import of asset information from MaxPatrol VM to KUMA involves the following steps:
You must create user accounts and a KUMA token for API operations.
If necessary, you can edit the received files.
When re-importing existing assets, assets that already exist in KUMA are overwritten. In this way, fixed vulnerabilities are removed.
Known limitations
If the same IP address is specified for two assets with different FQDNs, KUMA imports such assets as two different assets; the assets are not combined.
If an asset has two softwares with the same data in the name, version, vendor fields, KUMA imports this data as one software, despite the different software installation paths in the asset.
If the FQDN of an asset contains a space or underscore ("_"), data for such assets is not imported into KUMA, and the log indicates that the assets were skipped during import.
If an error occurs during import, error details are logged and the import stops.
Preparatory actions
Requirements imposed on accounts for which the API token is generated:
Creating the configuration file
To create the configuration file:
cd kuma-ansible-installer
cp kuma-ptvm-config-template.yaml kuma-ptvm-config.yaml
The configuration file will be created. Go to the Importing asset data step.
Importing asset data
To import asset information:
kuma-ptvm --config <
path to the kuma-ptvm-config.yaml file
> --download --upload
kuma-ptvm --config <
path to the kuma-ptvm-config.yaml file
> --download
For each tenant specified in the configuration file, a separate file is created with a name of the form <KUMA tenant ID>.JSON. Also, during export, a 'tenants' file is created, containing a list of JSON files to be uploaded to KUMA. All files are saved in the utility's directory.
kuma-ptvm --config <
path to the kuma-ptvm-config.yaml file
> --upload
To view information about the available commands of the utility, run the --help command.
The asset information is imported from MaxPatrol VM to KUMA. The console displays information on the number of new and updated assets.
Possible errors
When running the kuma-ptvm utility, the "tls: failed to verify certificate: x509: certificate is valid for localhost" error may be returned.
Solution.
To disable certificate validation, add the following line to the configuration file in the 'MaxPatrol settings' section:
ignore_server_cert: true
As a result, the utility is started without errors.
Page top