Nipper integration
Two templates cover Titania Nipper: a CSV issue export and the full Nipper Studio Security Audit XML report. Findings land on the audited device assets.
Scan types imported
- Network device security audits (routers, switches, firewalls)
- Configuration benchmark findings
File import
Upload either the CSV issue list or the Security Audit XML report generated by Nipper Studio.
What Centraleyezer expects in the file
- CSV columns: Issue Title, Devices, Rating, Finding, Recommendation — with a Critical/High/Medium/Low/Informational rating scale.
- XML: the template walks the SECURITYAUDIT report sections, reading the issue title, finding text, recommendation, rating and CVSSv2 base score/vector per section.
- Assets are matched by device name.
How imported findings are risk-scored
Every Nipper 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.