> For the complete documentation index, see [llms.txt](https://docs.sprinto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinto.com/monitors/extended-checks-in-mdm-tool-comms/jumpcloud-extended-device-checks.md).

# JumpCloud – Extended Device Checks

### **Overview**

Sprinto now supports deeper integration with **JumpCloud** to monitor two additional device compliance checks:

* **Screenlock** – Ensures staff devices automatically lock after a set period of inactivity.
* **Antivirus** – Ensures staff devices have an approved antivirus solution installed and running.

These checks complement the existing JumpCloud integration, which already monitors operating system versions and disk encryption status.

{% hint style="info" %}
This feature is available to all Sprinto customers who have integrated JumpCloud as their MDM provider.
{% endhint %}

### **How It Works**

Sprinto retrieves device configuration and application data from JumpCloud using its API.

* **Screenlock status** is determined by reading the “Screen Saver” policy applied to managed devices.
* **Antivirus status** is determined by matching installed applications from JumpCloud’s inventory against Sprinto’s supported antivirus list.

A monitor passes if:

* Screenlock is set to **15 minutes or less**, and
* An approved antivirus is installed and running.

If either condition fails, the monitor will show as failing in Sprinto.

### **Prerequisites**

Before enabling these checks in Sprinto, ensure:

* Your JumpCloud account has **Admin** access.
* Devices are enrolled in JumpCloud and grouped appropriately.
* You know the antivirus product name installed on your organisation’s devices.

### **Configuring Screenlock in JumpCloud**

Follow these steps to create or update the required screenlock policy:

1. Log in to the **JumpCloud Administrator Portal**.
2. Navigate to **Policy Management**.
3. Click the **green + button** to add a new policy.
4. Name the policy **exactly** as `Screen Saver`.
5. Set the **Auto Screen Lock** timeout to **15 minutes or less**.
6. Select the target **device group**.
7. Save the policy.

{% hint style="info" %}
If the policy is not assigned to a device group, it will not take effect. Repeat the steps for both **macOS** and **Windows** devices.
{% endhint %}

### **Configuring Antivirus Detection**

Sprinto checks for antivirus installation using JumpCloud’s **Applications List API**.

1. Confirm your antivirus product name matches one in Sprinto’s supported list (examples include Microsoft Defender, CrowdStrike Falcon, Sophos Endpoint, Malwarebytes, Bitdefender, McAfee, and Kaspersky).
2. Ensure the antivirus is installed and running on all managed devices.
3. Sprinto will automatically detect and pass the check if the antivirus name matches the supported list.

### **Supported Antivirus Products**

Sprinto supports a wide range of antivirus solutions for both macOS and Windows.

### **Troubleshooting**

<table><thead><tr><th width="149.85546875">Issue</th><th width="245.4453125">Possible Cause</th><th>Resolution</th></tr></thead><tbody><tr><td>Screenlock check is failing</td><td>Policy name is incorrect or not assigned to devices</td><td>Rename policy to <strong>Screen Saver</strong> and ensure it is assigned to the correct device group</td></tr><tr><td>Screenlock check is failing</td><td>Timeout set above 15 minutes</td><td>Reduce timeout to <strong>15 minutes or less</strong></td></tr><tr><td>Antivirus check is failing</td><td>Antivirus not in supported list</td><td>Verify product name and confirm with Sprinto support</td></tr><tr><td>Antivirus check is failing</td><td>Antivirus not installed on device</td><td>Install antivirus and verify installation in JumpCloud’s device applications list</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.sprinto.com/monitors/extended-checks-in-mdm-tool-comms/jumpcloud-extended-device-checks.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.