← klaro.services
SentinelConsentraKlaroShieldBundlesPricing

Continuous vulnerability management

Finding a vulnerability is the easy part. Vulnerability management is what happens after — tracking it, fixing it, and proving the fix actually worked.

Scan reports pile up. Vulnerabilities don't get fixed.

A one-time scan produces a PDF that gets read once and forgotten. Without tracked ownership, deduplication across repeated scans, and a way to confirm a fix actually worked, findings either get lost or get "fixed" without verification.

How Klaro approaches vulnerability management

  • •Continuous scanning of authorised web applications, not a single assessment.
  • •Findings are deduplicated across scans — the same issue found twice never shows up as two separate items.
  • •A full lifecycle: New → Open → Acknowledged → In Progress → Resolved → Verified, plus False Positive and Accepted Risk states.
  • •A finding is never silently marked fixed — it takes repeated clean scans to auto-resolve, and a dedicated rescan to reach Verified.
  • •Downloadable reports for sharing status with stakeholders or auditors.
Vulnerability management is part of Sentinel, alongside compliance readiness and business assurance.
Explore Sentinel →

Common questions

What is the difference between vulnerability scanning and penetration testing?
Scanning is automated and continuous, covering a broad surface on an ongoing basis. Penetration testing is manual, deeper, and typically point-in-time. Klaro provides continuous scanning and management, not manual penetration testing.
How does Klaro know a finding is actually fixed?
A finding only moves to Resolved after repeated scans no longer detect it, and only reaches Verified after a dedicated confirmation rescan.
Do I need to authorise scanning before it starts?
Yes — active scanning against any asset requires explicit authorisation, logged with a timestamp, before it runs.
Security monitoring →Compliance →Pricing →