Skip to main content
Version: 1.6

Launching a security scan

System users can run all security scans within a project layer or individual scans.

Launching a security scan for a project layer​

To launch a security scan for a project layer, follow these steps:

  1. Go to Projects → Project name → Project layers.
  2. Select Start a new scan.
note

When you select Start a new scan, the system runs all security scans in the layer.

caution

Launching a large number of security scans at the same time—several dozen or more—by using Solar AppScreener can cause issues because of the tool's architecture.

If you encounter issues, run the security scans separately. For more information, see "Launching a security scan" below.

Considerations for launching security scans in project layers with different tools​

If a project layer contains security scans that use different types of tools, for example, tools with direct API integration and external CLI tools, the system automatically determines whether the scans can run and which tasks to execute. This feature means you don't have to manually separate scans into different layers, and you can launch scans even when the layer contains different types of tools.

In this case, whether the security scan can run depends on the following conditions:

  1. If the project layer contains at least one scan that uses a tool with direct API integration, the user can start the scan. In this case, the system runs only scans that use this tool. The system skips scans that use external CLI tools that can't run in Kubernetes.
  2. If the project layer contains only scans that use CLI tools that can't run in Kubernetes, the system can't start the scan.

Launching a security scan​

To launch an individual security scan, follow these steps:

  1. Go to the required project layer under Projects → Project name → Project layers.
  2. Select the More actions button More actions in the scan row.
  3. Select Start a new scan.

When a security scan starts, its status changes to Scanning.

After the scan completes successfully, its status changes to Completed.

The default maximum run time for a scan cycle is 24 hours. If the cycle reaches the maximum run time, the scan status changes to Not completed, and the process ends. The status also changes to Not completed if an error occurs at any stage of the scan.

Stopping a scan​

You can also force a security scan with the In progress status to stop. To do this:

  1. Select the More actions button More actions in the scan row.
  2. Select Stop.