HP WebInspect integration
Export the WebInspect scan as XML and upload it against the Webinspect source. The template reads the report’s per-issue sections into structured finding fields.
Scan types imported
- Dynamic web application testing
File import
The template walks one Issue per finding and resolves the Summary, Implication and Execution report sections.
What Centraleyezer expects in the file
- Per issue: URL, severity (0–4), raw request and response, and the Summary (description), Implication (impact) and Execution (fix) section texts.
- Web assets are matched by the issue URL.
How imported findings are risk-scored
Every HP WebInspect 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.