Prisma Cloud Compute
Prisma Cloud Compute Edition provides protection for your hosts, containers, and serverless deployments, whether they are located in on-premises data centers or cloud environments. You can bring code, container, host, and security data from Prisma Cloud Compute into Brinqa to gain a more comprehensive view of your attack surface and strengthen your cybersecurity posture.
This document details the information you must provide for the connector to authenticate with Prisma Cloud Compute and how to obtain that information from Prisma Cloud. See create a data integration for step-by-step instructions on setting up the integration.
Required connection settings
When setting up a data integration, select Prisma Cloud Compute from the Connector dropdown. If you cannot find the connector in the dropdown, make sure that you have installed it first. You must provide the following information to authenticate Prisma Cloud Compute with Brinqa:
-
Server URL: The Prisma Cloud Compute Server URL.
-
API key and Secret key: The access keys associated with the Prisma Cloud Compute account, which must have permissions to log in to the API server and return data.
ImportantIf you use the on-premises version of Prisma Cloud Compute, you must use the username in the API key field and the password in the Secret key field. In either case, the credentials associated with the Prisma Cloud Compute account must have permissions to log in to the API server and return data.
Generate Prisma Cloud Compute access keys
For the cloud instance of the Prisma Cloud Compute connector to use the Prisma Cloud Compute API, you must provide the API credentials from Prisma Cloud Compute. To do so, follow these steps:
-
Log in to your organization's Prisma Cloud Compute server.
-
Navigate to Settings > Access Control > Access Keys.
-
Select Add > Access Key.
-
Enter a name for the key, enable key expiration, and set a expiry date and time.
-
Click Save to create the key.
Your new access keys display. You cannot view the secret key after this, so copy the key and save it to a secure location.
If you do not have the permissions to create access keys, contact your Prisma Cloud Compute administrator. For additional information, see Prisma Cloud Compute documentation.
Additional settings
The Prisma Cloud Compute connector contains additional options for specific configuration:
-
Page size: The maximum number of records to get per API request. The default setting is 100. It is not recommended to go over 100.
-
Parallel requests: The maximum number of parallel API requests. The default setting is 4.
-
Skip certificate verification: Select this option to allow for untrusted certificates.
Types of data to retrieve
The Prisma Cloud Compute connector can retrieve the following types of data from the Prisma Cloud Compute API:
Table 1: Data retrieved from Prisma Cloud Compute
| Connector Object | Required | Maps to Data Model |
|---|---|---|
| Cloud Resource | No | Not mapped |
| Code Repository | Yes | Code Repository |
| Container | Yes | Container |
| Container Image | Yes | Container Image |
| Host | Yes | Host |
| Installed Package | Yes | Installed Package |
| Serverless | No | Not mapped |
| Violation | Yes | Violation |
| Violation Definition | Yes | Violation Definition |
| Vulnerability | Yes | Vulnerability |
| Vulnerability Definition | Yes | Vulnerability Definition |
For detailed steps on how to view the data retrieved from Prisma Cloud Compute in the Brinqa Platform, see How to view your data.
Operation options
The Prisma Cloud Compute connector supports the following operation options. See connector operation options for information about how to apply them.
Click the sections below to view the supported operation options per connector object.
Code Repository
Table 2: Code Repository operation options
| Connector Object | Option | All Possible Values | Example |
|---|---|---|---|
| Code Repository | collections | Any valid Prisma Cloud Compute collection name or ID | Key: collections Value: collection1. This key and value combination only retrieves data for the collection1 collection from your code repositories. |
| id | Any valid Prisma Cloud Compute code repository ID | Key: id Value: repo-id-123. This key and value combination only retrieves data for the specified code repository. | |
| project | Any valid Prisma Cloud Compute project name or ID | Key: project Value: web-app. This key and value combination only retrieves data for the web-app project from your code repositories. |
Container
Table 3: Container operation options
| Connector Object | Option | All Possible Values | Example |
|---|---|---|---|
| Container | collections | Any valid Prisma Cloud Compute collection name or ID | Key: collections Value: collection1. This key and value combination retrieves data for the specified collection from containers. |
| hostname | Any valid Prisma Cloud Compute hostname | Key: hostname Value: host1. This key and value combination retrieves data for containers on the specified host. | |
| id | Any valid Prisma Cloud Compute container ID | Key: id Value: container1. This key and value combination retrieves data for the specified container. | |
| name | Any valid Prisma Cloud Compute image name | Key: name Value: image1. This key and value combination retrieves data for containers using the specified image. | |
| project | Any valid Prisma Cloud Compute project name or ID | Key: project Value: api-service. This key and value combination only retrieves data for the api-service project from your containers. |
Container Image
Table 4: Container Image operation options
| Connector Object | Option | All Possible Values | Example |
|---|---|---|---|
| Container Image | collections | Any valid Prisma Cloud Compute collection name or ID | Key: collections Value: collection1. This key and value combination retrieves data for the specified collection from container images. |
| id | Any valid Prisma Cloud Compute image ID | Key: id Value: image1. This key and value combination retrieves data for the specified image ID. | |
| name | Any valid Prisma Cloud Compute image name | Key: name Value: image1. This key and value combination retrieves data for the specified image. | |
| project | Any valid Prisma Cloud Compute project name or ID | Key: project Value: api-service. This key and value combination only retrieves data for the api-service project from your container images. | |
| registry | Any valid Prisma Cloud Compute registry | Key: registry Value: registry1. This key and value combination retrieves data from the specified registry. | |
| repository | Any valid Prisma Cloud Compute repository | Key: repository Value: repo1. This key and value combination retrieves data from the specified repository. |
Host
Table 5: Host operation options
| Connector Object | Option | All Possible Values | Example |
|---|---|---|---|
| Host | collections | Any valid Prisma Cloud Compute collection name or ID | Key: collections Value: collection1. This key and value combination retrieves data for the specified collection from hosts. |
| hostname | Any valid Prisma Cloud Compute hostname | Key: hostname Value: host1. This key and value combination retrieves data for the specified host. | |
| id | Any valid Prisma Cloud Compute instance ID | Key: id Value: i-12345. This key and value combination retrieves data for the specified host ID. | |
| project | Any valid Prisma Cloud Compute project name or ID | Key: project Value: database-cluster. This key and value combination only retrieves data for the database-cluster project from your hosts. | |
| provider | Any valid Prisma Cloud Compute cloud provider | Key: provider Value: aws. This key and value combination retrieves data from the specified cloud provider. | |
| region | Any valid Prisma Cloud Compute region | Key: region Value: us-east-1. This key and value combination retrieves data from the specified region. |
Violation & Vulnerability
Table 6: Violation, Violation Definition, Vulnerability, and Vulnerability Definition operation options
| Connector Object | Option | All Possible Values | Example |
|---|---|---|---|
| Violation, Violation Definition, Vulnerability, Vulnerability Definition | collections | Any valid Prisma Cloud Compute collection name or ID | Key: collections Value: collection1. This key and value combination retrieves security data from the specified collections. |
| functionLayers | Any Prisma Cloud Compute function layer identifiers | Key: functionLayers Value: layer1. This key and value combination only retrieves security data from the specified function layers. | |
| hostname | Any Prisma Cloud Compute hostname | Key: hostname Value: hostname1. This key and value combination only retrieves security data associated with the specified hostname. | |
| id | Any valid Prisma Cloud Compute security data ID | Key: id Value: violation1. This key and value combination retrieves data for the specified security data ID. | |
| name | Any Prisma Cloud Compute security data name identifiers | Key: name Value: name1,name2. This key and value combination only retrieves security data with the specified names. | |
| project | Any valid Prisma Cloud Compute project name or ID identifiers | Key: project Value: "web-app,data-service. This key and value combination only retrieves security data from the specified projects. | |
| provider | Any Prisma Cloud Compute cloud provider identifier | Key: provider Value: aws,azure. This key and value combination only retrieves security data from the specified providers. | |
| region | Any Prisma Cloud Compute region identifiers | Key: region Value: us-east-1,eu-west-1. This key and value combination only retrieves security data associated with the specified regions. | |
| registry | Any Prisma Cloud Compute registry identifiers | Key: registry Value: registry1,registry2. This key and value combination only retrieves security data from the specified registries. | |
| repository | Any Prisma Cloud Compute repository identifiers | Key: repository Value: repo1,repo2. This key and value combination only retrieves security data from the specified repositories. | |
| runtime | Any Prisma Cloud Compute runtime identifiers | Key: runtime Value: nodejs12.x,python3.8. This key and value combination only retrieves security data associated with the specified runtimes. |
The option keys and values are case-sensitive as they are shown in this documentation.
APIs
The Prisma Cloud Compute connector uses the Prisma Cloud Workload Protection REST API v1. Specifically, it uses the following endpoints:
Table 7: Prisma Cloud Compute API endpoints by the connector
| Connector Object | API Endpoints |
|---|---|
| Cloud Resource | GET /api/v1/cloud/discovery/entities |
| Code Repository | POST /api/v1/coderepos |
| Container | GET /api/v1/containers |
| Container Image | GET /api/v1/images |
GET /api/v1/registry | |
| Host | GET /api/v1/hosts |
| Installed Package | GET /api/v1/hosts |
GET /api/v1/containers | |
GET /api/v1/images | |
GET /api/v1/registry | |
POST /api/v1/coderepos | |
GET /api/v1/serverless | |
| Violation | GET /api/v1/containers |
GET /api/v1/hosts | |
GET /api/v1/images | |
GET /api/v1/registry | |
GET /api/v1/serverless | |
| Violation Definition | GET /api/v1/containers |
GET /api/v1/hosts | |
GET /api/v1/images | |
GET /api/v1/registry | |
GET /api/v1/serverless | |
| Vulnerability | POST /api/v1/coderepos |
GET /api/v1/hosts | |
GET /api/v1/images | |
GET /api/v1/registry | |
GET /api/v1/serverless | |
| Vulnerability Definition | POST /api/v1/coderepos |
GET /api/v1/hosts | |
GET /api/v1/images | |
GET /api/v1/registry | |
GET /api/v1/serverless |
Changelog
The Prisma Cloud Compute connector has undergone the following changes:
Table 8: Prisma Cloud Compute connector changelog
This connector is part of a bundled release with other connectors from the same vendor. If a version shows "No change", it means that the connector version was updated for consistency as part of the bundle, but no functional changes were made to this specific connector. You can update to or skip this version without affecting your existing configuration.
| Version | Description | Date Published |
|---|---|---|
| 3.3.0 | - Major refactor of the connector with optimized local store logic. - Added support for the Installed Package object and included it as a target for vulnerabilities. - Improved Serverless processing efficiency by optimizing the number of threads. | February 3rd, 2026 |
| 3.2.4 | Added the following attributes to the Vulnerability object:
| October 22nd, 2025 |
| 3.2.3 | No change. | September 30th, 2025 |
| 3.2.2 | No change. | July 28th, 2025 |
| 3.2.1 | No change. | June 18th, 2025 |
| 3.2.0 | No change. | February 10th, 2025 |
| 3.1.3 | Added the following attributes to the Vulnerability object:
| December 30th, 2024 |
| 3.1.2 | Added the NAMESPACES attribute to the Container Image object. | November 22nd, 2024 |
| 3.1.1 | Code cleanup and general maintenance. | July 17th, 2024 |
| 3.1.0 | - Fixed an issue where vulnerabilities existed in the Brinqa Platform that were not present in an API call, causing inaccurate counts. - Fixed an issue with the REGISTRY and REPOSITORY attributes on the Code Repository object. - Added the HOST_NAMES attribute to the Host object. | July 15th, 2024 |
| 3.0.13 | - Set the status to "Active" for all violations and vulnerabilities retrieved by the connector. This change addresses the possibility that the status of vulnerabilities can be modified in Prisma Cloud Compute after the fix date. - Updated the discovery date on the Violation and Vulnerability objects to use LAST_FOUND instead of FIRST_FOUND. | May 30th, 2024 |
| 3.0.12 | Added the RESOURCE_ID attribute to the Host object. | May 20th, 2024 |
| 3.0.11 | The Cloud Service object has been renamed to Cloud Resource. | May 2nd, 2024 |
| 3.0.10 | Code cleanup and general maintenance. | April 5th, 2024 |
| 3.0.9 | Fixed an issue where syncing vulnerabilities from Code Repository resulted in a 404 error. | March 1st, 2024 |
| 3.0.8 | Code cleanup and general maintenance. | February 29th, 2024 |
| 3.0.7 | Code cleanup and general maintenance. | February 26th, 2024 |
| 3.0.6 | Standardized the STATUS_CATEGORY attribute across the Vulnerability and Violation objects. | May 24th, 2023 |
| 3.0.5 | Updated the NAME attribute in the Container Image object to avoid duplicates. | May 19th, 2023 |
| 3.0.4 | Refactored the code to reduce memory consumption. | May 12th, 2023 |
| 3.0.3 | Code cleanup and general maintenance. | April 26th, 2023 |
| 3.0.2 | Code cleanup and general maintenance. | April 24th, 2023 |
| 3.0.1 | Code cleanup and general maintenance. | March 29th, 2023 |
| 3.0.0 | Initial Integration+ release. | February 1st, 2023 |