Source: https://sprinto-test.docs-staging.pageloop.ai/monitors/frequently-asked-questions # Frequently Asked Questions Here’s the draft for the article: ## **Monitors – Frequently Asked Questions (FAQ)** --- This FAQ covers common questions about Sprinto’s **Monitors** section, including how checks work, when to take action, and how to resolve failing or pending monitors. --- #### General **1. What is the Monitors section in Sprinto?**\ The Monitors section tracks technical and procedural controls across your systems. These include authentication settings, infrastructure configurations, workflow reviews, encryption, backups, and more. **2. What types of monitors are available?**\ Monitors fall into two categories: - **Automated** (from integrations like AWS, GitHub, GWS) - **Workflow-based** (manual checks like onboarding reviews, DR tests) **3. Where can I find the list of all active monitors?**\ Navigate to **Monitoring > Check History**. You can filter by integration, check type, and status. --- #### Troubleshooting & Resolution **4. Why is a monitor marked as “Failing”?**\ The check failed to meet compliance requirements or no evidence was submitted to validate it. **5. How do I resolve a failing monitor?**\ Click the monitor entry, review its description, upload required evidence or take system action (e.g., enable MFA), and click **Mark as Resolved**. **6. What does “Pending Evidence” mean?**\ The check requires documentation or screenshots to confirm compliance. No automatic status is possible without this evidence. **7. How often are checks refreshed?**\ Most integration-based checks are refreshed **every 4–12 hours**. Dr. Sprinto syncs devices every few hours when online. **8. Why does a resolved check fail again later?**\ Sprinto re-evaluates monitors regularly. If a system change rolls back a control (e.g., MFA is disabled), the check status may revert. --- #### Workflow Checks **9. What are workflow checks?**\ These are manually tracked compliance actions, such as staff access reviews, password policy enforcement, and DR test uploads. **10. How do I complete a workflow check?**\ Click the check → read instructions → upload the required file or evidence → click **Mark as Resolved**. **11. Can I exclude a workflow check?**\ Yes. If a check doesn’t apply to your organisation, select **Mark as Not Applicable** and provide justification. --- #### User Decisioning **12. What is user decisioning?**\ It’s the process of marking detected users as **In Scope**, **Not in Scope**, or **Resolved** based on whether they require control enforcement. **13. Which platforms support user decisioning?**\ Supported for AWS, GitHub, Bitbucket, Azure, Google Workspace, Office 365, Okta, and others. **14. Should I exclude service accounts?**\ Yes, provided they’re truly non-user accounts and their access is justified. Add comments when marking them as not in scope. --- #### Dr. Sprinto & Devices **15. What does Dr. Sprinto monitor?**\ It checks for screen-lock, OS patching, device health, and auto logout settings on Windows/macOS endpoints. **16. What if Dr. Sprinto shows my device as inactive?**\ The agent may be uninstalled, outdated, or disconnected from the internet. Reinstall and verify activity status. **17. Can I report device health manually?**\ Yes. Use the **Employee Portal** to complete tasks like confirming antivirus status or screen-lock enforcement. **18. What if Dr. Sprinto shows my device as inactive?** Older device entries are marked as **‘Not in use’** to prevent them from being monitored or flagged by Sprinto. **19. What are the currently Supported OS versions for Dr. Sprinto?** | Operating System | Minimum Supported Version | Recommended / Nudge Version | | ----------------------------------------- | ----------------------------------------- | --------------------------- | | macOS / Mac OS X / mac / macos / appleosx | >= 13.1 or 12.6.2 or 11.7.2 | >= 11.x | | Windows (win32 / winrt) | >= 10.0.22000 or 10.0.19045 or 10.0.19044 | – | | AWS Workspace | >= 10.0.14393 | >= 10.0.10240 | | Fedora | >= 36 | – | | Pop!\_OS | >= 22.4 | – | | Manjaro | >= 22.0.0 | – | | Debian | >= 11.11 | >= 12.9 | | Linux Mint | >= 19.x, 20.x, or 21.x | – | | Kali Linux | >= 2022.4 | – | | Ubuntu | >= 22.4.1 or \~20.4.5 or \~18.4.6 | 22.4.x, 20.4.x, or 18.4.x | | Linux (Generic) | >= 22.4.1 or \~20.4.5 or \~18.4.6 | 22.4.x, 20.4.x, or 18.4.x | | Elementary OS | >= 6.x or ^5.x | – | | KDE Neon | >= 5.26 | – | | Oracle Linux (ol) | >= 9.1 or ^8.7 or ^7.9 | – | | Deepin | >= 20.8 | – | | Ubuntu Kernel | >= 5.4.x | – | --- #### Miscellaneous **18. Can I customise which monitors are active?**\ Some monitors are linked to your selected compliance frameworks (e.g., SOC 2, ISO 27001). Contact Support to customise exclusions or scope. **19. Are monitors audit-ready?**\ Yes. Monitors can be used as proof during external audits. Ensure evidence uploads include reviewer name, date, and context. **20. How do I export a list of all monitors?**\ Use the **Export** option from the Monitoring dashboard to download check history, statuses, and comments.