Indegy Industrial Cybersecurity Suite
- 2 Minutes To Read
-
Print
-
DarkLight
Indegy Industrial Cybersecurity Suite protects industrial networks from cyber threats, malicious insiders, and human error, including threat detection and mitigation, asset tracking, vulnerability management, configuration control, and device integrity checks.
The Indegy Industrial Cybersecurity Suite adapter connection requires the following parameters:
- Indegy Domain - Use your Indegy domain.
- Robot Name - Specify the logical name for the robot you have created by using the
- SSL TLC Private Key - Upload the private key you have generated, which is a key.pem file.
- SSL Certificate - Upload the public key (cert) you have generated, which is a cert.pem file.
- Verify SSL - Choose whether to verify the SSL certificate of the server.
- HTTPS Proxy (optional) - Enter details if the connection to the API requires a proxy.
- Choose Instance - If you are using multi-nodes, choose the Axonius node that is integrated with the adapter. By default, the 'Master' Axonius node (instance) is used. For details, see Connecting Additional Axonius Nodes
Creating a Private Key, Public (Cert) Key and a "Robot" User for Authenticating API Calls to Indegy
The Indegy API Robots endpoint is used to facilitate the authentication and authorization process through the use of TLC Client Certificate. Instead of managing complicated tokens and sessions, Indegy enables the creation of a "Robot" user that serves as an intermediary, while supporting the use of TLC certificates as the authentication method for API calls.
To create a private key, public (cert) key and a "robot" user, do as follows:
-
Obtain a Token from Indegy Support.
-
Connect to your Indegy domain and run the following command to create a cert and private key.
For example:openssl req -x509 -newkey rsa:2048 -keyout key.pem -out cert.pem -days 365 -nodes
-
Save the generates files: the private key (key.pem) and the public key (cert.pem).
-
Issue a Robots (POST) API call with the body and token as specified below. This API call will associate the token with key.pem, so Axonius will not need to use the token for future API calls.
In the request, specify the following mandatory parameters:
- IP - The IP of your Indegy domain. Replace < IP > in the script below.
- Token - The token you have obtained from Indegy support. Replace < TOKEN > in the script below.
- Name (string) - A logical name for the robot ("robot1" in the example script below).
- Role (string) - The type of user role that is being created: "AdminRole" or "ReaderRole" ("AdminRole" in the example script below).
- Cert - The content of your cert.pem file. Use "\n" to reflect new rows. Replace < CERT> in the script below.
For example:curl -k -H 'Authorization: Bearer <TOKEN>' -XPOST https://<IP>/v1/robots --data '{"name": "robot1", "role": "AdminRole","cert": "<CERT>"}'