Kenna Security · Schema
finding_request_body_schema
CompanyCybersecurityVulnerability ManagementRisk-Based PrioritizationThreat IntelligenceSecurityCiscoREST API
Properties
| Name | Type | Description |
|---|---|---|
| asset_id | integer | The ID of the Asset associated with the Finding. |
| external_unique_id | string | A unique ID, created by a Scanner or client. |
| identifier | string | A CVE, CWE, or WASC. Example: "CWE-242". *Required* if `definition` is not specified. |
| definition | object | *Required* if `identifier` is not specified. |
| closed_at | string | When the Finding was closed. The status body parameter is required to have the status body parameter set to one of the valid closed status values: "closed", "duplicate", "false_positive", "resolved", |
| due_date | string | When the Finding should be fixed. |
| found_on | string | When the Finding was initially found. |
| last_found_on | string | When the Finding was last seen. |
| additional_fields | object | |
| remediation | string | Instructions for remediating the Finding. |
| scanner_score | number | The score provided by the Scanner. |
| status | object | The current status of the Finding. |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://artifacts.apis.io/kenna-security/json-schema/kenna-security-finding-request-body-schema-schema.json",
"title": "finding_request_body_schema",
"x-generated": "2026-11-10",
"x-method": "derived",
"x-generator": "derive-json-schema.py",
"x-source": "openapi/kenna-security-findings-api-openapi.yml#/components/schemas/finding_request_body_schema",
"type": "object",
"required": [
"asset_id",
"external_unique_id"
],
"properties": {
"asset_id": {
"type": "integer",
"description": "The ID of the Asset associated with the Finding.",
"format": "int32"
},
"external_unique_id": {
"type": "string",
"description": "A unique ID, created by a Scanner or client."
},
"identifier": {
"type": "string",
"description": "A CVE, CWE, or WASC. Example: \"CWE-242\". *Required* if `definition` is not specified."
},
"definition": {
"type": "object",
"description": "*Required* if `identifier` is not specified.",
"required": [
"scanner_identifier"
],
"properties": {
"scanner_identifier": {
"type": "string",
"description": "A value, most likely specific to the Scanner, identifying the Finding."
},
"scanner_name": {
"type": "string",
"description": "The name of the Scanner reporting the Finding."
},
"name": {
"type": "string",
"description": "A name for the Finding."
},
"description": {
"type": "string",
"description": "A description of the Finding."
},
"solution": {
"type": "string",
"description": "A solution to the Finding."
},
"pci_related": {
"type": "boolean",
"description": "Whether or not this Finding is related to the Payment Card Industry."
}
}
},
"closed_at": {
"type": "string",
"description": "When the Finding was closed. The status body parameter is required to have the status body parameter set to one of the valid closed status values: \"closed\", \"duplicate\", \"false_positive\", \"resolved\", and \"not_a_security_issue\". This implies that both closed_at and status will be updated.",
"format": "date-time"
},
"due_date": {
"type": "string",
"description": "When the Finding should be fixed.",
"format": "date-time"
},
"found_on": {
"type": "string",
"description": "When the Finding was initially found.",
"format": "date-time"
},
"last_found_on": {
"type": "string",
"description": "When the Finding was last seen.",
"format": "date-time"
},
"additional_fields": {
"$ref": "#/$defs/additional_fields"
},
"remediation": {
"type": "string",
"description": "Instructions for remediating the Finding."
},
"scanner_score": {
"type": "number",
"description": "The score provided by the Scanner.",
"format": "float"
},
"status": {
"$ref": "#/$defs/finding_status",
"description": "The current status of the Finding."
}
},
"$defs": {
"additional_fields": {
"description": "Any additional information you want associated with the Finding.",
"type": "object",
"properties": {
"fields": {
"type": "array",
"items": {
"type": "object",
"properties": {
"field_name": {
"type": "string"
},
"value": {
"type": "string"
}
}
}
}
}
},
"finding_status": {
"type": "string",
"enum": [
"duplicate",
"false_positive",
"in_progress",
"new",
"not_a_security_issue",
"resolved",
"risk_accepted",
"triaged"
]
}
}
}
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/kenna-security-finding-request-body-schema"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.