> For the complete documentation index, see [llms.txt](https://docs.expel.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.expel.io/detection-strategy-guides/d-m/jumpcloud-detection-strategy.md). # Jumpcloud Detection Strategy ## Product Overview JumpCloud is a cloud‑based directory and identity platform designed to help organizations securely manage users, access, and devices from one place — without the need for traditional on‑premises directory infrastructure (like Active Directory) or stitching together lots of separate tools JumpCloud provides a unified, cloud‑native directory platform that centralizes identity and access management (IAM), device management, and resource access in a single console. It supports cross‑platform environments (Windows, macOS, Linux, and mobile) and enables secure access to networks, applications, files, and systems. Expel’s integration with Jumpcloud currently focuses on the following key areas of detection: * Attempted use of expired Jumpcloud API keys * Suspicious authentication events & admin activity * Possible bypass of MFA * Suspicious successful authentications * Risky configuration changes ## Detection Strategy for Identity Integrations ### Detection Our identity security detection strategy focuses on optimizing user authentication and application access activity monitoring. This is achieved by directly integrating with identity providers and polling for audit and data access logs. These events are analyzed through a combination of raw log analysis and security alert processing, which are then evaluated by our detection engine for signs of suspicious login activity or post-exploitation behavior. When a threat is identified, our automated response bot, Ruxie, enriches evidence fields with first- and third-party threat intelligence. Additionally, Ruxie queries a wide range of technologies to provide analysts with critical investigative information and related events. ### Response For alerts that contain source user information, identity technologies can provide rich context such as groups, locations, job title, and other pieces of metadata. Additionally, for cloud and SaaS alerts, identity technologies are queried to provide verbose context around user login behavior. This allows analysts to investigate the underlying session behind the activity they are triaging. To learn more about our overall approach to detection strategy, see [About Detection Strategy](/workbench-reference/detections/about-detection-strategy.md) in the Help Center. ## What We Support for JumpCloud To see a comprehensive list of the most up-to-date Expel detection rules, vendor detection rules, opt-in detections, and available DUETs (did you expect this) that we support for JumpCloud, you can visit the [Detections page](https://workbench.expel.io/tools/detections/all?filter=%7B%22supportedTech%22%3A%7B%22is%22%3A%5B%22jumpcloud%3A1.0.0%22%5D%7D%7D) in Workbench or ask your Sales or Support rep for the most recent download. | **Supported versions** | | | ------------------------------------- | ----------------------------------------------------------------------- | | **Supported event log sources** | | | **JumpCloud detection rules support** | No. | | **Detection rules written by Expel** | Yes. | | **Hunting support** | No. Hunting is not currently available for this integration. | ## Additional Details and Common Questions ### DUET A DUET (did you expect this) rule flags certain events as needing an immediate verification or notification, and bypasses the normal internal event triage process. The events subject to DUET rules contain behaviors that are not typically indicative of true security incidents, as they are related to policy violations or potential risk. There are a number of workflows that a DUET may follow. When enabled, the activity will be flagged for investigation and will be routed to you (rather than to us) to take a specified first action. To see the specific DUET rules currently supported for this integration, visit the [Detections page](https://workbench.expel.io/tools/detections/all) in Workbench. --- # 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.expel.io/detection-strategy-guides/d-m/jumpcloud-detection-strategy.md?ask=&goal= ``` `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.