> 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/s-z/tanium-xem-core-detection-strategy.md). # Tanium XEM Core Detection Strategy ## Product Overview Tanium XEM Core is a converged endpoint management (XEM) platform that provides real-time visibility, control, and response across distributed endpoints at scale. The platform queries and acts upon every endpoint in seconds, providing a live, accurate picture of the entire IT environment in a single console. This comprehensive, real-time data allows teams to ask questions about their environment and receive immediate answers, enabling proactive cyber hygiene and rapid incident investigation. It combines deep asset inventory and patch management with endpoint detection and response (EDR), empowering teams to not only identify and remediate system weaknesses but also to hunt for advanced threats and execute immediate, targeted responses. ## Detection Strategy for Tanium XEM Core ### Detection Our endpoint detection strategy focuses on two common signal types: process and network events. By integrating directly with EDR vendors, we can process security alerts to extract evidence and normalize event details. These normalized signals are then processed through our detection engine to look for signs of post-exploitation activity. In addition to categorical handling of vendors' security alerts, Expel maintains a large library of behavioral detections to augment vendor detections. When a threat is detected, our automated response bot, Ruxie, takes action by enriching evidence fields with first- and third-party threat intelligence. Additional Ruxie actions query a wide span of technologies directly to arm analysts with key pieces of investigative information and related events. ### Response Endpoints provide rich context for processes and also support other types of Expel Alerts. For example, we use source device identification across a number of alert types when a source IP or hostname is available, because it provides rich context about the actor behind the activity. Additionally, endpoints provide valuable information for network alerts to help identify what process triggered a connection. 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 Tanium XEM Core To see a comprehensive list of the most up-to-date Expel detection rules, vendor detection rules, opt-in detections, and available DUETs (**d**id yo**u** **e**xpect **t**his) that we support for Tanium XEM Core, you can visit the [Detections page](https://workbench.expel.io/tools/detections/all?filter=%7B%22supportedTech%22%3A%7B%22is%22%3A%5B%22tanium%3A1.0.0%22%5D%7D%7D) in Workbench or ask your Sales or Support rep for the most recent download. | **Tanium XEM Core detection rules support** | Yes. | | ------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Detection rules written by Expel** | Yes. | | **Investigative support through Workbench** |

Yes. The integration provides multiple capabilities for investigation, including:


| | **Hunting support** | Yes. Hunting is available for this integration to customers who purchase this option. Contact your Sales or Support rep for help understanding the hypotheses and objectives for each hunting technique. For a full list of techniques by integration, see [Hunting Techniques](broken://pages/RmMQK8aDsnWXvU182utw) in the Help Center. | ## Additional Details and Common Questions ### Console Access A vendor alert does not typically include all of the contextual timeline activity surrounding the event of interest. Because this integration does not allow us to get all necessary data via the API, we will ask you for a certain level of console access during onboarding. The level of access that we require is meant to support essential triage and research activities, and to help us determine the vector and extent of attacker activity for an identified threat. At minimum, we will ask for visibility into alert data, timeline events recorded, and live response/real time response shell (if applicable). --- # 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/s-z/tanium-xem-core-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.