# Export every model through the Request Data Export API, in json, jsonl or xml, before support ends

PROGRAM GUIDE, read 10 Nov 2026

**The short answer.** The Cisco Vulnerability Management API exports asset, fix, vulnerability and finding data in json, jsonl or xml. No CSV export was found on 2026-11-10. Exports run in the background, search IDs last 30 days, and downloads arrive gzipped. Schedule the first full export now and repeat it until cutover.

## What the API exports

The Request Data Export endpoint in the [Kenna Platform API](https://apidocs.kennasecurity.com/reference/request-data-export.md) takes a model and a format. The four models are asset, fix, vulnerability and finding. The three formats are json, jsonl and xml, and jsonl is the default. A CSV export: none found on 2026-11-10 in the API documentation. If your downstream tools expect CSV, plan a conversion step.

The request runs in the background. The API returns a search_id, and the results can be fetched once processing completes. Search IDs are valid for 30 days after the request. Do not store the search_id as your archive. Download the files and keep them.

## Defaults that can hide data

For asset and vulnerability exports the defaults are open vulnerabilities with active assets. For finding exports the default is open findings with active assets. That means closed findings and inactive assets are left out unless you change the filters. If you want history, ask for it explicitly, and check the filter list in the API reference for the status and date parameters that each model accepts.

This default is the most common reason a first export looks smaller than the console. Compare the row count of each export with the count shown in the console for the same filter, and write both numbers in your run log.

## Field selection and file handling

The [downloading export files guide](https://apidocs.kennasecurity.com/docs/downloading-export-files.md) states that downloads are gzip files and that fields can be chosen with export_settings. A slim option applies a predetermined short field set, which includes id, status, closed_at, port, status_changed_at, last_seen_time, asset_id, cve_id and severity. Slim is useful for a quick inventory. It is not enough for a migration, because it omits most of the context you will want to carry.

Request all fields for the first full pull and store the raw files unchanged. Create a second, trimmed set for loading into the new platform. Keeping the raw set means you can answer an auditor's question about a past score after the subscription has ended.

## The daily full export

The documentation also says a daily full gzipped asset and vulnerability export can be arranged through tech support. That is useful if your tenant is large or if API rate limits slow you down. Ask for it in writing, with the delivery location and the date it starts, and confirm it continues until your last day of support. A named contact on the Cisco side is worth more than the ticket number.

## What to export besides findings

The API reference also exposes connector management: listing and updating connectors, running them, listing connector runs and uploading a data file to a file-based connector. Export the connector list. It documents which scanners feed the platform and how often, and that list becomes the first draft of the new platform's source plan.

Risk Meters are the asset-group risk scores in the product. Export the group definitions and the current scores so that you can compare them with the new platform's group scores later. Export the logged manual overrides of risk scores as well, since the documentation says an override is logged for audit and stops dynamic updates for that vulnerability.

- Request all four models in jsonl; keep the raw gzip files.
- Record the row count of each against the console count.
- Export connectors, groups and logged score overrides.
- Repeat monthly, then weekly in the last quarter, then once more at cutover.
- Store the files where a leaver cannot delete them, with a hash of each file.

## A run log for each export

Keep a simple log with one row per export request. Record the model, the format, the filters, the time of the request, the search ID, the time you downloaded the file, the file size, the row count and a hash of the file. The log is short, and it answers the questions that arrive later: which file did we load, was it complete, and was it changed.

Verify each file before you delete anything from the source side. Decompress it, count the records, and open a sample of ten records at random. Check that dates are in one format, that the asset identifier is present on every finding and that the CVE field is filled where you expect it. A file that downloads without error can still be truncated.

Test the load, not only the download. Take one file and import it into a scratch location, even if it is only a database table or a folder of parsed json. If a field is missing from the export that you needed, you find out while the old platform is still running and you can request the export again with the right settings. If you find out after support ends, you cannot.

- Model, format, filters and time of each request.
- Search ID and the 30 day expiry date.
- Row count compared with the console.
- SHA-256 hash of the compressed file.
- A note of who verified it and when.

## Sources

- Request Data Export, Kenna Platform API: https://apidocs.kennasecurity.com/reference/request-data-export.md (read 10 Nov 2026)
- Downloading Export Files: https://apidocs.kennasecurity.com/docs/downloading-export-files.md (read 10 Nov 2026)
- Download zipped vulnerability data: https://apidocs.kennasecurity.com/reference/download-zipped-vuln-data.md (read 10 Nov 2026)
- Kenna API index (connector endpoints): https://apidocs.kennasecurity.com/llms.txt (read 10 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/guides/export-cisco-vulnerability-management-data/
