/cisa/ics-advisories/search

POST /api/cisa/ics-advisories/search

Price: 20 credits

Search CISA industrial control systems advisories by vendor, topic, series and year

How to use it

Use this to find ICS/OT advisories, then read each hit in full from the same response — no follow-up call per advisory is needed. vendor, topic, year and advisory_type narrow to exactly the advisories CISA files under that term and combine with each other, so vendor=Siemens with year=2020 returns only the Siemens advisories CISA dates to 2020 — for an advisory CISA revised, that is the revision year rather than release_date. query is a separate full-text match over the advisory text. vendor and topic must be spelled as CISA writes them and are rejected otherwise. Sorting is by release date or by vendor name; CISA publishes no revision date on this list, so ordering by last update is not offered.

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, vendor and body (examples: "siemens", "pump controller")
• advisory_type string nullable — Restrict to one of CISA's ICS advisory series (one of: "ics_advisory", "ics_medical_advisory", "ics_alert")
• vendor string nullable — Vendor name exactly as CISA files it on the ICS advisory list (examples: "Siemens", "Rockwell Automation")
• topic string nullable — CISA topic the advisory is filed under (examples: "Medical Technology")
• year integer nullable — Calendar year CISA dates the advisory to on its own list — for an advisory CISA later revised this is the year of the revision, which can be later than release_date (examples: 2015; min: 1990; max: 2100)
• sort string — Order the advisories are returned in (default: "release_date"; one of: "release_date", "vendor_name")
• count integer required — Max result count (examples: 10; min: 1; max: 400)

Response

• @type string (default: "CisaIcsAdvisory")
• id string required
• name string nullable
• description string nullable
• web_url string nullable
• csaf_url string nullable
• advisory_type string nullable
• severity string nullable
• release_date string nullable
• updated_date string nullable
• tracking_version string nullable
• tracking_status string nullable
• category string nullable
• csaf_version string nullable
• language string nullable
• tlp_label string nullable
• distribution_text string nullable
• publisher_name string nullable
• publisher_category string nullable
• publisher_namespace string nullable
• publisher_contact_details string nullable
• aliases array (default: [])
• cve_ids array (default: [])
• notes array (default: [])
  • @type string (default: "CisaCsafNote")
  • category string nullable
  • name string nullable
  • text string nullable
  • audience string nullable
• references array (default: [])
  • @type string (default: "CisaCsafReference")
  • category string nullable
  • summary string nullable
  • url string nullable
• acknowledgments array (default: [])
  • @type string (default: "CisaCsafAcknowledgment")
  • names array (default: [])
  • organization string nullable
  • summary string nullable
  • urls array (default: [])
• revisions array (default: [])
  • @type string (default: "CisaCsafRevision")
  • number string nullable
  • date string nullable
  • legacy_version string nullable
  • summary string nullable
• products array (default: [])
  • @type string (default: "CisaCsafProduct")
  • product_id string required
  • name string nullable
  • vendor string nullable
  • product_family string nullable
  • version string nullable
  • cpe string nullable
  • model_numbers array (default: [])
  • serial_numbers array (default: [])
  • skus array (default: [])
  • generic_uris array (default: [])
    • @type string (default: "CisaCsafGenericUri")
    • namespace string nullable
    • uri string nullable
• vulnerabilities array (default: [])
  • @type string (default: "CisaCsafVulnerability")
  • cve_id string nullable
  • name string nullable
  • cwe_id string nullable
  • cwe_name string nullable
  • affected_product_ids array (default: [])
  • notes array (default: [])
    • @type string (default: "CisaCsafNote")
    • category string nullable
    • name string nullable
    • text string nullable
    • audience string nullable
  • references array (default: [])
    • @type string (default: "CisaCsafReference")
    • category string nullable
    • summary string nullable
    • url string nullable
  • remediations array (default: [])
    • @type string (default: "CisaCsafRemediation")
    • category string nullable
    • details string nullable
    • url string nullable
    • date string nullable
    • product_ids array (default: [])
    • group_ids array (default: [])
  • scores array (default: [])
    • @type string (default: "CisaCsafScore")
    • version string nullable
    • base_score number nullable
    • base_severity string nullable
    • vector_string string nullable
    • temporal_score number nullable
    • temporal_severity string nullable
    • environmental_score number nullable
    • environmental_severity string nullable
    • product_ids array (default: [])
• text string nullable
• tags array (default: [])
  • @type string (default: "CisaAdvisoryTag")
  • name string required
  • values array (default: [])

Errors

• 422 — vendor or topic does not match any name CISA files advisories under; spell it as CISA does. Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit 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 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 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 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 Wait at least 30 seconds, then retry.

Response 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.