Skip to main content
Version: 1.5

Running a security scan

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

Running a security scan for a project layer​

To run a security scan for a project layer:

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

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

caution

If you start a large number of security scans at the same time—several dozen or more—the Solar AppScreener tool might encounter issues due to its architecture.

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

Features of running 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 it can run the scans and which tasks to execute. This feature means you don't have to manually separate scans into different layers. You can also run scans even when the layer contains different types of tools.

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

  1. If the project layer contains at least one scan that uses a tool with direct API integration, you can start the scan. In this case, the system runs only the scans that use this tool. It 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, you can't start the scan.

Running a security scan​

To run an individual security scan:

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

When you start a security scan, its status changes to Scanning.

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

The default maximum runtime for a scan cycle is 24 hours. If the cycle reaches the maximum runtime, the scan status changes to Not completed, and the process ends. The system also assigns the Not completed status 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 additional actions button Additional actions in the scan row.
  2. Select Stop.