AlienVault USM integration
Two templates cover AlienVault: the classic XLS vulnerability report and the AlienVault USM CSV export.
Scan types imported
- Network vulnerability scan results
- Threat / vulnerability data from USM
File import
Upload the XLS vulnerability report (the template skips the 5-row preamble) or the USM CSV export.
What Centraleyezer expects in the file
- XLS columns: Host IP, Service (port/protocol), CVSS, Vulnerability, Remedation, Observation, Test Output, Risk Level, CVEs.
- USM CSV columns: Asset, Vulnerability Name, Severity, Vulnerability ID.
- The High/Medium/Low/Info risk level drives risk scoring; assets are matched by IP.
How imported findings are risk-scored
Every AlienVault USM 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.