Collections

Collections are predefined filters for segments of your environment. They’re centrally defined, and they’re used in rules and views across the product.
Collections are used to:
  • Scope rules to target specific resources in your environment. For example, you might create a vulnerability rule that applies to all container images in an app called sock-shop. The rule might reference collectionA, which specifies
    sock-shop**
    in the image resource filter.
  • Partition views. Collections provide a convenient way to browse data from related resources.
  • Enforce which views specific users and groups can see. Collections can control access to data on a need-to-know basis. These are known as assigned collections.
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.

Partitioning views

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 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 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 a product team runs the shopping app.
Selecting a collection reduces the scope displayed in Console to just the relevant resources. For example, the developer for the travel app only cares about vulnerabilities in the images that make up the travel app. All other vulnerabilities are just noise. Collections help focus the data.

Scoping rules

The scope of a rule is defined by referencing the relevant collections. Collections offer a centralized way to create and manage scope settings across the product. Collections make it easy to consistently reuse scope settings across policies. Policy tables give you a clear picture of what resources are being targeted in your rules.
When creating new rules, you can either select from a list of previously defined collections, or create a new one. By default, Prisma Cloud sets a rule’s scope to the
All
collection, which captures all resources in the environment.
Collections cannot be deleted as long as they’re being used by a rule. This mechanism ensures that rules are never left unscoped. Click on a specific collection to see how it’s being used.

Importing and exporting rules

Rules can be exported from one Console and imported into another Console. When importing rules, any associated collections are also imported and created.
  • If the imported rule uses a collection that doesn’t exist in Console, the collection is automatically created.
  • If the imported rule uses collection with a name that already exists, but with a different scope, the collection is created with the following name and description:
    • Name: <policyType> - <ruleName> <collectionName>
    • Description: Automatically generated collection for an imported rule/entity
  • If the imported rule uses a collection that already exists, and a matching scope, the existing collection is used as-is.

Creating collections

You can create as many collections as you like. Collections cannot be nested. In tenant projects, collections are created and managed on a per-project basis.
Prisma Cloud ships with a built-in set called
All
that is not editable. The
All
collection contains all objects in the system. It is effectively the same as creating a collection manually and setting a wildcard (*) for each resource type (e.g., containers, images, hosts, labels, etc).
Collections can be created in
Manage > Collections and Tags > Collections
. Alternatively, collections can be created directly from a new rule dialog when you’re setting the rule’s scope. When creating collections from a new rule dialog, Prisma Cloud automatically disables any irrelevant scope fields. When selecting previously defined collections in a rule’s scope field, any improperly scoped collections are hidden from display. For example, you can’t select a collection that specifies serverless functions in a container runtime rule.
By default, new collections set a wildcard for each resource, effectively capturing all resources in the system. Customize the relevant fields to capture some segment of the universe of resources.
The labels field supports Docker labels, Kubernetes pod template labels, Kubernetes namespace labels, Kubernetes deployment labels, AWS tags, osDistro:<name> (for hosts), and osVersion:<version> (also for hosts). To use Kubernetes namespace and deployment labels, enable the following setting when deploying Defenders:
Manage > Defenders > Deploy > DaemonSet > Collect Deployment and Namespace labels
.
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.
Filtering by cloud account ID for Azure Container Instances isn’t currently supported.
To create a new collection:
  1. Open Console.
  2. Go to
    Manage > Collections and Tags > Collections
    .
  3. Click
    Add collection
    .
  4. In the
    Create a new collection
    dialog, enter a name, description, and then specify a filter to target specific resources.
    For example, create a collection named
    Raspberry images
    that shows all
    raspberry
    images in the
    fruit
    namespace. Pick a color for easy visibility and differentiation.
    The following collection selects all images that start with the string
    raspberry
    . You can also create collections that exclude resources. For more information on syntax that can be used in the filter fields (e.g., containers, images, hosts, etc), see Rule ordering and pattern matching.
  5. Click
    Save
    .

Assigned collections

Collections provide a light-weight mechanism to provision least-privilege access to the resources in your environment. You can assign collections to specific users and groups to limit their view of data and resources in the environment.
Projects is the other mechanism for partitioning your environment. Projects are Prisma Cloud’s solution for multi-tenancy. They let you provision multiple independent environments, and federate them behind a single Console URL, interface, and API. Projects take more effort to deploy than collections. Collections and Projects can work together. Collections can be utilized in both non-Project and Project-enabled environments.
By default, users and groups can access all collections and are not assigned with any collection.
Users with admin or operator roles can always see all resources in the system. They can also see all collections, and utilize them to filter views. When creating users or groups with the admin or operator role, there is no option for assigning collections.
When creating users or groups with any other role, admins can optionally assign one more collections. These users can only see the resources in the collections they’ve been assigned.
Collections cannot be deleted as long as they’ve been assigned to users or groups. This enforcement mechanism ensures that users and groups are never left stateless. Click on a specific collection to see who is using them.
Changes to a user or group’s assigned collections only take affect after users re-login.

Assigning collections

Assign collections to specific users and groups to restrict their view of data in the environment.
Collections can be assigned to local users, LDAP users, and SAML users. Collections can also be assigned to LDAP and SAML groups. They cannot be assigned to local groups.
When using Projects, Collections can only be assigned to users on each project. Users of the Central Console have access to all projects, and cannot be limited with assigned collections.
Prerequisites:
  • You’ve already created one or more collections.
  • (Optional) You’ve integrated Prisma Cloud with a directory service or SAML IdP.
  1. Open Console, and go to
    Manage > Authentication > {Users | Groups}
    .
  2. Click
    Add users
    or
    Add group
    .
  3. Select the
    Auditor
    or
    DevOps User
    role.
  4. In
    Permissions
    , select one or more collections. If left unspecified, the default permissions is
    All collections
    .
  5. Click
    Save
    .

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
.
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.
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.

Limitations

Different views in Console are filtered by different resource types.
If a collection specifies resources that are unrelated to the view, filtering by this collection returns an empty result.
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
VMware Tanzu 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, Clusters, Container Deployment Labels (under Labels), Cloud Account IDs. (Cluster collections are not currently able to filter some events such as container audits, specifically.)
Monitor/Events
CNNF for Containers
Images (Destination image), Cloud Account IDs
Monitor/Events
WAAS for Containers
Images, Namespaces, Cloud Account IDs
Monitor/Events
Trust Audits
Images, Clusters, Cloud Account IDs
Monitor/Events
Admission Audits
Namespaces, Clusters, Cloud Account IDs
Monitor/Events
Docker Audits
Images, Containers, Hosts, Clusters, Cloud Account IDs
Monitor/Events
App Embedded audits
App IDs (App Embedded), Cloud Account IDs
Monitor/Events
WAAS for App-Embedded
App IDs (App Embedded), Cloud Account IDs
Monitor/Events
Host audits
Hosts, Clusters, Labels, Cloud Account IDs
Monitor/Events
CNNF for Hosts
Hosts (Source and Destination Hosts), Cloud Account IDs
Monitor/Events
WAAS for Hosts
Hosts, Cloud Account IDs
Monitor/Events
Host Log Inspection
Hosts, Clusters, Cloud Account IDs
Monitor/Events
Host File Integrity
Hosts, Clusters, Cloud Account IDs
Monitor/Events
Host Activities
Hosts, Clusters, Cloud Account IDs
Monitor/Events
Serverless audits
Functions, Cloud Account IDs
Monitor/Events
WAAS for Serverless
Functions, Cloud Account IDs
Monitor/Runtime
Container incidents
Images, Containers, Hosts, Namespaces, Clusters, Cloud Account IDs
Monitor/Runtime
Host incidents
Hosts, Clusters, 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

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

Recommended For You