How to Resolve Issues with Setting Up Cloud Scans in CYRISMA
If you're experiencing difficulties while setting up cloud scans, this guide provides troubleshooting steps and instructions to ensure your scans run smoothly.
Written by Liam Downward
Updated at November 27th, 2024
- User Manual
- Agents
- The Cyber Risk Assessment Process
- API Documents
- General Questions and Troubleshooting
- The Cyber Risk Assessment Process (Video Tutorials)
- Sales and Prospecting Articles
- CYRISMA Partner Portal Access
- Glossary
- CYRISMA Change Log
- Support Ticket SLA
- Onboarding Framework
- PSA Integrations
- Billing Questions
- Self Onboarding Guide
Table of Contents
Steps to Resolve Cloud Scan Issues
1. Setting Up a Scheduled Scan
-
Verify the Cloud Agent:
Ensure that a cloud agent has been created and deployed correctly. The cloud agent is necessary to initiate and complete cloud scans. -
Use a Local Agent if Needed:
If a cloud agent isn't available, you can designate a local CYRISMA instance as the cloud agent to perform the scans. This allows flexibility when setting up scans.
2. Designating a Cloud Server
-
Assigning a Machine as the Cloud Server:
Designate a machine as the cloud server for scans. This server will act as the central hub for performing scans on designated targets. -
Schedule the Scan:
After designating the cloud server, set up a scan schedule within the CYRISMA platform.
Prioritizing Your Scan
If you need the scan to run urgently:
- Submit a support ticket requesting scan prioritization.
- Once submitted, your scan will begin within 30 minutes of the ticket submission.