AppSpider (Rapid7) integration
Export the AppSpider report as XML and upload it against the AppSpider source.
Scan types imported
- Web application DAST with attack traffic evidence
File import
The template walks one Vuln element per finding, per website.
What Centraleyezer expects in the file
- Per finding: vulnerability type, description, recommendation, CWE ID, attack score (0-Safe to 4-High) and raw request/response.
- Web assets are matched by the WebSite element.
How imported findings are risk-scored
Every AppSpider (Rapid7) 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.
Related integrations
Rapid7 InsightVM
Connect the Rapid7 InsightVM Security Console API v3, pick a site, and import per-asset vulnerabilities with solutions and proof. Nexpose CSV also supported.
Metasploit Pro
Import Metasploit Pro scan and exploitation results into Centraleyezer via XML export for validated finding tracking.