Tripwire IP360 integration
Centraleyezer connects to the Tripwire IP360 VnE console API, lets you pick a network, and on every run imports the newest completed audit for that network — vulnerability results, host details and OS information. A Tripwire CSV template is available for file-based imports.
Scan types imported
- Network vulnerability audits
- Host and OS detail from the VnE console
File import
Upload a Tripwire CSV export using the TripWire template.
What Centraleyezer expects in the file
- Columns: Description, Remediation, Vulnerability, CVE, IP, Risk.
- Assets are matched by IP.
API connection
Configure the VnE console address and an API-enabled account, click Test to list your IP360 networks, and select the network to track. Imports are incremental — an audit that was already ingested is skipped.
Configuration
Where to get the credentials
Use a VnE console user with API permissions (created in the IP360 VnE administration UI).
What gets imported on every run
- The latest completed audit of the selected network: every vulnerability result with port and protocol.
- Vulnerability detail (description, remediation) resolved from the IP360 ASPL vulnerability database.
- Host details and operating system information for every audited host — findings attach to assets matched by IP.
How imported findings are risk-scored
Every Tripwire IP360 finding is normalised into Centraleyezer’s risk model on import: the scanner’s native severity scale maps to a configurable DREAD vector (Damage, Reproducibility, Exploitability, Affected users, Discoverability), which combines with asset criticality, network exposure, exploitability intelligence and the platform’s other risk factors to produce one comparable risk score across every scanner you run. CVE, CVSS and CWE metadata are preserved on the finding for reference and reporting, and duplicate findings from repeated imports are automatically correlated instead of creating noise.