Skip to main content
Version: 1.6.1

Running a security scan

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

Running a security scan for a project layer​

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

  1. Go to Projects → Project name → Security 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

Running a large number of security scans at the same time—several dozen or more—with Solar AppScreener can cause issues due to the tool's architecture.

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

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

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

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

  1. If the project layer includes 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. The system skips scans that use external CLI tools that can't run in Kubernetes.
  2. If the project layer includes 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, follow these steps:

  1. Go to the required project layer under Projects → Project name → Security 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 Ready.

The default maximum runtime for a scan cycle is 24 hours. If the cycle reaches its maximum runtime, the scan status changes to Not completed, and the process ends. The system also assigns the Not completed status when 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.