Resolve Vulnerability Instances

Use the IoT Security API to mark one or more instances of a vulnerability as resolved.

Synopsis

URI
/pub/v4.0/vulnerability/update
HTTP Method
PUT
FQDN
<customer-name>.iot.paloaltonetworks.com

Description

Mark one or more instances of a vulnerability as resolved.

Request Fields

The URL of this request contains the following parameter:
Field
Description
customerid
(
Required
) The customer ID specifies the API call for a specific tenant.
The following value is a string.
The payload of this request contains the following parameters:
Field
Description
ticketIdList
(
Required
) This is a list of one or more ticket IDs for vulnerability instances being resolved.
If you include the ticket IDs for multiple vulnerability instances, separate them by commas; for example:
"ticketIdList": ["vuln-1a4a72c2", "vuln-1a4a72c3", "vuln-1a4a72c4"]
To retrieve a list of vulnerabilities and vulnerability instances, including their ticket IDs, use Get Vulnerability Instancesand refer to the
zb_ticketid
values.
action
(
Required
) This is the action employed to resolve the vulnerability instance. The following value is a string and must be either
mitigate
or
ignore
.
reason
(
Required
) This is the reason for resolving the vulnerability instance. The following value is a string and cannot contain any special characters.
full_name
(
Required
) This is the name of the vulnerability; for example,
CVE-2018-18568
.
The following value is a string.
Request to Resolve a Vulnerability Instance Example
curl 'https://acmecorp.iot.paloaltonetworks.com/pub/v4.0/vulnerability/update?customerid=acmecorp' -H 'X-Key-Id: <key_id>' -H 'X-Access-Key: <access_key>' --header ’Content-Type: application/json’ --data-raw '{ "ticketIdList" [ "vuln-1a4a72c2" ], "action": "mitigate", "reason": "Threat was removed", "full_name": "CVE-2018-18568" }'

Success Response

Upon success, the HTTP response code is 200.
Success Response Example
{ "api": "/pub/v4.0/vulnerability/update", "ver":"v4.0", "updatedVulnerInstanceList": [ "newLevel": "Low", "newScore": 18, "newAnomalyMap": { "application": 0.125, "payload": 0.125, "internal": 0.125, "external": 0.125, "protocol": 0.125 } ] }

Error Response

Upon error, the reply includes an HTTP response code, an error message, and additional information describing the error. The HTTP response code is one of the following:
Field
Description
400
Bad Request. Got an invalid JSON.
401
Unauthorized access. An issue occurred during authentication. This can indicate an incorrect key, id, or other invalid authentication parameters.
402
Unauthorized access. User does not have the required license type to run this API.
403
Forbidden access. The provided API Key does not have the required RBAC permissions to run this API.
500
Internal server error. A unified status for API communication type errors.
Error Response Format
{code: STATUS_CODE, msg: GENERAL_MESSAGE}

Recommended For You