Deployed Artifacts
The Deployed Artifacts page displays the artifact status of all the generated and deployed artifacts in the application.
Navigate to Security Issues -> Deployed Artifacts.
The panel at the top displays the total number of Artifacts, Deployed Artifacts and Deployed Overridden Artifacts in the application, and the risk status of the artifacts.
Critical Risk - The artifacts that are of critical risk.
High Risk - The artifacts that are of high risk.
Medium Risk - The artifacts that are of medium risk.
Low Risk - The artifacts that are of low risk.
The panel below displays the details of the artifacts.
Artifact - The name/identifier of the build artifact (e.g., Docker image or package) being tracked.
Application - The application or service to which the artifact belongs.
Account - The cloud or registry account under which the artifact is hosted or deployed.
Artifact Version - The specific version tag or release number of the artifact.
Artifact SHA - The unique cryptographic digest (SHA hash) that identifies the exact artifact build.
Semantic Tags - Human-readable labels or versioning tags associated with the artifact.
Open Issues - The count of currently unresolved security or compliance issues found in the artifact.
Vulnerability - Displays the number of vulnerabilities identified for the given artifact. On clicking it, the Vulnerabilities Management details page is displayed.
Created On - The date and time when the artifact was created or registered.
Team - The team or group responsible for owning or managing the artifact.
Built by - The CI/CD pipeline or user that built and published the artifact.
Service - The microservice or workload that the artifact powers in deployment.
Source Repository - The source code repository (e.g., Git URL) from which the artifact was built.
Stage - The deployment stage or environment (e.g., dev, staging, prod) where the artifact is running.
Cluster - The Kubernetes or cloud cluster to which the artifact is deployed.
Branch - The source code branch from which the artifact was built.
Reports - Links or references to associated security scan or compliance reports for the artifact.
DBOM Status -The status of the Dependency Bill of Materials, tracking software supply chain compliance.
Actions - On clicking the three dots, you can view the list of scans run for the artifact as shown below:
You can download the scan results by clicking on it.
View SBOM for Artifacts
The SBOM for all the deployed artifacts can be viewed by clicking the View SBOM option as shown below:
On clicking View SBOM, the SBOM page is displayed.
It displays the various components and related details of the components as shown below:
Component - Displays the components of the artifact.
Version - Displays the components version.
Package URL - Displays the package URL of the component.
License - Displays the list of licenses that are available for the component.
Vulnerabilities - Displays the count of vulnerabilities related to the component.
EOL Risk - Displays the score of how close the OSS packages used in their project are towards End-of-Life (EOL).
Actions - On clicking Edit License, you can edit the license type.
You can view the vulnerabilities of the components by clicking the Vulnerabilities column.
You can download the SBOM details in .json or .csv format by clicking the SBOM File button.
You can download the SBOM details in report format (.pdf or .html) by clicking the SBOM Report button.
SBOM, Compare and OSS
The SBOM, SBOM comparison page and OSS for the individual artifacts can be accessed from the Reports column.
The icons are displayed in the Reports column.
SBOM - This displays the individual SBOM (Software Bill of Materials) details for the corresponding artifact.
OSS Risk - This displays the OSS (Open Source Software) Risk page of the corresponding artifact.
Compare - This displays the SBOM (Software Bill of Materials) comparison page for the corresponding artifact.
Last updated