Why Is there a 5-Item Selection Limit in Data Scans?
In CYRISMA, data scans are essential for identifying vulnerabilities and potential risks across various environments. To ensure optimal performance and prevent system overload, a limitation has been introduced where users can only select up to five items during a single data scan. This article explains the reasoning behind this limitation and offers alternatives for users needing to scan larger datasets.
Written by Liam Downward
Updated at February 25th, 2025
- User Manual
- Self Onboarding Guide
- Agents
- The Cyber Risk Assessment Process
- PSA Integrations
- General Questions and Troubleshooting
- The Cyber Risk Assessment Process (Video Tutorials)
- Sales and Prospecting Articles
- CYRISMA Partner Portal Access
- Glossary
- API Documents
- CYRISMA Change Log
- Support Ticket SLA
- Billing Questions
Table of Contents
1. System Performance & Resource Allocation
Shared Cloud Agents:
CYRISMA utilizes shared ServiceMa Cloud Agents to conduct data scans.
When users initiate extensive scans (e.g., scanning thousands of mailboxes), it can overburden the shared infrastructure.
Heavy scanning loads can lead to queueing delays as agents are tied up, impacting other users.
Microsoft Throttling:
When scanning cloud environments, especially large datasets like Office 365 mailboxes, hitting Microsoft's servers too frequently can trigger rate-limiting or throttling.
Throttling significantly slows down scan speeds, sometimes extending scan durations to weeks.
2. System Stability & Reliability
Preventing Scan Failures:
In the past, unrestricted scans caused many instances where scans failed or timed out, leading to incomplete results.
The 5-item limit helps maintain scan reliability and ensures that results are delivered promptly.
Optimizing Resource Use:
By limiting the number of items scanned concurrently, the platform can better manage its resources, ensuring fair use across all clients.
Alternatives & Solutions
1. Install a Local Cloud Agent
Dedicated Scanning:
CYRISMA offers the option to install a Local Cloud Agent on your own infrastructure.
With a local agent, the 5-item limit is removed, allowing you to scan as many items as your local resources can handle.
Benefits of Local Agents:
Faster Scans: No queueing for shared cloud agents.
No Throttling: Microsoft is less likely to throttle requests from your dedicated agent.
Greater Control: Manage scans directly from your infrastructure.
2. Batch Scanning Approach
If using the shared cloud agent, consider breaking larger scans into smaller batches of five.
While this requires more manual scheduling, it helps prevent system overload and scan failures.
3. Contact CYRISMA Support
If you encounter consistent challenges or need assistance setting up a Local Cloud Agent, reach out to CYRISMA Support for guidance and documentation.
Best Practices
Opt for Local Agents: For organizations with large datasets, installing a local cloud agent will drastically improve scanning efficiency.
Plan Scan Schedules: Schedule scans during off-peak hours to minimize the impact on shared cloud resources.
Monitor Scan Performance: Regularly review scan logs to ensure successful completions and address any issues proactively.
Conclusion
The 5-item selection limit in data scans was implemented to balance system performance, reliability, and fair resource usage across CYRISMA’s user base. By leveraging options like the Local Cloud Agent and following best practices, users can optimize their scanning processes while maintaining platform stability.
For further assistance or more details, contact CYRISMA Support.