How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Cisco XDR

Cisco XDR Vulnerability API

The Vulnerability API from Cisco XDR — 9 operation(s) for vulnerability.

Documentation Provider Profile APIs.io OpenAPI GitHub

Cisco XDR Vulnerability API is one of 83 APIs that Cisco XDR publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Vulnerability, Security, XDR, and Threat Detection. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 12 operations across 9 paths, and defines 16 schemas. It is described by OpenAPI 3.2.0, at version 4178275a824512c2fd3a2acdb0e8277233919054 v2.71.0.

Requests are made against a single base URL, /.

12 operations 9 paths 16 schemas 2 DELETE8 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
4178275a824512c2fd3a2acdb0e8277233919054 v2.71.0
Base URL
https://private.intel.amp.cisco.com
Authentication
API Key, OAuth 2.0
Contact
Cisco Security Business Group -- Advanced Threat
License
All Rights Reserved
Resource Areas
1

Authentication & Security 2

Cisco XDR Vulnerability API declares 2 security schemes for authenticating requests. An API key is passed in the header as Authorization (JWT). It supports OAuth 2.0 (oauth2) using the authorizationCode flow, exposing 6 scopes. By default, every request must be authenticated.

  • JWT — Ex: Bearer \

Paths & Operations 12

Across 9 paths, the API surfaces 12 operations — 2 DELETE, 8 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Vulnerability 12
GET
/ctia/vulnerability/cpe_match_strings
List Vulnerabilities with configurations matching CPE 2.3 match strings
13 params → 200
POST
/ctia/vulnerability
Adds a new Vulnerability
1 param body → 201
PUT
/ctia/vulnerability/{id}
Update an existing Vulnerability
2 params body → 200
GET
/ctia/vulnerability/{id}
Get one Vulnerability by ID
2 params → 200
DELETE
/ctia/vulnerability/{id}
Delete one Vulnerability
2 params → 204
GET
/ctia/vulnerability/external_id/{external_id}
List Vulnerability by external id
7 params → 200
GET
/ctia/vulnerability/search
Search for Vulnerability entities using a ES query syntax and field filters
16 params → 200
DELETE
/ctia/vulnerability/search
Delete Vulnerability entities matching given Lucene/ES query string or/and field filters
12 params → 200
GET
/ctia/vulnerability/search/count
Count Vulnerability matching a Lucene/ES query string and field filters
10 params → 200
GET
/ctia/vulnerability/metric/histogram
Histogram for some Vulnerability field
14 params → 200
GET
/ctia/vulnerability/metric/topn
Topn for some Vulnerability field
14 params → 200
GET
/ctia/vulnerability/metric/cardinality
Cardinality for some Vulnerability field
11 params → 200

Schemas 16

The contract defines 16 schemas that model the data the API accepts and returns. The most detailed are CVSSv3 (31 properties), PartialVulnerability (26 properties), NewVulnerability (26 properties), CVSSv2 (25 properties). Each schema is shown below with its type and property counts.

MetricResultFilters
object
2 properties 2 required
CPENode
object
4 properties 1 required
CVE
object
1 property 1 required
CPELeafNode
object
3 properties 2 required
CPEMatch
object
6 properties 2 required
PartialVulnerability
object
Indicates weakness or flaw in the system that can be exploited by an attacker to gain unauthorized access or cause harm to the system. Vulnerabilities can exis…
26 properties
VulnerabilityImpact
object
Describes the potential impact of a vulnerability that is being tracked in the system. Provides information on the extent of damage that a vulnerability can ca…
2 properties
CVSSv2
object
25 properties 3 required
CVEDataMeta
object
2 properties
ExternalReference
object
External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to…
5 properties 1 required
CVSSv3
object
31 properties 3 required
Configurations
object
Represents a list of affected versions or configurations of a software component that is impacted by a vulnerability. By tracking the affected software compone…
2 properties 2 required
NewVulnerability
object
a new Vulnerability
26 properties 1 required
MetricResultData
object
MetricResult
object
3 properties 3 required
Vulnerability
object
Indicates weakness or flaw in the system that can be exploited by an attacker to gain unauthorized access or cause harm to the system. Vulnerabilities can exis…
19 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

cisco-xdr-vulnerability-api-openapi.yml Raw ↑

Other APIs Cisco XDR publishes across the network.

Cisco XDR Actor API
AE Profile APIs.io
Cisco XDR Asset API
AE Profile APIs.io
Cisco XDR Asset Mapping API
AE Profile APIs.io
Cisco XDR Asset Properties API
AE Profile APIs.io
Cisco XDR Attack Pattern API
AE Profile APIs.io
Cisco XDR Bulk API
AE Profile APIs.io
Cisco XDR Bundle API
AE Profile APIs.io
Cisco XDR Campaign API
AE Profile APIs.io
Cisco XDR Casebook API
AE Profile APIs.io
Cisco XDR COA API
AE Profile APIs.io
Cisco XDR Deliberate API
AE Profile APIs.io
Cisco XDR Event API
AE Profile APIs.io
#Vulnerability#Security#XDR#Threat Detection
← Back to C APIs
API Details
ID
cisco-xdr:cisco-xdr-vulnerability-api
Base URL
https://private.intel.amp.cisco.com
Docs
https://developer.cisco.com/docs/cisco-xdr/
Provider
Cisco XDR
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=cisco-xdr-vulnerability-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/cisco-xdr-vulnerability-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Cisco XDR Vulnerability API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.