: Scan Images for Custom Vulnerabilities

Scan Images for Custom Vulnerabilities

Table of Contents

Scan Images for Custom Vulnerabilities

Prisma Cloud lets you scan for insecure versions of proprietary software components.
First, augment Prisma Cloud’s Intelligence Stream with your own custom data that specifies a package type, name, and version number. Then configure Prisma Cloud to take action (alert, block) when the scanner finds this package in an image. By default, Prisma Cloud raises an alert when it detects a vulnerability in a custom component.
Prisma Cloud supports the following package types:
  • Distro packages (deb, rpm).
  • Binaries.
  • Nodejs packages.
  • Python packages.
  • Ruby gems.
  • Java artifacts (JAR files).
For cases where Prisma Cloud does not offer built-in support for a package type, you can specify an MD5 hash for the file.

Add a custom vulnerability

Define a custom vulnerability.
  1. Open Console.
  2. Go to
    Manage > System > Custom Feeds
  3. Click on
    Custom Vulnerabilities
  4. Click
    1. Enter a name for your vulnerability..
    2. From the drop-down list, select a package type.
      For Debian packages, RPM packages, and shared libraries, select
      If your package type is not supported, select
    3. Enter the name of your package/binary.
      Package names must be specific for matching. For example, "containerd" is valid, "containerd*" is not.
    4. Specify the range of package versions for which your rule applies.
      The following formats can be used to specify versions:
      Specific version
      Enter a single multi-dot number.
      Range of versions: Min and max are known.
      Enter two multi-dot numbers, separated by a dash.
      Range of versions: Only min version is known.
      Specify a multi-dot number for the minimum version, followed by a dash, then a wild card.*
      Range of versions: Only max version is known.
      Specify a wild card (*) for the minimum version, followed by a dash, then a multi-dot number for the maximum version.
      If package type is set to binary, the version fields are not visible. Instead, enter the MD5 hash for your file or binary.
  5. Click
    Your custom vulnerability is now available to the scanner.
    By default, an alert is logged if an image scan detects a component that you have designated as vulnerable. To see the default rule, go to
    Defend > Vulnerabilities > Images
    , and click on the
    Default - alert all components
    rule. To change the default rule, select a different Alert or block threshold. To take a different action, create a new vulnerability rule.

Recommended For You