Staying Secure & Up to Date – Part 3: Toolbox – Scanners, Databases & Sources

Category: Projects / CVE Check | Reading time: ~6 minutes
Toolbox with scanner magnifier, database cylinder and security advisories
Series overview: In part 2 you inventoried your systems. Today you build the toolbox: the tools and sources to answer “Is something known about this?”.

“How do I actually check all of this?”

You only need three tools:

1. Trivy – an open-source scanner that checks your containers (later also system packages) against known CVEs, automatically.

2. A scan database – the knowledge Trivy checks against; downloaded automatically on first run.

3. Two watchlists online: the CISA KEV feed (actually attacked flaws) and the NVD API (NIST’s official CVE database). Both are free and perfect for checking news yourself.

Install Trivy (5 minutes, any Linux)

curl -sfL https://raw.githubusercontent.com/aquasecurity/trivy/main/contrib/install.sh | sudo sh -s -- -b /usr/local/bin
trivy --version

Beginner tip: on Ubuntu/Debian you can also do sudo apt install trivy. The first scan downloads the CVE database (a few minutes, needs internet).

What the three sources do

🎯 CISA KEV – “the topic of the day”: flaws that are being actively exploited right now. Weekly updates, publicly available. Golden rule remains: if something there affects your software → act now.

🧠 NVD API – “the encyclopedia”: the official US database of all registered CVEs. Description, severity (CVSS score), affected versions. Query it directly:

https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-109618

🇩🇪 CERT-Bund / WID – German warnings from the BSI. Often redundant for individuals, nice if you prefer German sources.

Assessing severity, reachability and affected software together

Reading CVSS scores (beginner shortcut)

Almost every advisory has a number like CVSS 9.8. Here’s how to classify:

| Value  | Meaning                       | Reaction         |
|--------|-------------------------------|------------------|
| 9.0–10 | Critical, often unauthenticated | update now      |
| 7.0–8.9| High, serious impact           | schedule soon   |
| 4.0–6.9| Medium                        | keep normal rhythm |
| 0–3.9  | Low                           | watch           |
Remember: CVSS is orientation, not judgement. A “critical” score in a component you don’t use is less severe than a “medium” one at your internet entry point. The practical combination of part 4 (scanning) and part 5 (KEV matching) automates exactly that weighing.

Your first mini-test (aha moment)

With one command you can already check any software – e.g. your whole system:

sudo trivy fs --severity HIGH,CRITICAL /

Scans installed packages (a few minutes). Result table: package name, CVE IDs, severity, and the Fixed Version column – exactly the principle we use for Docker containers in the next part.


Pro Corner

• Trivy modes in one line: trivy image, trivy fs, trivy repo; add --severity HIGH,CRITICAL --no-progress for scripts.

• Databases: the CVE DB updates regularly; for offline use check --download-db-only and the airgap docs.

• KEV feed is machine-readable: known_exploited_vulnerabilities.json contains cveID, vendorProject, product, dateAdded. A small Python json parse is enough for automated matching (part 5 provides the ready script).

• Use scores with caveats: the NVD number is just a number; real risk depends heavily on context (internet-exposed? component unused?). EPSS complements CVSS for large estates.


Why this matters: with Trivy + KEV + NVD you have what professionals use – just as three free building blocks instead of expensive products.

Next part: Part 4 – Scanning containers with Trivy. Back to the overview via the menu (Part 0).

AI Assisted AI Assisted