mail.mimecast

[ 1 Introduction ] [ 2 Valid tags and data tables ] [ 3 How is the data sent to Devo? ] [ 4 Table structure ]

Introduction

The tags beginning with mail.mimecast identify events generated by Mimecast.

Valid tags and data tables

The full tag must have 4 levels. The first two are fixed as mail.mimecast. The third level identifies the type of events sent, and the fourth level indicates the event subtype.

These are the valid tags and corresponding data tables that will receive the parsers' data:

Data tables	Tags	Data tables

Data tables	Tags	Data tables
Mimecast Secure Email Gateway Mimecast Targeted Threat Protection	`mail.mimecast.account.dashboard`	`mail.mimecast.account.dashboard`
	`mail.mimecast.archive`	`mail.mimecast.archive`
	`mail.mimecast.archive.messageview`	`mail.mimecast.archive.messageview`
	`mail.mimecast.archive.search`	`mail.mimecast.archive.search`
	`mail.mimecast.audit.events`	`mail.mimecast.audit.events`
	`mail.mimecast.message.list`	`mail.mimecast.message.list`
	`mail.mimecast.message.summary`	`mail.mimecast.message.summary`
	`mail.mimecast.siem`	`mail.mimecast.siem`
	`mail.mimecast.siem.attachment_v2`	`mail.mimecast.siem.attachment_v2`
	`mail.mimecast.siem.av`	`mail.mimecast.siem.av`
	`mail.mimecast.siem.av_v2`	`mail.mimecast.siem.av_v2`
	`mail.mimecast.siem.delivery`	`mail.mimecast.siem.delivery`
	`mail.mimecast.siem.delivery_v2`	`mail.mimecast.siem.delivery_v2`
	`mail.mimecast.siem.iep`	`mail.mimecast.siem.iep`
	`mail.mimecast.siem.iep_v2`	`mail.mimecast.siem.iep_v2`
	`mail.mimecast.siem.impersonation_v2`	`mail.mimecast.siem.impersonation_v2`
	`mail.mimecast.siem.jrnl`	`mail.mimecast.siem.jrnl`
	`mail.mimecast.siem.jrnl_v2`	`mail.mimecast.siem.jrnl_v2`
	`mail.mimecast.siem.process`	`mail.mimecast.siem.process`
	`mail.mimecast.siem.process_v2`	`mail.mimecast.siem.process_v2`
	`mail.mimecast.siem.receipt`	`mail.mimecast.siem.receipt`
	`mail.mimecast.siem.receipt_v2`	`mail.mimecast.siem.receipt_v2`
	`mail.mimecast.siem.spameventthread`	`mail.mimecast.siem.spameventthread`
	`mail.mimecast.siem.spam_v2`	`mail.mimecast.siem.spam_v2`
	`mail.mimecast.siem.ttp`	`mail.mimecast.siem.ttp`
	`mail.mimecast.siem.url_v2`	`mail.mimecast.siem.url_v2`
	`mail.mimecast.threat.feed`	`mail.mimecast.threat.feed`
	`mail.mimecast.ttp`	`mail.mimecast.ttp`
	`mail.mimecast.ttp.attachment`	`mail.mimecast.ttp.attachment`
	`mail.mimecast.ttp.attachment_protect`	`mail.mimecast.ttp.attachment_protect`
	`mail.mimecast.ttp.impersonation`	`mail.mimecast.ttp.impersonation`
	`mail.mimecast.ttp.impersonation`	`mail.mimecast.ttp.impersonation`
	`mail.mimecast.ttp.url`	`mail.mimecast.ttp.url`

How is the data sent to Devo?

Events may be sent directly to Devo using the Mimecast API or using our Devo relay.

Table structure

These are the fields displayed in these tables: