Evidence-linked defensive vulnerability priorities, change signals, and known-exploited context—packaged for review queues, watchlists, and secure delivery.
Buyer decisionWhich source-backed vulnerabilities should enter our defensive review queue first?
These stale, official-source examples show how a buyer can review the feed. They are not the current release and do not disclose customer, watchlist, or private delivery data.
| Vendor / product | CVE | Known exploited | KEV added | Federal due date | Preview state |
|---|---|---|---|---|---|
| Apache Log4j2 | CVE-2021-44228 | Yes | Dec 10, 2021 | Dec 24, 2021 | Historical |
| Progress MOVEit Transfer | CVE-2023-34362 | Yes | Jun 2, 2023 | Jun 23, 2023 | Historical |
| Palo Alto PAN-OS | CVE-2024-3400 | Yes | Apr 12, 2024 | Apr 19, 2024 | Historical |
Every amount below is Introductory pricing for the exact scope shown. Buy a snapshot or monthly watch online; use the other options when your team needs configuration, analysis, or integration work.
For one-time analysis, internal evaluation, and a fixed reference date.
For teams maintaining a scoped defensive review queue as the source picture changes.
For organizations that need larger scopes, reviewed configuration, and an ongoing human delivery boundary.
For one buyer question, one approved source boundary, one compact evidence package, and one acceptance test.
For systems that need authenticated current-release checks and verified bundle retrieval.
Elkwai Data prioritizes deterministic release controls, source authority, and inspectable decisions before adding model-assisted enrichment.
Collect approved public inputs with timestamps, rights notes, and source identifiers.
Resolve records into a stable schema without redistributing raw source bodies.
Compare stable fingerprints and label new, updated, escalated, resolved, or unchanged states.
Use explainable urgency inputs to order review; never claim exploit probability.
Publish only after freshness, rights, schema, evidence, integrity, and delivery gates pass.
The product description and dated examples on this page are public. Current releases, private evidence, watchlists, and downloads require authentication and an active product entitlement. Authorized downloads remain subject to the product license.
Stripe sends a signed webhook. The backend verifies the raw event, records it idempotently, and provisions through a queue. The browser success redirect never grants access.
The Watch and Integration rails support buyer-approved vendors, products, geographies, and other scoped filters. Asset matching still requires a qualified owner and appropriate inventory inputs.
The last-known-good release remains current. Failed candidates are recorded for operations review and never replace the buyer delivery pointer.