From
To Finance Lab <[email protected]>
0xSENTRY TRACE / SIMULATION LAB
Follow an email from Exchange to your security team. Inspect the evidence that changes the decision and the alert your analyst actually receives.
A finance employee receives an email asking them to change a payment process. Would the request warrant a second look?
0xSENTRY executes its monitoring worker on synthetic mail. The journal parser writes alerts to a temporary JSONL file. The AI decision uses a controlled test response.
Exchange journal relay
Waiting for a message
Finance Lab inboxEmail inspection
Awaiting evidence
Body, sender and local rulesLocal JSONL export
Queue empty
Waiting for a decisionSOC action ·
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.
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 ↗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 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.