Skip to main content
Version: 1.7

Run a security scan

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

Run 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 a new scan.
note

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

caution

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

If you encounter issues, run the security checks individually. For more information, see Run a security scan below.

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

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

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

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

Run a security scan​

To run an individual security check:

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

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

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

The default maximum runtime for a check cycle is 24 hours. If the cycle reaches the maximum runtime, the check 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 check.

Stop a scan​

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

  1. Select the additional actions button Additional actions in the check row.
  2. Select Stop.