Market validation

Cyber Vulnerability Change Feed

A proposed normalized API for teams that need lightweight CVE, KEV, severity, and product watchlist changes in automation-friendly JSON.

GET /v1/cyber/vulnerabilities/changes?cpe=nginx&hasKev=true&since=2026-07-01
{
  "data": [
    {
      "cveId": "CVE-2026-0001",
      "severity": "critical",
      "knownExploited": true,
      "publishedAt": "2026-07-02",
      "matchedProducts": ["sample:nginx"]
    }
  ],
  "meta": { "sampleOnly": true, "market": "cyber-vulnerability" }
}

Validation Thesis

This concept is only built further if tracked requests, demo clicks, or marketplace intent justify the build.

Public Data Sources

The initial product would normalize public records into stable polling endpoints and exports.

Buyer Workflows

These are the specific self-serve workflows this page is testing before any backend is built.

Known-exploited polling

Poll for newly added or modified known-exploited vulnerability records without maintaining a local parser.

Product watchlists

Monitor vendor and product names that matter to an MSP, SaaS operator, or internal security dashboard.

Severity change alerts

Detect when public CVE records change severity, references, or exploitation status.

Specific Workflow Tests

These pages test sharper buyer searches before implementation.

Monetization Hypothesis

Pricing only becomes meaningful after tracked demand appears. The first offer should stay narrow and low-touch.

Validation FAQ

Would this replace a threat-intelligence platform?

No. The target product is a lightweight public-data change feed for automation, not a full threat-intelligence suite.

How would false positives be handled?

Responses would include source records and match basis so callers can verify product and version evidence.