Status

Scan status

When using Kubescape to scan your cluster for misconfigurations and other issues you get results in a report. The different status options are as follows (please note: some statuses have sub-statuses):

• Failed - Kubescape scanned all the resources applicable to the control and found at least one failed resource that was not excluded.
• Passed – Kubescape scanned all the resources applicable to the control and none of them failed.
• Passed (Irrelevant) – Kubescape could not perform a scan as it found no applicable resources. As a result, it could not have failed.
• Passed (Ignored) – Kubescape performed a scan and found that some or all failed resources are in ignore state. As a result, it could not have failed.
• Action required (Configuration) – Kubescape did not perform a scan due to incomplete setup of the control. The specified control requires arguments or a default value.
• Action required (Review) – Kubescape scanned all the resources applicable to the control. The output of the scan needs to be reviewed and approved manually by a user.
• Action required (Manual review) – Kubescape did not perform a scan, as the specified control cannot be automated. The user must perform a manual review.
• Action required (Integration) – Kubescape did not perform a scan due to incomplete setup of the scanner.

📘

Example for Action required (Integration) status

No cloud integration and the control requires access to the managed API server or you did not run the scan with --enable-host-scan while the control requires worker node information like Kubelet settings.