1. Overview

Collections are predefined filters for segments of your environment. They are centrally defined, and can be used in rules and views across the product.

Collections can be used to:

  • Partition views. They provide a convenient way to browse data from related resources.

  • Optionally enforce which views specific users and groups can see. They can control access to data on a need-to-know basis. These are known as assigned collections.

While a single Console manages data from Defenders spread across all hosts, collections let you segment that data into different views based on attributes. Collections are created with pattern matching expressions that are evaluated against attributes such as image name, container name, host name, labels, function name, namespace, and more. AWS tags are supported as part of the Collection label attribute.

Collections are useful when you have large container deployments with multiple teams working on multiple apps all in the same environment. For example, you might have a single Kubernetes cluster that runs a shopping app, a travel app, and an expenses app. Different teams might be responsible for the development and operation of each app. An internal tools team might be responsible for the travel and expenses app, while the product team runs the shopping app.

Selecting a collection reduces the scope displayed in Console to just the relevant components. The developer for the travel app, for example, only cares about vulnerabilities in the images that make up the travel app. All other vulnerabilities are just noise. Collections help focus the data

2. Creating collections

You can create as many collections as you like. Collections cannot be nested. When using Tenant Projects, Collections are created in each of the tenant Projects. When using Scale Projects, Collections are created in the Central Console.

Filtering by cloud account ID for Azure Container Instances isn’t currently supported.
  1. To create a collection, navigate to Manage > Collections and Tags > Collections.

    Prisma Cloud ships with a built-in set called All collections that is not editable. The Default collection contains all objects in the system. It is effectively the same as manually creating a collection manually with a wildcard (*) for each resource type (Containers, Images, Hosts, Labels).

  2. Click Add collection.

  3. In the Create a new collection dialog, enter a name, then specify a filter.

    For example, create a collection called Raspberry images that shows all raspberry images in the namespace fruit. Pick a color for easy visibility and differentiation.

    collections specify filter

    This collection selects all images that start with the string raspberry. You can also create a collection to exclude a set of images. For more information on syntax that can be used inside the filter fields (Containers, Images, Hosts, and Labels), see Rule ordering and pattern matching.

    You cannot have collections that specify both containers and images. You must leave a wildcard in one of the fields, or else the collection won’t be applied correctly. If you want to create collections that apply to both a container and an image, create two separate collections. The first collection should only include the container name, the second should only include the image name. Filtering on both collections at the same time will yield the desired result.
  4. Click Save.

3. Selecting a collection

Collections filter data in the Monitor section of Console.

When a collection (or multiple collections) are selected, only the objects that match the filter are shown in those views. When a collection is selected, it remains selected for all views until it is explicitly disabled.

To select a collection, go to any view under Monitor. In the Collections drop-down list in the top right of the view, select a collection. In the following screenshot, the view is filtered based on the collection named google images, which shows all images that contain the string google_containers.

collections 792004

When multiple collections are selected, the effective scope is the union of each individual query.

Individual filters on each collection aren’t applicable to all views. For example, a collection created with only functions won’t include any resources when viewing hosts results. Similarly, a collection created with hosts won’t filter images by hosts when viewing image results.
collections 792010

The Collections column shows to which collection a resource belongs. The color assigned to a collection distinguishes objects that belong to specific collections. This is useful when multiple collections are displayed simultaneously. Collections can also be assigned arbitrary text tags to make it easier for users to associate other metadata with a collection.

4. Collections limitations

The different views under the Console are filtered by different resource types of the collections.

If your collection is created based on a resource that is not included in the resource types relevant to the view you wish to filter, filtering by this collection should yield empty results.

Section View Supported resources in collection

Monitor/Vulnerabilities

Monitor/Compliance

Images

Images, Hosts, Namespaces, Clusters, Labels, Cloud Account IDs

Monitor/Vulnerabilities

Monitor/Compliance

Containers

Images, Containers, Hosts, Namespaces, Clusters, Labels, Cloud Account IDs

Monitor/Vulnerabilities

Monitor/Compliance

Hosts

Hosts, Clusters, Labels, Cloud Account IDs

Monitor/Vulnerabilities

Monitor/Compliance

VM images

VM images (under Images), Cloud Account IDs

Monitor/Vulnerabilities

Monitor/Compliance

Functions

Functions, Cloud Account IDs

Monitor/Vulnerabilities

Code repositories

Code repositories

Monitor/Vulnerabilities

PCF Blobstore

Hosts (of the scanner host), Cloud Account IDs

Monitor/Vulnerabilities

Vulnerability Explorer

Images, Hosts, Clusters, Labels, Functions, Cloud Account IDs

Monitor/Compliance

Cloud Discovery

Cloud Account IDs

Monitor/Compliance

Cloud Compliance

Cloud Account IDs

Monitor/Compliance

Compliance Explorer

Images, Hosts, Namespaces, Clusters, Labels, Cloud Account IDs

Monitor/Events

Container audits

Images, Namespaces, Container Deployment Labels (under Labels), Cloud Account IDs

Monitor/Events

Host audits

Hosts, Labels, Cloud Account IDs

Monitor/Events

Serverless audits

Functions, Cloud Account IDs

Monitor/Events

App Embedded audits

App IDs (App Embedded), Cloud Account IDs

Monitor/Runtime

Container incidents

Images, Containers, Hosts, Namespaces, Cloud Account IDs

Monitor/Runtime

Host incidents

Hosts, Cloud Account IDs

Monitor/Runtime

Serverless incidents

Functions, Cloud Account IDs

Monitor/Runtime

App Embedded incidents

App IDs (App Embedded), Cloud Account IDs

Monitor/Runtime

Container models

Images, Namespaces, Clusters, Cloud Account IDs

Monitor/Runtime

Host Observations

Hosts, Clusters, AWS tags (under Labels), OS tags (under Labels), Cloud Account IDs

Radar

Containers Radar

Images, Containers, Hosts, Namespaces, Clusters, Labels, Cloud Account IDs

Radar

Hosts Radar

Hosts, Clusters, AWS tags (under Labels), OS tags (under Labels), Cloud Account IDs

Radar

Serverless Radar

Functions

Manage

Defenders

Hosts, Clusters, Cloud Account IDs

4.1. Using Collections

After collections are created or updated, there are some views that require a rescan before you can see the change:

  • Deployed Images vulnerabilities and compliance views

  • Registry Images vulnerabilities and compliance views

  • Code repositories vulnerabilities view

  • Trusted images

  • Cloud Discovery

  • Cloud Compliance

  • Vulnerability Explorer

  • Compliance Explorer

After collections are created or updated, there are some views that are affected by the change only for future records. These views include historical records that keep their collections from creation time:

  • Images and Functions CI results view

  • Events views

  • Incidents view