Error "unknown compliance vulnerability id 420 on the rule" not allowing creation of New CI images Compliance Policy in Prisma Cloud Compute
3759
Created On 07/14/22 16:20 PM - Last Modified 07/18/22 19:37 PM
Symptom
- Error "unknown compliance vulnerability id 420 on the rule" not allowing creation of New CI images Compliance Policy in Prisma Cloud Compute.
Environment
- Prisma Cloud
Cause
- Compliance Vulnerability ID 420 was deprecated, but for some reason this wasn’t cleaned from the affected Policy Rules.
Resolution
Though the Compliance Vulnerability ID 420 can’t be removed using the Prisma Cloud Console UI, this can be done manually using API calls:
- Retrieve current policy with GET `/api/v1/policies/compliance/ci/images` and save the JSON response : Curl for GET
- Remove the Compliance Vulnerability ID 420 from all the affected Rules.
- Save changes with PUT `/api/v1/policies/compliance/ci/images` using the edited JSON as a body : Curl for PUT
Additional Information
Example
- In the following example, Postman (API platform) has been used to perform this task via API calls.
- While accessing CI images compliance policy, open Developer Tools in Browser.
- Go to the Request URL that contains /api/v1/policies/compliance/ci/images
- Copy the Request URL value and save it in a notepad or text file.
- Scroll down to the Request Headers, copy the Authorization value and save it in a notepad or text file.
- Open Postman and access Import tab > Raw text
- Give the curl command to submit HTTP GET request (syntax shared below).
curl -k -H 'Content-Type: application/json' -H 'Authorization: VALUE' -X GET 'URL'Note: Replace the VALUE and URL field with the values copied earlier.
- Sample for Authorization Field shared below.
- Sample for URL Field shared below.
- Import the Curl Command once entered.
- As confirmed, 2 Additional Headers added in the GET Request.
- Click on Send to Submit the GET Request. Once Status 200 OK response received, Copy the Response Body in JSON format.
- Save this response in a notepad or text file.
- Identify and remove id 420 from the rule.
- Go back to Postman > replace GET with PUT > select Body > select raw > select type JSON > Paste the modified Policy > Click on Send.
- Status 200 OK once received indicates that the resource has been updated successfully
- Confirm this change on the Prisma Cloud Console.