0xSENTRY TRACE / SIMULATION LAB

How 0xSENTRY catches phishing.

Follow an email from Exchange to your security team. Inspect the evidence that changes the decision and the alert your analyst actually receives.

The case

A finance employee receives an email asking them to change a payment process. Would the request warrant a second look?

The run

0xSENTRY executes its monitoring worker on synthetic mail. A test adapter stands in for Microsoft Graph and Sentinel. The AI decision uses a controlled test response.

Ready
  1. 01Mail intake
  2. 02Evidence
  3. 03Trace
  4. 04Queue
  5. 05SIEM
Start with the message Choose a case, then run the worker or inspect the recorded stages one at a time.

Exchange Online

Microsoft Graph

0

Waiting for a message

Finance Lab inbox

0xSENTRY Trace

Email inspection

SIMULATED AI

Awaiting evidence

Body, sender and local rules

Microsoft Sentinel

Sentinel test receiver

0

Queue empty

Waiting for a decision

Event stream

00 EVENTS
  1. Select a case and run it, or advance one event at a time with Step.

The worker uses temporary records and rolls them back after each run. Analyst controls rehearse the response in your browser. The lab does not send mail or access a Microsoft tenant.

Where 0xSENTRY fits

Microsoft protects the mailbox

Microsoft 365 and Defender for Office 365 offer anti-phishing controls such as spoofing and impersonation protection. Capabilities and actions depend on the license and policy. This lab starts from a delivered message and leaves the Defender verdict unknown.

Microsoft anti-phishing documentation ↗

0xSENTRY adds a second review

The worker monitors approved Exchange Online mailboxes through Graph or consumes journal copies from Exchange Server. It extracts message evidence and validates the AI’s citations before deciding whether to alert. The worker reports findings and leaves mail delivery and quarantine to existing controls.

The SOC gets actionable evidence

The alert carries severity, evidence IDs and a correlation key. The body stays out of the SIEM payload. Failed cloud exports are retried, and the on-premises worker can write alerts to a local collector without Graph or Azure.

The context-only case illustrates the effect of sending redacted body excerpts. The connected lab enables excerpts for synthetic mail. The on-premises profile inspects the body locally and sends signal IDs to Trace.