AppDetectivePro integration
Export the AppDetectivePro assessment as CSV and upload it against the AppDetectivePro source. Findings land on your database assets.
Scan types imported
- Database configuration & vulnerability checks (Oracle, SQL Server, MySQL, PostgreSQL, DB2)
File import
Standard CSV export, header on the first row.
What Centraleyezer expects in the file
- Columns: Asset Name, Check Name, Overview, Fix Information, Cve References, Risk.
- The High/Medium/Low risk drives risk scoring; database assets are matched by asset name.
How imported findings are risk-scored
Every AppDetectivePro 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.