# CISA KEV Inventory Crosswalk & Changes (`usta/kev-cve-inventory-crosswalk`) Actor

For vulnerability analysts: join up to 10,000 supplied asset/CVE pairs to the official CISA KEV catalog. Track changes against your prior snapshot, retain source evidence and separate invalid IDs. No scanning or safety verdict.

- **URL**: https://apify.com/usta/kev-cve-inventory-crosswalk.md
- **Developed by:** [US Tech Automations](https://apify.com/usta) (community)
- **Categories:** Developer tools
- **Stats:** 1 total users, 0 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$5.00 / 1,000 evaluated inventory pairs

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## CISA KEV Inventory Crosswalk & Changes

Turn a supplied CVE watchlist into source-linked evidence for each asset reference. This Actor is for vulnerability analysts who need structured joins and repeatable comparisons outside their existing vulnerability-management platform.

**Run the synthetic sample**, then replace its opaque references and CVE IDs with your own approved inventory. The Actor does not connect to, scan or inspect those assets.

### What you receive

One dataset row per unique, valid asset/CVE pair: KEV membership, source catalog version and release time, source hash, CISA record fields and the change against your supplied previous snapshot. Different assets associated with the same CVE remain separate rows. Repeated identical pairs within one run produce one row.

Changes are BASELINE, UNCHANGED, ADDED\_TO\_KEV, NO\_LONGER\_IN\_CURRENT\_CATALOG or KEV\_RECORD\_CHANGED. A missing current catalog entry is not proof that a vulnerability was fixed, that an asset is safe, or that CISA formally withdrew a record. Supplied asset associations and historical snapshots are not independently certified. CISA dates are reported as source fields; their applicability to your organization is not determined.

Read OUTPUT first. EVALUATED means the declared pairs were evaluated; PARTIAL means invalid identifiers or a delivery limit left gaps. UNKNOWN means source coverage could not be established, never a clean result. A catalog more than seven days old, over five minutes in the future, or older than your supplied evidence produces UNKNOWN and no new paid rows. This conservative freshness policy can withhold a catalog even when CISA has simply published no update.

### Price

**0.005 USD per delivered unique asset/CVE evaluation, with no Actor start fee.** Both listed and unlisted pairs are evaluations. Unchanged results are charged on another run. Invalid identifiers, duplicate pairs within a run and failed source evaluation produce no paid row. At most 10,000 pairs are accepted: a full run costs at most 50 USD in Actor event charges. Set your Apify run charge limit before starting; platform/account terms apply. The underlying CISA feed is free. You pay for the inventory join, comparison and delivered evidence.

### Inputs and repeated runs

Input is at most 5 MiB. Supply 1–10,000 objects containing only `asset_ref` and `cve_id`. An asset reference is 1–80 letters, numbers, underscores or hyphens. CVE IDs are normalized to uppercase. Invalid CVE formats appear in the private UNRESOLVED record and produce no dataset row.

For changes, paste the previous private NEXT\_SNAPSHOT array into `previousSnapshot`. Without it, the run establishes a baseline. After a capped run, NEXT\_SNAPSHOT advances only rows actually delivered and preserves supplied prior evidence for undelivered current pairs. Re-running all pairs evaluates and charges them again; submit only the pairs you intend to reevaluate. DELIVERY\_UNKNOWN or DELIVERY\_RECONCILIATION\_REQUIRED requires inspecting the existing dataset and charge record before another run. A resumed run does not automatically replay an ambiguous delivery.

### Privacy and limits

The two input arrays use Apify encrypted input fields. Before reading input or writing output, the Actor restricts the run, default dataset and key-value storage, then checks that unauthenticated requests are denied. If access remains available or cannot be checked, it stops. Output links require authorized access; this Actor does not expose signed public download links. Apify and authorized account users still process the data. Use opaque identifiers; do not submit credentials, hostnames, personal information or confidential advisory text. Storage retention follows your Apify account settings; delete the run's data when no longer needed.

Only the fixed official CISA GitHub mirror is fetched, with no redirects and a 5 MiB source limit. No arbitrary URL collection, exploit checks, patch verification, legal interpretation, automatic remediation, alerts or claims of comprehensive vulnerability coverage are included. If your existing platform already supplies this inventory join and history, its native workflow may be sufficient.

Source: [CISA KEV official repository](https://github.com/cisagov/kev-data), CC0. This product is independent of CISA. For reproducible errors, use the Actor Issues tab with a run ID and synthetic reproduction; do not post customer inventory. No response-time or security-outcome guarantee is made.

# Actor input Schema

## `inventory` (type: `array`):

1–10,000 objects with only asset\_ref and cve\_id. Use opaque letters/numbers/underscore/hyphen references, not hostnames, URLs, credentials or personal data. Each delivered unique pair costs 0.005 USD per evaluation.

## `previousSnapshot` (type: `array`):

Paste the private NEXT\_SNAPSHOT array from your earlier run to compare changes. Leave empty for baseline. Supplied historical evidence is not independently certified.

## Actor input object example

```json
{
  "inventory": [
    {
      "asset_ref": "example-asset-1",
      "cve_id": "CVE-2021-27104"
    },
    {
      "asset_ref": "example-asset-2",
      "cve_id": "CVE-2024-99999"
    }
  ]
}
```

# Actor output Schema

## `inventory` (type: `string`):

No description

## `status` (type: `string`):

No description

## `snapshot` (type: `string`):

No description

## `unresolved` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "inventory": [
        {
            "asset_ref": "example-asset-1",
            "cve_id": "CVE-2021-27104"
        },
        {
            "asset_ref": "example-asset-2",
            "cve_id": "CVE-2024-99999"
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("usta/kev-cve-inventory-crosswalk").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "inventory": [
        {
            "asset_ref": "example-asset-1",
            "cve_id": "CVE-2021-27104",
        },
        {
            "asset_ref": "example-asset-2",
            "cve_id": "CVE-2024-99999",
        },
    ] }

# Run the Actor and wait for it to finish
run = client.actor("usta/kev-cve-inventory-crosswalk").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "inventory": [
    {
      "asset_ref": "example-asset-1",
      "cve_id": "CVE-2021-27104"
    },
    {
      "asset_ref": "example-asset-2",
      "cve_id": "CVE-2024-99999"
    }
  ]
}' |
apify call usta/kev-cve-inventory-crosswalk --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,usta/kev-cve-inventory-crosswalk"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/nvhxFG53wMACRQWAh/builds/mwbTJHGt37pcvPCdr/openapi.json