TotulDigital
EN
Client Portal Get Started
HELP ARTICLE • Updated 8 October 2026

Vulnerabilities and hardening

Two lists keep a server honest: the software it runs with known vulnerabilities, and the configuration checks it fails.

PART 01

Vulnerabilities

Each sensor reports the installed packages. They are matched against published vulnerabilities (CVEs) for that operating system and ranked by severity: Critical, High, Medium, Low, and Unscored where no score is published yet.

Start with the critical ones on machines exposed to the internet; Topology shows which those are. Most fixes are a package update, and a kernel fix needs a reboot before it counts.

When a fixed package still showsA vulnerability can stay listed when a distribution ships its fix under a version the matching does not recognise, for example a backported kernel. Check the distribution's own security tracker; tell us and we will mark it.
PART 02

Hardening (CIS benchmarks)

Every machine is checked against the CIS benchmark for its system, every few hours. The score is the share of checks passed. Each failing check says why it matters, how to fix it, and which framework controls it supports.

ScoreReading
80% and aboveAt target.
60–79%Needs attention.
Below 60%Weak: the default installation of most systems lands here.
KEEP READING

Related

Compliance and evidenceHow checks become controls. Adding serversBring more machines in.
SUPPORT

Still stuck?

Write to us with what you tried and what you saw. A person answers, in writing, on business days.