[Integrations](https://spiral.ai/integrations) › [dots](https://spiral.ai/integrations/dots) › [CISA KEV vulnerability search](https://spiral.ai/integrations/dots/cisa-kev-vulnerability-search)

# How to Use CISA KEV vulnerability search in dots

Find CISA catalog records for a vendor, product, weakness, or date range, including descriptions, required actions, and due dates. Use it to investigate a technology's known exploited vulnerabilities without starting with CVE IDs.

|  |  |
| --- | --- |
| Model | CISA KEV vulnerability search |
| Available through | Alexandria |
| Category | Developer |
| Price | $0.00873 per call. |
| Returns | json |
| Runs | In the background |
| Setup | About 2 minutes, with a Spiral API key |

## Prompts to try with CISA KEV vulnerability search in dots

- Every Monday, use CISA KEV vulnerability search for Fortinet FortiOS and report changes in required actions, due dates, or ransomware status compared with the previous review.
- Every weekday, use CISA KEV vulnerability search for Ivanti Connect Secure and list returned records with due dates in the next seven days, followed by records whose dates have passed.
- Every Monday at 9am: use CISA KEV vulnerability search to look this up and give me the result as a table.
- Pull the latest numbers from CISA KEV vulnerability search and tell me what changed since last week.
- Check CISA KEV vulnerability search and summarize what you find in three bullet points.

## How to set up CISA KEV vulnerability search in dots

Pick the way that suits you. Each takes about two minutes.

### Use the Spiral skill

1. **Send dots this message**: Your agent reads Spiral's skill and sets itself up.

```
set up https://spiral.ai/SKILL.md
```

2. **Sign in or paste a key**: Approve Spiral in the browser, or give the agent a key from the console.

### Use Spiral's MCP server

1. **Create an API key**: In the console, open API keys and create a key for your dot. Copy it.

2. **Send your dot this message**: Your dot reads Spiral's skill and asks for your API key.

```text
set up https://spiral.ai/SKILL.md
```

3. **Give your dot the key**: When your dot asks for the key, add it where your dot keeps secrets, never in the chat itself.

### Use the Spiral CLI

1. **Install and sign in**: Installs the Spiral CLI, signs you in and adds its skill to your coding agents.

```bash
npx -y spiral-cli@latest init
```

### Call the Spiral API

1. **Create an API key**: In the console, under API keys.

2. **Run CISA KEV vulnerability search**: One request; the result comes back by polling or a webhook.

```bash
curl https://api.spiral.ai/v1/runs \
  -H "Authorization: Bearer $SPIRAL_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
    "provider": "alexandria",
    "model": "cisa-gov/vulnerabilities/kev_search",
    "input": {
      "cwe": "<cwe>"
    }
  }'
```

Then paste one of the prompts above: dots finds CISA KEV vulnerability search on Spiral, shows the price and runs it.

Setup guide in the docs: https://spiral.ai/docs/quickstarts/dots

## CISA KEV vulnerability search tools and prices

- [CISA Known Exploited Vulnerabilities (KEV) catalog · Kev search](https://spiral.ai/tools/alexandria/cisa-gov/vulnerabilities/kev_search) (Alexandria): $0.00873 per call.

## Settings you can ask for

| Setting | Allowed values | Default | Description |
| --- | --- | --- | --- |
| cwe |  | — | CWE id, CWE-79 or 79. Pattern: ^\s*([Cc][Ww][Ee]-)?[0-9]{1,6}\s*$. |
| url |  | — | A pasted cisa.gov KEV catalog page, print page, /kev or feed URL; its search_api_fulltext and field_cve values join query. Pattern: ^https?://. |
| query |  | — | Words that must all appear (case-insensitive) in the CVE id, vendor, product, vulnerability name or description: 'Roundcube', 'remote code execution', 'CVE-2024'. |
| cursor |  | — | next_cursor from a previous page of the same search. |
| due_to |  | — | Latest federal due date, YYYY-MM-DD, inclusive. Pattern: ^\s*[0-9]{4}-[0-9]{2}-[0-9]{2}\s*$. |
| vendor |  | — | Case-insensitive substring of the vendor or project: Ivanti, Microsoft, Apache. |

## What can you do with CISA KEV vulnerability search in dots?

Maintain a recurring review queue of relevant CISA KEV records and their remediation deadlines. A scheduled agent can check new additions or revisit selected CVEs and products to flag changes in required actions or ransomware status.

### Prioritize scanner findings

Match scanner CVEs against CISA records and put confirmed KEV matches into a remediation review with the required actions and due dates.

### Prepare patch tickets

Turn relevant catalog records into ticket drafts containing the CVE, affected product, vulnerability description, required action, and supporting references.

### Review ransomware exposure

Identify records marked as known ransomware use within a CVE list, recent additions, or a vendor review, then compare affected products with the organization's inventory.

### Plan remediation work

Arrange relevant KEV records by due date and required action to prepare a patch planning meeting.

### Write technology-specific security briefings

Summarize exploited vulnerabilities affecting technologies such as Microsoft Exchange, Ivanti Connect Secure, or Apache Log4j, with descriptions and remediation references.

### Review recurring software weaknesses

Organize relevant KEV records by their reported CWE codes to support an engineering discussion about recurring weakness types.

### Prepare a vendor remediation review

Collect relevant records for a software supplier and use CISA's required actions and linked references to prepare specific questions about remediation.

## Overview

- [Alexandria](https://spiral.ai/providers/alexandria)
- [All dots guides](https://spiral.ai/integrations/dots)

## CISA KEV vulnerability search in other agents

- [Amp](https://spiral.ai/integrations/amp/cisa-kev-vulnerability-search)
- [ChatGPT](https://spiral.ai/integrations/chatgpt/cisa-kev-vulnerability-search)
- [Claude](https://spiral.ai/integrations/claude-desktop/cisa-kev-vulnerability-search)
- [Claude Code](https://spiral.ai/integrations/claude-code/cisa-kev-vulnerability-search)
- [Cline](https://spiral.ai/integrations/cline/cisa-kev-vulnerability-search)
- [Codex](https://spiral.ai/integrations/codex/cisa-kev-vulnerability-search)
- [Cursor](https://spiral.ai/integrations/cursor/cisa-kev-vulnerability-search)
- [Devin](https://spiral.ai/integrations/devin/cisa-kev-vulnerability-search)
- [Factory Droid](https://spiral.ai/integrations/factory-droid/cisa-kev-vulnerability-search)
- [Gemini](https://spiral.ai/integrations/gemini/cisa-kev-vulnerability-search)
- [Gemini CLI](https://spiral.ai/integrations/gemini-cli/cisa-kev-vulnerability-search)
- [Google Antigravity](https://spiral.ai/integrations/antigravity/cisa-kev-vulnerability-search)
- [goose](https://spiral.ai/integrations/goose/cisa-kev-vulnerability-search)
- [Grok](https://spiral.ai/integrations/grok/cisa-kev-vulnerability-search)
- [Grok Build](https://spiral.ai/integrations/grok-build/cisa-kev-vulnerability-search)
- [Hermes](https://spiral.ai/integrations/hermes/cisa-kev-vulnerability-search)
- [Instinct](https://spiral.ai/integrations/instinct/cisa-kev-vulnerability-search)
- [Manus](https://spiral.ai/integrations/manus/cisa-kev-vulnerability-search)
- [Muse](https://spiral.ai/integrations/muse/cisa-kev-vulnerability-search)
- [Muse Code](https://spiral.ai/integrations/muse-code/cisa-kev-vulnerability-search)
- [n8n](https://spiral.ai/integrations/n8n/cisa-kev-vulnerability-search)
- [Notion](https://spiral.ai/integrations/notion/cisa-kev-vulnerability-search)
- [OpenClaw](https://spiral.ai/integrations/openclaw/cisa-kev-vulnerability-search)
- [opencode](https://spiral.ai/integrations/opencode/cisa-kev-vulnerability-search)
- [Perplexity](https://spiral.ai/integrations/perplexity/cisa-kev-vulnerability-search)
- [Raycast](https://spiral.ai/integrations/raycast/cisa-kev-vulnerability-search)
- [VS Code](https://spiral.ai/integrations/vscode/cisa-kev-vulnerability-search)
- [Windsurf](https://spiral.ai/integrations/windsurf/cisa-kev-vulnerability-search)
- [Zapier](https://spiral.ai/integrations/zapier/cisa-kev-vulnerability-search)

## More dots guides

- [CISA KEV recent additions](https://spiral.ai/integrations/dots/cisa-kev-recent-additions)
- [CVE.org CNA directory](https://spiral.ai/integrations/dots/cve-org-cna-directory)
- [CISA KEV CVE lookup](https://spiral.ai/integrations/dots/cisa-kev-cve-lookup)
- [CVE.org recent CVE changes](https://spiral.ai/integrations/dots/cve-org-recent-cve-changes)
- [Artificial Analysis model search](https://spiral.ai/integrations/dots/artificial-analysis-model-search)
- [CVE.org vulnerability record](https://spiral.ai/integrations/dots/cve-org-vulnerability-record)

## Questions about CISA KEV vulnerability search in dots

**Can dots use CISA KEV vulnerability search?**

Yes. Add Spiral to dots as an MCP server, and dots can find and run CISA KEV vulnerability search like any built-in tool.

**How much does CISA KEV vulnerability search cost in dots?**

$0.00873 per call. You pay from your Spiral balance as you go, with no subscription, and a failed run is not charged. Your dots plan is separate.

**Do I need an Alexandria account to use CISA KEV vulnerability search in dots?**

You need no Alexandria account. dots uses one Spiral API key for every tool, and Spiral runs CISA KEV vulnerability search on its own Alexandria account.

**How long does it take to set up CISA KEV vulnerability search in dots?**

About two minutes: create an API key, then send your dot this message, then give your dot the key.

**Does dots wait while CISA KEV vulnerability search runs?**

CISA KEV vulnerability search runs in the background. dots starts the run, checks on it and gives you the json when it's ready.

**Does CISA KEV contain every disclosed vulnerability?**

No. CISA requires reliable evidence of exploitation in the wild and a clear remediation action before inclusion, so KEV covers a narrower set of vulnerabilities.

**How often does CISA update the catalog?**

Updates typically happen on weekdays during normal US Eastern business hours when CISA has new or updated entries. That is a typical publishing pattern, not a fixed daily release.

**Does the date added show when exploitation began?**

No. It records when CISA added the vulnerability to KEV, so a recent addition does not establish a recent discovery or first attack.

**Does Unknown ransomware status mean no ransomware use?**

No. CISA defines Unknown as lacking confirmation that the vulnerability has been used for ransomware.

**Can I see how an existing KEV record changed?**

The catalog file has no accessible inline revision log. CISA's public GitHub repository preserves commit history that can help identify changes to existing entries.

