Outpost24 integration
Upload the Outpost24 XML report against the Outpost 24 source. Each detail element becomes a finding attached to the host it was reported on.
Scan types imported
- Network vulnerability assessment
- Web application findings
File import
The template walks one detail element per finding under each scanned IP.
What Centraleyezer expects in the file
- Per finding: name, description, solution, CVSSv3 score and vector, risk rating, CVE (from the id/cve element), port number and service protocol (from portinfo).
- The numeric risk rating (0–3) drives risk scoring.
- Assets are matched by the ip element.
How imported findings are risk-scored
Every Outpost24 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.