Course contentsShow
← Cloud and Infrastructure
Lesson 1085 of 2,98921. Container RegistriesFree lesson

Continuous Vulnerability Monitoring

Ongoing scanning of stored images as new vulnerabilities are disclosed and alerting on newly discovered risks.

Continuous Vulnerability Monitoring

What you'll learn: How to automatically track and alert on new vulnerabilities in your stored container images, even after they've been pushed to your registry.

The Challenge: Images Age Like Milk, Not Wine

When you scan an image at build time, you only know about vulnerabilities that exist at that moment. But security researchers discover new vulnerabilities every day. An image that was "clean" yesterday might be critically vulnerable today—without changing a single byte.

What Is Continuous Monitoring?

Continuous vulnerability monitoring is the practice of repeatedly scanning stored images in your registry as new vulnerability databases are updated. Instead of scanning once during push, the registry (or an integrated security tool) automatically re-scans all stored images on a schedule—daily, hourly, or whenever new CVE (Common Vulnerabilities and Exposures) data becomes available.

Think of it like a smoke detector that constantly checks the air, rather than just once when you move into a house.

How It Works

  1. Baseline scan: Image is scanned when first pushed
  2. Scheduled re-scans: Registry periodically re-analyzes the same image layers against updated vulnerability databases
  3. Delta detection: System compares new scan results with previous ones
  4. Alerting: When a new vulnerability is found, teams receive notifications (email, Slack, webhook, etc.)
  5. Policy enforcement: Optionally block deployment of newly-vulnerable images

This process happens automatically in the background without requiring developers to rebuild or re-push images.

Why It Matters

Images sitting in your registry for weeks might be running in production. Continuous monitoring ensures you discover when those running images become vulnerable, enabling proactive patching before exploitation.

Key Takeaway: Continuous vulnerability monitoring automatically re-scans stored registry images against updated threat databases, alerting teams when previously-clean images develop new security risks over time.