SSL Labs integration
Add SSL Labs as a managed scanner and Centraleyezer assesses every HTTPS website asset through the public SSL Labs API v3: it starts the analysis, polls until the grade is ready, and imports the findings — weak cipher suites, certificate problems and insecure protocol versions. A JSON file import is also available.
Scan types imported
- TLS/SSL configuration assessment
- Certificate issues and protocol weaknesses
File import
Upload raw SSL Labs analyze JSON against the SSL Labs JSON source — parsing is handled by a dedicated built-in parser.
What Centraleyezer expects in the file
- The unmodified JSON returned by the SSL Labs v3 analyze endpoint for a host.
API connection
No credentials required — the public SSL Labs API is used. Assign the scanner to a project and every HTTPS website asset is analyzed on each run (the platform polls until each assessment is READY).
Configuration
Where to get the credentials
None — SSL Labs API v3 is free to use within Qualys’ fair-use limits.
What gets imported on every run
- TLS protocol and cipher suite weaknesses per endpoint.
- Certificate issues: expiry, chain and configuration problems.
How imported findings are risk-scored
Every SSL Labs 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.