Lynis integration
Upload the normalized Lynis report (.lns) against the Lynis source. Each audit finding lands on the corresponding host asset with its severity and remediation guidance.
Scan types imported
- Host hardening & configuration audit findings
- Compliance checks on Linux/Unix systems
File import
The Lynis report is normalized into Centraleyezer’s .lns container and mapped per host.
What Centraleyezer expects in the file
- Per finding: name, description, recommendation, severity (Low/Medium/High), port and protocol where applicable.
- Findings attach to the audited host asset.
How imported findings are risk-scored
Every Lynis 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.