Skip to main content
Version: 1.5.1

Start a security check

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

Start a security check for a project layer​

To start a security check 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, all security checks in the layer will start.

caution

Solar AppScreener may encounter issues when you start a large number of security checks at the same time—several dozen or more—because of the tool's architecture.

If you encounter issues, start the security checks individually. For more information, see Start a security check below.

Starting security checks 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 start and which tasks to run. This feature lets you avoid manually separating checks into different layers and start checks even when the layer contains different types of tools.

In this case, whether you can start a security check 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 checks. In this case, only checks that use this tool will start. 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 checks.

Start a security check​

To start 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 a security check starts, its status changes to Scanning.

After the check finishes successfully, its status changes to Done.

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