# /cisa/advisories/search

`POST /api/cisa/advisories/search`

Price: 20 credits

Search CISA cybersecurity advisories, alerts and malware analysis reports

## How to use it

Use this to find CISA's joint advisories on a threat actor, sector or technique and read each hit in full from the same response. sector, topic, audience, partner, nation_state_actor, attack_ttp and vendor take CISA's own tag wording; a rejection carries no suggestion, so query is the safer choice when you are unsure of the exact tag. attack_ttp also accepts a bare ATT&CK id. Results always come back newest first, and the alerts among them carry a cisa.gov path rather than an alert code as their id.

## Parameters

- `access-token` (string, required)

## Request body

- `timeout` (integer) — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
- `query` (string, nullable) — Full-text query matched against the advisory title and body (examples: "log4j", "ransomware")
- `advisory_type` (string, nullable) — Restrict to one of CISA's advisory series (one of: "alert", "cybersecurity_advisory", "malware_analysis_report")
- `year` (integer, nullable) — Calendar year the advisory was released (examples: 2021; min: 1990; max: 2100)
- `sector` (string, nullable) — Critical infrastructure sector the advisory is tagged with (examples: "Communications Sector")
- `topic` (string, nullable) — CISA topic the advisory is filed under (examples: "Nation-State Threats")
- `audience` (string, nullable) — Audience CISA addresses the advisory to (examples: "Federal Government")
- `partner` (string, nullable) — Co-sealing agency or partner on the advisory (examples: "Federal Bureau of Investigation")
- `nation_state_actor` (string, nullable) — Nation-state actor the advisory attributes activity to (examples: "Russia")
- `attack_ttp` (string, nullable) — MITRE ATT&CK tactic or technique the advisory is tagged with, by name or by id (examples: "Brute Force", "T1110")
- `vendor` (string, nullable) — Vendor the advisory is filed against (examples: "Siemens")
- `count` (integer, required) — Max result count (examples: 10; min: 1; max: 400)

## Response

### 200 — Successful Response

- `@type` (string) (default: "CisaAdvisory")
- `id` (string, required)
- `name` (string, nullable)
- `web_url` (string, nullable)
- `advisory_type` (string, nullable)
- `release_date` (string, nullable)
- `updated_date` (string, nullable)
- `description` (string, nullable)
- `text` (string, nullable)
- `cve_ids` (array) (default: [])
- `attack_technique_ids` (array) (default: [])
- `attack_tactic_ids` (array) (default: [])
- `tags` (array) (default: [])
  - `@type` (string) (default: "CisaAdvisoryTag")
  - `name` (string, required)
  - `values` (array) (default: [])
- `related_advisory_ids` (array) (default: [])

## Errors

### 422 — Validation Error

A filter value CISA does not tag advisories with.

What to do: Check the fields against this schema. A URN with the wrong prefix is the most common cause.

- `detail` (array)
  - `loc` (array, required)
  - `msg` (string, required)
  - `type` (string, required)
  - `input` (any)
  - `ctx` (object)

### 408

The request ran past its time limit

What to do: Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.

### 412

The entity was not found, or a precondition failed

What to do: Retrying will not help: either the entity does not exist, or the input points at a different one.

### 429

Too many requests: a rate limit or a usage window is exhausted

What to do: When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.

### 500

Something broke on our side

What to do: Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.

### 529

Rate limit reached, or the endpoint is overloaded

What to do: Wait at least 30 seconds, then retry.

## Response envelope

Success: Array of objects (may be empty if no results)

Error: Error may coexist with partial results if it occurs mid-execution. Check X-Error header and status code.

Every response carries these headers:

- `X-Error` — Error message text (present only on error)
- `X-Request-ID` — Unique request identifier
- `X-Execution-Time` — Execution time in seconds
- `X-Result-Count` — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
- `X-Total-Available-Results` — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
- `X-Warning` — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
- `X-Retry-After` — Seconds to wait before retrying. Present only on 429.