Tripwire IP360
Connection Requirements
This adapter connects to a Tripwire IP360 VnE Manager and collects the tracked asset inventory from the AssetView API. IP360 is deployed on premises only, so the connection always targets your own VnE Manager, whether it runs on VMware, Hyper-V or an AWS Marketplace image.
Before you begin
Use a VnE Manager account whose permissions allow:
Access to the AssetView APIs under /rest/v1/assets
Access to the remaining /rest/v1/ endpoints
Enumerating asset IDs and running queries per asset
Make sure the port the VnE Manager publishes its REST API on is reachable from the OctoXLabs host.
1 - Ip
The hostname or IP address of your Tripwire IP360 VnE Manager, for example vne.example.com.
2 - Port
The port the VnE Manager REST API is published on. (default: 443)
3 - Is Secure? (advanced)
Choose this if your connection is going to be over HTTPS (optional, default: True).
4 - Username
The username of the VnE Manager account used to connect. IP360 accounts are usually written in email form, for example ip360@tripwire.com.
5 - Password
The password of the provided username.
6 - Per Page (advanced)
The number of assets requested per page. Larger values reduce the number of requests but increase the load on the VnE Manager. (default: 100)
7 - Fetch Device Operation (advanced)
Collect the asset inventory. Turning this off makes the discovery return no assets. (default: True)
8 - Proxy (advanced)
An HTTP proxy to route the requests through, in host:port format. Leave it empty to connect directly. (default: empty)
9 - Timeout (advanced)
The amount of time (in seconds) to wait for API responses. (default: 30)
Last updated
Was this helpful?