canonical: https://jentic.com/apis/cisco.com/cisco # Cisco PSIRT openVuln API Jentic publishes the only available OpenAPI specification for Cisco PSIRT openVuln API, keeping it validated and agent-ready. The Cisco PSIRT openVuln API delivers Cisco Security Vulnerability information in machine-consumable formats (CVRF and OVAL), so security teams and AI agents can monitor advisories without scraping the Cisco website. It exposes 19 GET endpoints that retrieve advisories by CVE ID, advisory ID, severity, year, product, and IOS/IOS XE platform. Access is OAuth 2.0 client-credentials, with tokens issued by cloudsso.cisco.com after registering an application at apiconsole.cisco.com. ## For AI agents Pull Cisco security advisories in CVRF or OVAL format by CVE, severity, year, or product, so an agent can triage Cisco vulnerabilities and feed them into a SIEM or ticketing system. ## Scope Does not handle device configuration, network telemetry, or non-Cisco vulnerability data - use for retrieving Cisco PSIRT security advisories only. ## Capabilities - Retrieve a specific Cisco security advisory in CVRF format by advisory ID - Look up Cisco advisories by CVE ID to map a public CVE to Cisco's response - Filter advisories by severity (critical, high, medium, low) for prioritised triage - Pull advisories by year for batch ingestion into a vulnerability tracker - Retrieve advisories that affect a specific Cisco product or IOS/IOS XE release - Fetch the latest N CVRF or OVAL advisories for daily monitoring jobs ## Use cases ### Daily Cisco vulnerability ingest into a SIEM A security operations team polls /security/advisories/cvrf/latest/{number} every morning to pull the latest Cisco advisories, parses the CVRF XML, and forwards critical and high-severity items into the SIEM as detection rules. The OAuth client-credentials flow makes this safe to run unattended on a scheduler. Example prompt: Call GET /security/advisories/cvrf/latest/10, filter the response to advisories with severity 'Critical' or 'High', and forward each one to the SIEM ingestion endpoint. ### CVE-to-Cisco-advisory lookup during incident response When a public CVE is reported, an analyst or agent calls /security/advisories/cvrf/cve/{cve_id} to find Cisco's advisory for that CVE, including affected products, fixed releases, and workarounds. This shortens the time from CVE disclosure to a remediation plan from hours to seconds. Example prompt: Call GET /security/advisories/cvrf/cve/CVE-2024-20399 and return the advisory ID, affected products, and fixed releases. ### IOS and IOS XE platform-specific vulnerability scan Network teams use /security/advisories/ios and /security/advisories/iosxe to retrieve advisories that specifically affect IOS or IOS XE, then cross-reference the affected releases against their inventory of running images. This drives prioritised firmware upgrades on routers and switches. Example prompt: Call GET /security/advisories/iosxe, extract the list of affected IOS XE releases, and produce an upgrade priority list for the network team. ### AI agent vulnerability triage via Jentic An AI agent connected to Jentic searches for 'find Cisco advisory by CVE', loads the schema for /security/advisories/cvrf/cve/{cve_id}, and executes the call as part of a larger triage workflow that also queries NVD and the customer's asset inventory. Jentic resolves the OAuth token transparently - the agent never sees the client_secret. Example prompt: Through Jentic, search 'find Cisco advisory by CVE', load the schema for the CVE lookup endpoint, and execute it with CVE-2024-20399 to retrieve the matching advisory. ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | /security/advisories/cvrf/advisory/{advisory_id} | Get a CVRF advisory by ID | | GET | /security/advisories/cvrf/cve/{cve_id} | Look up advisories by CVE ID | | GET | /security/advisories/cvrf/severity/{severity} | List advisories by severity | | GET | /security/advisories/cvrf/latest/{number} | Get the latest N advisories | | GET | /security/advisories/cvrf/year/{year} | List advisories published in a given year | | GET | /security/advisories/ios | List IOS advisories | | GET | /security/advisories/iosxe | List IOS XE advisories | | GET | /security/advisories/oval/cve/{cve_id} | Get OVAL definitions by CVE ID | ## Key resources - **CVRF advisories** — Common Vulnerability Reporting Framework documents - XML advisories with affected products, severity, and fixes - **OVAL definitions** — Open Vulnerability and Assessment Language definitions used by automated scanners - **IOS / IOS XE advisories** — Platform-specific advisory feeds for Cisco's network operating systems ## Why Jentic - **Setup:** Wiring the Cisco PSIRT openVuln API by hand means running its OAuth flow and formatting advisory lookups by CVE, severity, year, and product family yourself. Through Jentic you install once, import the Cisco PSIRT openVuln API from the API Directory, store the OAuth credential once, and your agent calls it. - **Permission scoping:** This API is read-only and puts identifiers like the advisory or CVE id in the URL path (/advisory/{advisory_id}, /cve/{cve_id}), so scope the agent to the advisory-retrieval operations it needs. You choose the operations it may call, so it can be limited to lookups by CVE alone if that is all it needs. - **Credential handling:** Your Cisco OAuth credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'find advisories for a CVE' or 'list the latest security advisories', and Jentic returns the matching Cisco PSIRT operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **CIRCL CVE Search** — Open CVE database for cross-referencing Cisco advisories with NVD data - **GitHub API** — Used to file a remediation issue or PR after a Cisco advisory triage - **Splunk API** — SIEM destination for Cisco advisory feeds and detection content ## FAQ ### Why is there no official OpenAPI spec for Cisco PSIRT openVuln API? Cisco does not publish an OpenAPI specification for the PSIRT openVuln API. Jentic generates and maintains this spec so that AI agents and developers can call Cisco PSIRT openVuln API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer. ### What authentication does the Cisco PSIRT openVuln API use? It uses OAuth 2.0 client-credentials. You register an application at apiconsole.cisco.com to obtain a client_id and client_secret, exchange them for a bearer token at https://cloudsso.cisco.com/as/token.oauth2, and send the token as Authorization: Bearer . Through Jentic, the client_id and client_secret stay in your Jentic One instance. ### Can I look up Cisco advisories by a public CVE ID? Yes. GET /security/advisories/cvrf/cve/{cve_id} returns the CVRF advisory matching that CVE, including affected Cisco products, severity, and fixed releases. There is also an OVAL equivalent at /security/advisories/oval/cve/{cve_id} for scanner-friendly output. ### What are the rate limits for the Cisco PSIRT openVuln API? The OpenAPI spec does not declare explicit rate limits. Cisco's documented guidance is to respect 429 responses and back off; for production polling, schedule the /latest/{number} endpoint at most once every few minutes rather than continuous polling. ### Can I retrieve advisories that only affect IOS or IOS XE? Yes. The dedicated GET /security/advisories/ios and GET /security/advisories/iosxe endpoints return advisories affecting those network operating systems specifically, which is more efficient than filtering the full advisory feed. ### How do I monitor new Cisco advisories from an AI agent through Jentic? Run pip install jentic, have the agent search 'list latest Cisco security advisories', load the schema for GET /security/advisories/cvrf/latest/{number}, and execute it on a schedule. Jentic refreshes the OAuth token automatically - the agent only sees the JSON response. ### Can I limit what my agent is allowed to do with the Cisco PSIRT openVuln API? Yes. Because you run Jentic One yourself, your own rules decide which of this API's read-only operations the agent may call and which credential it may use. This API is entirely read-only and puts identifiers in the URL path, so you can scope the agent to just the advisory-retrieval operations it needs, such as the CVE lookup at GET /security/advisories/cvrf/cve/{cve_id} or the latest-advisories feed, while withholding the severity, year, or IOS and IOS XE endpoints. If the agent only ever looks up advisories by CVE, you can grant that single operation and nothing more.