Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Create a Support Ticket
  • Partner Portal
  • Cyrisma MSP Dashboard
  • Home
  • General Questions and Troubleshooting
  • Agent Troubleshooting

Understanding the 'CYRISMA Cloud Agent' Idle Status

The CYRISMA Cloud Agent may display an "Idle" or "Down" status in specific situations. This article explains the reasons for this status and provides guidance on how to resolve it.

Written by Liam Downward

Updated at November 27th, 2024

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • User Manual
    Overall Risk Dashboard Agent Status Report Builder Data Scan Vulnerability Scan Secure Baseline Compliance Mitigation Dark Web MSP Interface Instance Admin
  • Self Onboarding Guide
  • Agents
  • The Cyber Risk Assessment Process
  • PSA Integrations
  • General Questions and Troubleshooting
    Agent Troubleshooting Scanning Troubleshooting
  • The Cyber Risk Assessment Process (Video Tutorials)
  • Sales and Prospecting Articles
  • API Documents
  • Support Ticket SLA
  • Billing Questions
+ More

Table of Contents

Why is the CYRISMA Cloud Agent Idle or Down? Steps to Resolve the Idle Status 1. Designate a Cloud Server 2. Schedule a Scan 3. Request Scan Prioritization (Optional)

Why is the CYRISMA Cloud Agent Idle or Down?

The CYRISMA Cloud Agent remains in a down or idle state when:

  1. No cloud server has been designated.
  2. A data scan has not been initiated.

The agent requires an active cloud server and an ongoing data scan to function properly.


Steps to Resolve the Idle Status

1. Designate a Cloud Server

  • Assign a machine to act as the cloud server. This step is essential for enabling the Cloud Agent to start operations.

2. Schedule a Scan

  • Once a cloud server is designated, schedule a scan via the CYRISMA platform. This will activate the Cloud Agent.

3. Request Scan Prioritization (Optional)

  • If an urgent scan is needed, submit a support ticket requesting prioritization.
  • Your scan will begin shortly after the ticket submission.
cyrisma cloud agent cloud agent cyrisma idle status idle

Was this article helpful?

Yes
No
Give feedback about this article

Related Articles

  • Why Agent-Based Scanning is Recommended
  • Why Are CYRISMA Agents Not Showing Up for Provisioning?
  • How to Change the Secure Baseline Profile for Targets
Expand