All integrations
DAST

Nikto integration

Run Nikto with XML output (-Format xml) and upload the file against the Nikto source.

Scan types imported

  • Web server misconfigurations and dangerous files

File import

XML

The template reads each scan item description per scanned host.

What Centraleyezer expects in the file

  • The standard niktoscan XML output; each description item becomes a finding on the scanned host.

How imported findings are risk-scored

Every Nikto 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.

See the Nikto integration live

Book a demo and we’ll connect your Nikto data and walk through risk-based prioritisation on your own findings.

Nikto Integration — Setup & Imported Scan Types