> 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/n-q/proofpoint/proofpoint-insider-threat-management-via-siem-detection-strategy.md).

# Proofpoint Insider Threat Management (via SIEM) Detection Strategy

## Product Overview <a href="#h_01k10z26dx1e1mr6rv50zmy2z2" id="h_01k10z26dx1e1mr6rv50zmy2z2"></a>

Proofpoint Insider Threat Management (ITM) is a people-centric SaaS solution designed to detect, prevent, and respond to insider threats and data loss at the endpoint. It achieves this by providing deep visibility into user activities, correlating user behavior with sensitive data movement across various channels (endpoint, email, cloud), and offering real-time alerts with rich context. This allows it to accelerate investigations and provide irrefutable evidence of wrongdoing by identifying malicious, negligent, or compromised insiders.

## Detection Strategy for Identity Integrations <a href="#h_01k10z26dzw0ghrv1fxa4z8ggk" id="h_01k10z26dzw0ghrv1fxa4z8ggk"></a>

### Detection <a href="#h_01k10z26dzthjy4zpc1ja2kckb" id="h_01k10z26dzthjy4zpc1ja2kckb"></a>

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.&#x20;

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 <a href="#h_01k10z26e1jwfj6y8v9253rfja" id="h_01k10z26e1jwfj6y8v9253rfja"></a>

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 Proofpoint Insider Threat Management (via SIEM) <a href="#h_01k10z26e3b39mvy13vcsjg73a" id="h_01k10z26e3b39mvy13vcsjg73a"></a>

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 Proofpoint Insider Threat Management (via SIEM), you can visit the [Detections page](https://workbench.expel.io/tools/detections/all?filter=%7B%22supportedTech%22%3A%7B%22is%22%3A%5B%22observeit_siem%3A1.0.0%22%5D%7D%7D) in Workbench or ask your Sales or Support rep for the most recent download.

| **Supported versions**                                                      | <ul><li>All versions supported.</li></ul>                                                                                                              |
| --------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Supported platforms**                                                     | <ul><li>Sumo Logic.</li></ul>                                                                                                                          |
| **Proofpoint Insider Threat Management (via SIEM) detection rules support** | Yes.                                                                                                                                                   |
| **Detection rules written by Expel**                                        | No.                                                                                                                                                    |
| **Investigative support through Workbench**                                 | <p>Yes. We are able to take the following investigative actions to gather data for triage and investigation of events.</p><ul><li>Query User</li></ul> |
| **Hunting support**                                                         | No. Hunting is not currently available for this integration.                                                                                           |

## Additional Details and Common Questions <a href="#h_01k10z26eefjt7vaz1djarv4px" id="h_01k10z26eefjt7vaz1djarv4px"></a>

### Console Access <a href="#h_01k10z26ef47q61hndny4z3559" id="h_01k10z26ef47q61hndny4z3559"></a>

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.&#x20;

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).

### DUET <a href="#h_01k10z26eg02fw9624mxbkgan8" id="h_01k10z26eg02fw9624mxbkgan8"></a>

A DUET (**d**id yo**u** **e**xpect **t**his) 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.&#x20;

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/n-q/proofpoint/proofpoint-insider-threat-management-via-siem-detection-strategy.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.