> For the complete documentation index, see [llms.txt](https://docs.stoik.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stoik.io/email-security/compromised-accounts.md).

# Compromised accounts

Email Security detects mailboxes showing signs of unauthorized access or suspicious activity. The Stoïk SOC reviews every alert and contains the account when needed.

## Alerts table

Alerts are listed in `Email Security` > `Compromised accounts`. The **Detected signals** column lists the signals behind each alert, grouped by type with their number of occurrences (e.g. `3 Impossible travels · 2 Abnormal behaviors`).

Click an alert to open its details.

## Alert details

### Information

* **Detection date:** when the compromise was detected
* **Status:** Open or Closed
* **Validity:** True Positive or False Positive
* **Protected user:** the mailbox that was targeted
* **Actions:** None, MFA reset, Password reset, etc. See [Remediation actions](https://docs.stoik.io/email-security/remediation-actions.md#compromised-accounts).
* **Criticality:** Low, Medium, High, or Critical

### User profile

A baseline of what's normal for this user, computed from the last 13 weeks of sign-in activity. Use it as a reference when reading the timeline.

<table><thead><tr><th width="235.86328125">Row</th><th>What it tells you</th></tr></thead><tbody><tr><td>Usual location</td><td>The top countries this user signs in from (with the share of sign-ins for each).</td></tr><tr><td>Usual device</td><td>The operating system and browser the user typically uses.</td></tr><tr><td>Usual sign-in pattern</td><td>A weekly heatmap showing when the user is normally active.</td></tr><tr><td>VPN usage</td><td>How often this user signs in through a VPN.</td></tr><tr><td>Email throughput</td><td>How many emails this user sends per day on average, with their historical peak.</td></tr><tr><td>Coverage</td><td>The number of sign-ins the baseline is computed from.</td></tr></tbody></table>

For example, if the user normally signs in from Paris on weekdays between 9 AM and 6 PM, a sign-in from Moscow at 3 AM is a strong anomaly.

## Activity timeline

The signals that triggered the alert and the actions taken by the Stoïk SOC, grouped by day, most recent first.

### Detected signals

* Impossible travel detected: two sign-ins too far apart given the time between them.
* Sign-in from high-risk country: sign-in from a country flagged in our threat database.
* Sign-in from unusual location / network / device / browser: the user signed in from a context they don't usually use.
* Sign-in at unusual time: sign-in outside of the user's normal working hours.
* Automated access detected: sign-in coming from a headless browser or automation tool.
* Suspicious app access: access from a tool often used by attackers (e.g. Graph Explorer, Azure CLI).
* High email volume detected: the user sent significantly more emails than usual in 24 hours.
* Suspicious inbox rule created: a rule was created on the mailbox that auto-deletes, forwards or hides messages.
* Authentication method added or removed: an MFA method was changed on the account.
* Sign-in from known malicious IP: sign-in from an IP listed in our threat feed.
* VPN used: sign-in via VPN, on a user who rarely uses one.
* Session reused across devices: the same session ID was seen from two different OS/browser combinations.
* Microsoft Entra flagged high risk: Microsoft's own identity protection raised an alert.
* Failed MFA attempt: an MFA challenge failed.

### Alert handling

<table><thead><tr><th width="235.421875">Step</th><th>Meaning</th></tr></thead><tbody><tr><td>Alert creation</td><td>When the compromise was detected.</td></tr><tr><td>Alert confirmation</td><td>When the alert was ingested and confirmed in the Stoik system.</td></tr><tr><td>Alert processing</td><td>When a SOC analyst started investigating the alert.</td></tr><tr><td>Alert closure</td><td>When the alert was resolved and closed.</td></tr></tbody></table>

**Alert creation** and **Alert confirmation** always appear. **Alert processing** and **Alert closure** appear as the alert progresses.

### SOC actions, notes and emails

* **SOC actions**: the [remediation actions](https://docs.stoik.io/email-security/remediation-actions.md#compromised-accounts) taken to contain the account.
* **Analyst notes**: context written by the Stoïk SOC on how the alert was investigated, when relevant.
* **Email exchanges**: the emails exchanged with your organization about the alert, when there are any.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stoik.io/email-security/compromised-accounts.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
