This is a cache of https://docs.openshift.com/acs/3.72/integration/integrate-with-image-vulnerability-scanners.html. It is a snapshot of the page at 2024-11-25T17:34:30.542+0000.
Integrating with image vulnerability scanners | Integrating | Red Hat Advanced Cluster Security for Kubernetes 3.72
    OpenShift docs are moving and will soon only be available at docs.redhat.com, the home of all Red Hat product documentation. Explore the new docs experience today.
  1. Documentation
    2. history
×

Integrating with image vulnerability scanners

Red Hat Advanced Cluster Security for Kubernetes (RHACS) integrates with various vulnerability scanners to enable you to import your container images and monitor them for vulnerabilities. You can set up Red Hat Advanced Cluster Security for Kubernetes to obtain image vulnerability data from many open-source and commercial container image vulnerability scanners, including:

If you are using one of these products in your DevOps workflow, you can use the RHACS portal to configure a connection with RHACS. Once integrated, your image vulnerabilities are surfaced in the RHACS portal and you can triage them easily.

Integrating with CoreOS Clair

You can integrate Red Hat Advanced Cluster Security for Kubernetes with CoreOS Clair for the static analysis of vulnerabilities in your images.

Procedure

  1. On the RHACS portal, navigate to Platform Configuration → Integrations.

  2. Under the Image Integrations section, select CoreOS Clair.

  3. Click New integration.

  4. Enter the details for the following fields:

    1. Integration name: The name of the integration.

    2. Endpoint: The address of the scanner.

  5. (Optional) If you are not using a TLS certificate when connecting to the registry, select Disable TLS certificate validation (insecure).

  6. (Optional) Select Test to test that the integration with the selected registry is working.

  7. Select Save.

Integrating with Google Container Registry

You can integrate Red Hat Advanced Cluster Security for Kubernetes with Google Container Registry (GCR) for container analysis and vulnerability scanning.

Prerequisites

  • You must have a service account key for the Google Container Registry.

  • The associated service account has access to the registry. See Configuring access control for information about granting users and other projects access to GCR.

  • If you are using GCR Container Analysis, you have granted the following roles to the service account:

    • Container Analysis Notes Viewer

    • Container Analysis Occurrences Viewer

    • Storage Object Viewer

Procedure

  1. On the RHACS portal, navigate to Platform Configuration → Integrations.

  2. Under the Image Integrations section, select Google Container Registry.

    The Configure image integration modal box opens.

  3. Click New Integration.

  4. Enter the details for the following fields:

    1. Integration Name: The name of the integration.

    2. Types: Select Scanner.

    3. Registry Endpoint: The address of the registry.

    4. Project: The Google Cloud project name.

    5. Service Account Key (JSON) Your service account key for authentication.

  5. Select Test (checkmark icon) to test that the integration with the selected registry is working.

  6. Select Create (save icon) to create the configuration.

Integrating with Quay Container Registry to scan images

You can integrate Red Hat Advanced Cluster Security for Kubernetes with Quay Container Registry for scanning images.

Prerequisites

  • You must have an OAuth token for authentication with the Quay Container Registry to scan images.

Procedure

  1. On the RHACS portal, navigate to Platform Configuration → Integrations.

  2. Under the Image Integrations section, select Red Hat Quay.io.

  3. Click New integration.

  4. Enter the Integration name.

  5. Under Type, select Scanner. (If you are also integrating with the registry, select Scanner + Registry.) Enter information in the following fields:

    • Endpoint: Enter the address of the registry.

    • OAuth token: Enter the OAuth token that RHACS uses to authenticate by using the API.

    • Optional: Robot username: If you are configuring Scanner + Registry and are accessing the registry by using a Quay robot account, enter the user name in the format <namespace>+<accountname>.

    • Optional: Robot password: If you are configuring Scanner + Registry and are accessing the registry by using a Quay robot account, enter the password for the robot account user name.

  6. Optional: If you are not using a TLS certificate when connecting to the registry, select Disable TLS certificate validation (insecure).

  7. Optional: To create the integration without testing, select Create integration without testing.

  8. Select Save.

If you are editing a Quay integration but do not want to update your credentials, verify that Update stored credentials is not selected.