PrismaCloud CWPP Connector

The following is not supported in Tenable FedRAMP Moderate environments. For more information, see the Tenable FedRAMP Product Offering.

Prisma Cloud (Palo Alto Networks) is a comprehensive Cloud Workload Protection solution that delivers flexible protection to secure cloud VMs, containers and Kubernetes apps, serverless functions and containerized offerings like AWS Fargate® tasks. With Prisma Cloud, DevOps and cloud infrastructure teams can adopt the architecture that fits their needs without worrying about security keeping pace with release cycles or protecting a variety of tech stacks.

Prerequisites and User Permissions

Before you begin configuring the connector, make sure to:

• Identify the Prisma Cloud CWPP server URL:

  1. Navigate to Runtime Security > Manage > System.
  2. Click on Utilities.
  3. Identify the server URL.

• Assign a System Administrator role for full access, or configure a custom role:

  • Assign the role to a specific Account Group that includes the resources to be synced (e.g., cloud accounts or on-premises Kubernetes clusters).

    

  • If you plan to ingest data from on-premises Kubernetes clusters, select the On-Prem / Other Cloud Providers checkbox in the Advanced Options section of the role configuration.

  • Confirm that the Account Group is not empty and contains the required resources.

• Generate PrismaCloud CWPP Access and Secret Keys:

  Note: These should be the credentials of a valid Prisma Cloud user with the assigned role as described above.

  1. Sign in to the Prisma Cloud console.

  2. Navigate to Settings > Access Control > Users.

  3. Create a new user or select an existing one.

  4. Assign the appropriate role and account group.

  5. Ensure that the API key Expiration is set to within 6 months of the generation date.

  6. Generate an Access Key ID and Secret Key for the user.

  7. Save the credentials securely. You’ll use them to configure the connector in Exposure Management.

Add a Connector

To add a new connector:

1. In the left navigation menu, click Connectors.

   The Connectors page appears.

   

2. In the upper-right corner, click Add new connector.

   The Connector Library appears.

   

3. In the search box, type the name of the connector.

4. On the tile for the connector, click Connect.

   The connector configuration options appear.

Configure the Connector

To configure the connector:

1. (Optional) In the Connector's Name text box, type a descriptive name for the connector.

2. (Optional) To use a preconfigured on-prem connector to connect to this connector, from the Gateway drop-down, select the on-prem connector you want to use for the connector. Otherwise, select Don't use gateway.

   Note: For information about configuring a gateway, see Tenable On-Prem Connector.

3. In the Server Url section, type the URL of your PrismaCloud server.

4. In the Access Key ID and Secret Access Key text boxes, paste the secret credentials you generated in PrismaCloud.

5. In the Data pulling configuration section, you can configure dynamic settings specific to the connector.

   • In PrismaCloud Assets, check the assets you want to fetch:

     • Fetch Hosts: Mapped as Devices in Exposure Management

     • Fetch Images: Mapped as Containers in Exposure Management

     • Fetch CI Images: Mapped as Containers in Exposure Management

     • Fetch Registries: Mapped as Containers in Exposure Management

   • In Vulnerabilities, check the "Base image indication for Image vulnerabilities" if relevant.

   • In the Asset Retention text box, type the number of days after which you want assets to be removed from Tenable Exposure Management. If an asset has not been detected or updated within the specified number of days, it is automatically removed from the application, ensuring your asset inventory is current and relevant.

     Tip: For more information, see Asset Retention.

6. In the Test connectivity section, click the Test Connectivity button to verify that Tenable Exposure Management can connect to your connector instance.
   

   • A successful connectivity test confirms that the platform can connect to the connector instance. It does not, however, guarantee that the synchronization process will succeed, as additional syncing or processing issues may arise.
     

   • If the connectivity test fails, an error message with details about the issue appears. Click Show tests for more information about the exact error.
     

     

7. In the Connector scheduling section, configure the time and day(s) on which you want connector syncs to occur.

   Tip: For more information, see Connector Scheduling.

8. Click Create. Tenable Exposure Management begins syncing the connector. The sync can take some time to complete.
   

9. To confirm the sync is complete, do the following:

   • Navigate to the Connectors page and monitor the connector's status. Sync is complete once the connector status is Connected.

   • View the sync logs for the connector to monitor the logs for a successful connection.

Prisma CWPP in Tenable Exposure Management

Locate Connector Assets in Tenable Exposure Management

As the connector discovers assets, Tenable Exposure Management ingests those devices for reporting.

To view assets by connector:

1. In Tenable Exposure Management, navigate to the Assets page.

2. In the Filters section, under 3rd Party Connectors, click the connector name for which you want to view assets.

   

   The asset list updates to show only assets from the selected connector.

3. Click on any asset to view Asset Details.

Locate Connector Weaknesses in Tenable Exposure Management

As the connector discovers weaknesses, Tenable Exposure Management ingests those weaknesses for reporting.

To view weaknesses by connector: 

1. In Tenable Exposure Management, navigate to the Weaknesses page.

2. In the Filters section, under 3rd Party Connectors, click the connector name for which you want to view weaknesses.

   

   The weaknesses list updates to show only weaknesses from the selected connector.

3. Click on any weakness to view Weakness Details.

Locate Connector Findings in Tenable Exposure Management

As the connector discovers individual findings, Tenable Exposure Management ingests those findings for reporting.

To view findings by connector:

1. In Tenable Exposure Management, navigate to the Findings page.

2. In the Filters section, under 3rd Party Connectors, click the connector name for which you want to view findings

   

   The findings list updates to show only assets from the selected connector.

3. Click on any asset to view Finding Details.

Data Mapping

Exposure Management integrates with the connector via API to retrieve relevant weakness and asset data, which is then mapped into the Exposure Management system. The following tables outline how fields and their values are mapped from the connector to Exposure Management.

Finding Mapping (for Containers)

Tenable Exposure Management UI Field	Prisma CWPP Field
Unique Identifier	cve + packageName + packageVersion
Finding Name	title or text or cve
CVEs	cve
Severity Severity Driver Risk Factor	cvss
Description	description
Last seen (Observed) In case a finding is fixed, then > Findings > Last Fixed At	discovered
Finding Custom Attributes	vecStr packageName packageVersion packageType cvss severity

Finding Status Mapping

Status Update Mechanisms

Every day, Tenable Exposure Management syncs with the vendor's platform to receive updates on existing findings and assets and to retrieve new ones (if any were added).

The table below describes how the status update mechanism works in the connector for findings and assets ingested into Tenable Exposure Management.

Uniqueness Criteria

Tenable Exposure Management uses defined uniqueness criteria to determine whether an ingested asset or finding should be recognized as a distinct record. These criteria help define how assets and findings are identified and counted from each connector.

Tip:  Read all about Third-Party Data Deduplication in Tenable Exposure Management

The uniqueness criteria for this connector are as follows:

API Endpoints in Use

API version: v1.0, v34.00