Code Security: Policy Ids for Errors

Showing results for 
Show  only  | Search instead for 
Did you mean: 

Code Security: Policy Ids for Errors

L0 Member

When scanning IAC with Bridgecrew GitHub action, an error may be returned as "Check: 8060797_AWS_1672940525627: "AWS Lambda function is not configured for function-level concurrent execution Limit" with a link to


Why is the 8060797_AWS_1672940525627 shown as the policy id rather than the native policy id - either BC_AWS_GENERAL_63 or CKV_AWS_115?


In the API to list errors (/code/api/v1/errors/file), the response still returns 8060797_AWS_1672940525627 rather than a native ID as errorId.  The API does not return a link to documentation.   


Linking errors to the underlying OOTB policy is challenging without the native policy id.


L0 Member

A policy ID like "8060797_AWS_1672940525627" is the format of a custom build policy (CCS). Maybe a clone of the OOTB policy?

L0 Member

A custom policy would explain it. 

However, I know this one is not.

When viewing the policy definition in the console, it says "This policy is defined in Checkov, for more information about this policy's exact definition visit".

When querying policy details through the API, the createdBy attribute = "Prisma Cloud System Admin".

I know we've at one time disabled, re-enabled, and updated the labels on this policy (and most other OOTB build policies).  Maybe there was a side effect of one of those operations.  

So I agree that indications are that somehow Prisma Cloud is inaccurately seeing this and other many other of our OOTB build policies as custom policies.

Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!