Troubleshooting CSPM Scan Failures

Overview

This guide explains how to troubleshoot Cloud Security Posture Management (CSPM) scans that fail during execution, specifically focusing on authentication and invalid credential errors. You will learn how to:

• Interpret scan status indicators
• Identify failed jobs
• Access and review error logs
• Resolve invalid credential errors by recreating cloud integrations

---

Prerequisites

• Access to the Cloud Security Misconfigurations dashboard
• Access to the Integrations management dashboard

---

Understanding Scan Status

Scan status is displayed using icons in the projects list accordion.

• Completed – All jobs executed successfully
• Partially Completed – At least one job succeeded and at least one job failed
• Failed – All jobs failed
• Stopped – Scan was manually stopped by the user

Hover over the status icon to view the tooltip message for more details.

Icon colors indicate result state. For example:

• Red indicates a failed scan
• Gray indicates a manually stopped scan

---

Steps to Troubleshoot Failed Scans

1. Check Overall Scan Status

1. Navigate to Cloud Security Misconfigurations → Projects
2. Locate the scan project
3. Review the Status Icon in the accordion
4. Hover over the icon to see the status message
5. Click the arrow icon to expand and view the list of created jobs, including the ones that failed

If the scan shows as failed, proceed to review logs.

---

2. Open Scan History

1. Click the project name to open the Findings dashboard
2. Navigate to the History tab
3. Review the list of historical scans performed
4. Check the Status column for failed entries

---

3. View Error Logs

1. Open the three-dot menu for the affected scan
2. Click Error
3. Expand error entries using the arrow button
4. Review detailed logs to understand why the scan failed

Only partially successful or failed jobs will display error details.

There may be a single log or multiple error logs for a scan.

---

Common Failure Scenarios

Invalid Credentials (Authentication Failed)

The error log may indicate that authentication failed because the provided credentials for the cloud account are invalid.

Action:

1. Identify the integrated connector associated with the failed scan.
2. Navigate to Integrations → Connected Providers to view all active cloud integrations.
3. Delete the connector with invalid credentials (credentials cannot be edited once saved).
4. Create a new integration with the correct credentials.
5. Return to Cloud Security Misconfigurations and create a new scan using the updated connector.

Temporary Processing Issue

Example error message may indicate:

• Temporary internal processing error
• Retry recommended

Action:

• Re-run the scan
• Contact support if the issue persists

These logs do not expose sensitive data.

---

When to Contact Support

Contact support if:

• Repeated failures occur after retrying
• Newly created integrations still result in authentication errors
• Logs indicate unknown processing errors

Include relevant error log details when submitting a support request.

---

Field Reference

Field	Description	Example
Status Icon	Overall scan result indicator	Completed / Partial / Failed / Stopped
History Tab	Displays all past scan executions	History
Status Column	Shows result of each historical scan	Failed
Three-dot Menu	Access error details	Error
Error Logs	Detailed job failure information	Authentication failed
Connected Providers	Dashboard listing all cloud integrations	Integrations