A common security data model for email delivery and inspection events
Email remains one of the most common entry points for security threats. Yet email products often describe the same activity with different table names, fields, and values. This makes it harder to build detections and investigations that work consistently across data sources.
The Microsoft Sentinel Advanced Security Information Model, or ASIM, EmailEvent schema is now available. It provides a common structure for email delivery and inspection events, helping customers and partners create security content that works across supported email data sources.
A consistent view of email security activity
EmailEvent standardizes the information analysts need to understand what happened to an email and why. It covers:
- Email delivery and inspection events
- Sender, source, and recipient information
- Message subject, size, direction, and delivery location
- URLs and file attachments
- SPF, DKIM, and DMARC authentication results
- Delivery actions such as delivered, blocked, quarantined, or deleted
- Threat, risk, confidence, tactic, technique, and remediation details
Instead of learning a different data model for every product, analysts can query the normalized EmailEvent fields. Parser developers map each source's native data to the same schema.
How it works
Consider an email that contains a suspicious attachment. The email security product records the sender, recipients, attachment, authentication results, inspection verdict, and final action. A connector collects that event. A parser or Data Collection Rule maps the source fields to EmailEvent. Microsoft Sentinel can then query the normalized record using the same field names used for other supported email sources.
This common structure separates security content from the details of a specific product. When another source adds an EmailEvent parser, existing source-independent queries and detections can work with that source without being rewritten around its native field names.
Why it matters
- Simpler analytics: Write queries against one consistent set of email fields.
- Broader coverage: Apply source-independent security content across normalized email sources.
- Faster investigations: Compare delivery, authentication, attachment, URL, and threat details without translating different data models.
- Easier integration: Give connector and parser developers a defined contract for bringing new email telemetry into ASIM.
EmailEvent does not replace the rich native data produced by email security products. It provides a consistent security layer that makes that data easier to use together.
Build on EmailEvent
The EmailEvent release includes the schema definition, source-independent parser framework, filtering parser, deployment templates, and validation support in the Azure-Sentinel repository. The schema version is 1.0.0.
Customers can use normalized EmailEvent data to develop hunting queries, analytics rules, workbooks, and investigation experiences. Partners and community contributors can create source-specific parsers that map their email data to the schema.
Get started
Normalization Email Schema MS Learn
Learn about normalization and ASIM
Explore the EmailEvent implementation in Azure-Sentinel
Thank you to the ASIM engineering and partner teams who contributed to the schema, deployment path, validation, and release.
Microsoft Sentinel is an industry-leading SIEM & AI-first platform powering agentic defense across the entire security ecosystem.