Normalized sources
CISA KEV, EUVD, GitHub Advisory, NVD, OSV and EPSS share one evidence model.
Emerging-threat relevance
A new vulnerability matters when it affects your service.
Threat Radar normalizes authoritative advisories, matches exact customer inventory and records whether an asset is affected, protected, unprotected or unknown.
What the current evidence supports
AegiFlow never converts an advisory directly into enforcement. Exact matching creates a case; shadow, canary and verification gates decide what happens next.
GoTe now
GoTe nowGoTePrivate beta · operator-assisted
- Traffic
- Checking current route
- Protection
- Unknown
- Runtime
- Unknown
- Scope
- Not verifiable
- Traffic proof until
- Not verifiable
Current state is shown only after a fresh, schema-validated snapshot is loaded.
Open status evidencePlatform capabilities
These cards describe product scope. Current delivery stage, runtime health, scope and freshness are reported separately from the validated public snapshot above.
Platform · implemented
Threat Coverage Ledger
Every conclusion carries evidence, confidence, inventory freshness and last verification.
SiteAV Connector
Signed outbound inventory exists; file integrity and runtime malware detection follow after isolation review.
02
How you use it in an operating workflow
The visitor path remains short. Configuration, verification and rollback stay visible to the operator at every stage.
Fast request pathParallele AnalyseEvidence before promotion
- 01
Ingest
Advisories are deduplicated and scored outside the request path.
- 02
Match
Packages and versions are compared with signed inventory.
- 03
Act safely
Relevant findings open one case and a guarded mitigation proposal.
The interface explains what is known, unknown and required
AegiFlow does not turn missing evidence into a reassuring zero. Every state links to its source, freshness and next action.
- Delivery stage
- Planned, implemented, verified, activatable or active.
- Runtime health
- Healthy, degraded, stale, unknown or unavailable — independently of delivery stage.
- Evidence
- Source, timestamp, scope and last successful verification.
- Action
- The responsible party, exact change and expected impact.
- Way back
- Rollback instructions are defined before an active change.
In depth
How this capability behaves in production — grounded in the platform's documented, current operation.
Many advisories, one honest question
Threat Radar normalizes CISA KEV, NVD, GitHub Advisory, OSV and ENISA EUVD into one evidence model, scored with EPSS. The live snapshot supplies the current catalogue count. The question that matters is: does this match the exact packages and versions the service runs?
The Coverage Ledger refuses to bluff
For every advisory-service pair, the ledger records affected, protected, not affected — or unknown. Unknown stays visible until the inventory is fresh enough to answer. No advisory silently deploys a virtual patch, and no stale inventory is presented as safety.
Start without changing traffic. Activate only measured controls.
Ownership, certificate, origin health and rollback must pass before traffic protection changes.