Viewing Scan Results

Scan results are available as the CLI output in your terminal or in the CloudGuard portal.

CLI Output

The Scan Engine prints the scan results to the CLI. This output can be displayed in a table view or as a JSON JavaScript Object Notation. A lightweight data interchange format. file. The results are based on the assessments that consider vulnerabilities found in the scanned image against the attached policy.

The JSON output has the same format as the results of the assessment API. For more information about API, see the API Reference Guide.

When the scan results include more than 2 CVEs, they show the CVEs in short form: two CVEs with the highest severity and the number of the remaining CVEs (for example, CVE The Common Vulnerabilities and Exposures (CVE) system provides a reference-method for publicly known information-security vulnerabilities and exposures.-123, CVE-456 and 10 others).

To see the full output:

• use the -o flag to print the full output to a file

• use the -j flag to see the output in JSON

Output in CloudGuard

The scan results shown in the CloudGuard portal include both the particular vulnerabilities found in the image and their assessment against the attached policy.

Upon scan completion, the Scan Engine sends the results to the associated environment in CloudGuard.

To see the scan results, do one of these:

• Navigate to Workload Protection > Containers Assets > Images. This page shows images scanned in CI/CD pipeline.

• Navigate to Events > Posture Findings and filter the view for the ShiftLeft Platform and ShiftLeft Image Entity Type. This page shows posture findings in your images. To learn more about posture findings, see Events.

• Click a ShiftLeft The ShiftLeft tool scans source code, containers and serverless functions, looking for vulnerabilities including those associated with the Log4j tool. This tool alerts the security and DevOps teams if any vulnerabilities are detected in the pre-build phase, ensuring that vulnerable code is not deployed. image to open its page. Go to the Vulnerabilities tab to see vulnerable entities in the image.

  To learn more about vulnerabilities, see Agentless Workload Posture.

Known Limitations

• The image to be scanned should be exported by repository:tag and not by repository@digest.