Ingest SARIF Data
Upload SAST data from third-party tools (for vendors that support SARIF output) to the Prisma Cloud platform using SARIF (Static Analysis Results Interchange Format) to analyze and remediate SAST issues directly within the platform. This feature is particularly useful for vendors that are not directly supported by Prisma Cloud. When SARIF data findings are uploaded, they are parsed to generate code weaknesses.
If you are using Veracode, consider using the native ingestion feature instead. The native integration includes automatically pulling the data periodically and provides additional fidelity.
Prisma Cloud supports SARIF versions 2.0 and 2.1 and accepts .zip, .json, and .sarif files.
You can upload SARIF files through the Prisma Cloud platform or via the API.
Before you begin:
Permissions:
Grant System Administrator or AppSec privileges to users who need to view and upload SARIF results. Limit access to read-only for selected repositories by assigning the Developer role permissions to users who only need to view and analyze data in specific repositories without the ability to make changes
GRBAC (Generic Role-Based Access Control): Viewing will require permissions for Projects > View and access to the selected repositories. Ingesting SARIF files will require permissions for Providers > Create or Update. Deleting old SARIF files will require permissions for Providers > Delete
Onboard the repository into the system before SARIF findings for that repository can be uploaded
Only upload findings relevant to the repository
Ensure that uploaded findings follow the standard SARIF specifications
Add the Prisma Cloud IP addresses and hostname for Application Security to an allow list to enable access to the Prisma Cloud console
Ingest SARIF via the console
Export the required SARIF file from your third-party vendor to your host machine.
In Application Security, select Repositories > click on a repository > Add SARIF Findings.
Browse for and select the SARIF file from the displayed dialog box.
The file is uploaded and the ingestion process begins (up to ten minutes depending on the size of the ingested data). Popups will notify you that the ingestion upload was successful and that the ingestion processing has begun.
Ingest SARIF via the API
Ingest SARIF files via the API, enabling automation, such as in a CI/CD pipeline:
Command properties breakdown:
Prisma Cloud API URL: Use your tenant API URL (for example, "https://api3.prismacloud.io"). For more information, refer to Enable Access to the Prisma Cloud Console
Prisma Cloud generated token: Use the login endpoint to generate a JWT. Refer to Prisma Cloud APIs - Login for more information
Repository ID: Found in the header on the Repositories page or the response from the List Repositories List endpoint. Refer to List Repositories List for more information
EXAMPLE
Example pipeline
The following is an example of a pipeline that scans every push to the main or master branch and sends the results to Prisma Cloud. Before you begin, set the following secrets as repository secrets in your secret management system for your CI pipelines (for example, for GitHub: Settings > Secrets and variables > Actions > Add secrets):
PRISMA_URL: Base URL for Prisma Cloud login and file upload
PRISMA_USERNAME: Your Prisma Cloud API ID
PRISMA_PASSWORD: Your Prisma Cloud API key
PRISMA_REPO_ID: Your repository ID in Prisma Cloud
Manage Code Weaknesses
To view and manage code weaknesses from ingested SARIF findings, refer to Manage Third-Party Ingested Data.
Last updated
Was this helpful?

