Administration Guide
General administration for the Trusted Profile Analyzer service
Abstract
Preface
Welcome to the Red Hat Trusted Profile Analyzer (RHTPA) Administration Guide!
Chapter 1. What are importers?
An importer in Red Hat Trusted Profile Analyzer (RHTPA) gives you the ability to fetch advisory and vulnerability data from different remote sources. Then RHTPA uses this data to give you more insights when analyzing your Software Bill of Materials (SBOM) and Common Security Advisory Framework (CSAF) documents.
Available importers
By default, RHTPA comes configured with four importer sources: Red Hat CSAFs, Red Hat SBOMs, Common Vulnerability and Exposure (CVE) list version 5, and the GitHub advisory database. We disabled the Red Hat CSAF and SBOM importers because they can run a long time before finishing, but you can enable them at anytime. We enabled the CVE list and GitHub advisory database importer sources.
Scheduling
By default, the set schedule for each importer source to run is 1 day. This means an enabled importer source runs once a day. After a successful initial running of the importer, the next scheduled run is 24 hours from the time the importer job finished.
Computing resources
Computing resources, and setting limitations on those resources in Red Hat OpenShift Container Platform is important to ensure the application runs stable and performs as expected. The default resource request is 1 CPU and 8 GB of RAM, for both the importer and API server deployments. There are no resource limits by default.
You can either reduce the resource requirements, at the cost of stability, or give more resources to the cluster, supporting the workload. Pods can fail to start, or become stuck in a "Pending" state, if computing requirements are not adequate to support the workload.
Additional resources
- For more information about computing resources, see Understanding resource requests and limits in the OpenShift Container Platform documentation.
Chapter 2. Creating a software bill of materials manifest file
Red Hat Trusted Profile Analyzer can analyze both CycloneDX and Software Package Data Exchange (SPDX) SBOM formats by using the JSON file format. Many open source tools are available to you for creating Software Bill of Materials (SBOM) manifest files from container images, or for your application. For this procedure we are going to use the Syft tool.
Currently, Trusted Profile Analyzer only supports CycloneDX version 1.3, 1.4, and 1.5, along with SPDX version 2.2, and 2.3.
Prerequisites
Install Syft for your workstation platform:
Procedure
To create an SBOM by using a container image.
CycloneDX format:
Syntax
Copy to Clipboard Copied! Toggle word wrap Toggle overflow syft IMAGE_PATH -o cyclonedx-json@1.5
syft IMAGE_PATH -o cyclonedx-json@1.5
Example
Copy to Clipboard Copied! Toggle word wrap Toggle overflow syft registry:example.io/hello-world:latest -o cyclonedx-json@1.5
$ syft registry:example.io/hello-world:latest -o cyclonedx-json@1.5
SPDX format:
Syntax
Copy to Clipboard Copied! Toggle word wrap Toggle overflow syft IMAGE_PATH -o spdx-json@2.3
syft IMAGE_PATH -o spdx-json@2.3
Example
Copy to Clipboard Copied! Toggle word wrap Toggle overflow syft registry:example.io/hello-world:latest -o spdx-json@2.3
$ syft registry:example.io/hello-world:latest -o spdx-json@2.3
NoteSyft supports many types of container image sources. See the official supported source list on Syft’s GitHub site.
To create an SBOM by scanning the local file system.
CycloneDX format:
Syntax
Copy to Clipboard Copied! Toggle word wrap Toggle overflow syft dir: DIRECTORY_PATH -o cyclonedx-json@1.5 syft file: FILE_PATH -o cyclonedx-json@1.5
syft dir: DIRECTORY_PATH -o cyclonedx-json@1.5 syft file: FILE_PATH -o cyclonedx-json@1.5
Example
Copy to Clipboard Copied! Toggle word wrap Toggle overflow syft dir:. -o cyclonedx-json@1.5 syft file:/example-binary -o cyclonedx-json@1.5
$ syft dir:. -o cyclonedx-json@1.5 $ syft file:/example-binary -o cyclonedx-json@1.5
SPDX format:
Syntax
Copy to Clipboard Copied! Toggle word wrap Toggle overflow syft dir: DIRECTORY_PATH -o spdx-json@2.3 syft file: FILE_PATH -o spdx-json@2.3
syft dir: DIRECTORY_PATH -o spdx-json@2.3 syft file: FILE_PATH -o spdx-json@2.3
Example
Copy to Clipboard Copied! Toggle word wrap Toggle overflow syft dir:. -o spdx-json@2.3 syft file:/example-binary -o spdx-json@2.3
$ syft dir:. -o spdx-json@2.3 $ syft file:/example-binary -o spdx-json@2.3
Additional resources
- National Telecommunications and Information Administration’s (NTIA) How-to Guide on SBOM generation.
Chapter 3. Downloading and viewing license information
Red Hat’s Trusted Profile Analyzer (RHTPA) can analyze both CycloneDX and Software Package Data Exchange (SPDX) SBOM documents. You can download and view license information from uploaded Software Bill of Materials (SBOM) documents, in CycloneDX or SPDX format. To learn more about the differences between the two licenses formats for CycloneDX and SPDX, see the additional resources section.
Prerequisites
- Installation of RHTPA service on Red Hat OpenShift or Red Hat Enterprise Linux.
- An uploaded CycloneDX 1.3, 1.4, or 1.5 or SPDX 2.2, 2.3 document.
Procedure
- Open a web browser, and log in to the RHTPA console.
- From the home page, click Search from the navigational sidebar.
- Find your SBOM from the list.
- Click the dropdown menu, and click Download License Export.
-
Extract the license information from the downloaded
.zip
file. Open the comma-separated values (CSV) file to view it.
NoteThe license reference CSV file only applies to SPDX-formatted SBOMs.
Additional resources