Import agentless connections using an XLSX file

The import XLSX file menu is available through the drop down arrow next to the + Add button in the top right corner of the agentless connections list of the Cyberwatch interface, that displays the Import an XLSX file button.

The form offers two options:

  • possibility to import the chosen file that will be used to create agentless connections
  • an XLSX file import model to use this feature

Using the model file

Download the XLSX file model, its name will look something like batch_import_model-[HASH].xlsx.

This file has two tabs:

  • The Example tab presents examples of ways to import different kind of connections
  • To Import is the tab that Cyberwatch will read to create the agentless connections

Data present in the Example tab will not be taken into account when importing the file in Cyberwatch.

XLSX file content

The XLSX file contains the following columns:

  • HOST*: for the hostname or IP address of the asset to import
  • PORT*: the asset port on which will be established the agentless connection
  • TYPE*: the type of connection established, possible values are: LINUX (SSH), WINDOWS (WINRM), SNMP
  • AUTH*: authentication type, possible values are: PASSWORD, KEY, NEGOTIATE, PLAIN TEXT OVER SSL, SSL
  • CREDENTIAL: the stored credential in Cyberwatch to be used for the connection, has to be specified by its name. Using this field makes it not required to fill the USERNAME, SECRET, ENCRYPTION_PASSWORD columns
  • USERNAME: the login used to connect to the asset
  • SECRET: the password or key used to authenticate on the asset (corresponds to the authentication password for SNMP connections)
  • ENCRYPTION_PASSWORD: only for SNMP connections, represents the encryption password
  • NODE*: the name of the Cyberwatch node that will be used to monitor the asset
  • GROUPS: optional groups that will be assigned to the asset once it is created

Fields followed by an “*” are always mandatory.

Please consult the examples tab to see more relevant real world use cases.

Using a stored credential, with the CREDENTIAL column, is highly recommended, and avoids having to provide logins and passwords in the XLSX file.

Back to top