mail.abnormalsecurity
Introduction
The tags beginning with mail.abnormalsecurity
identify events generated by Abnormal Security.
Valid tags and data tables
The full tag must have 3 levels. The first two are fixed as mail.abnormalsecurity
. The third level identifies the type of events sent.
These are the valid tags and corresponding data tables that will receive the parsers' data:
Product / Service | Tags | Data tables |
---|---|---|
Abnormal Security |
|
|
|
|
For more information, read more About Devo tags.
Table structure
These are the fields displayed in these tables:
mail.abnormalsecurity.cases
Field | Type | Extra fields |
---|---|---|
eventdate |
|
|
hostname |
|
|
caseId |
|
|
severity |
|
|
affectedEmployee |
|
|
firstObserved |
|
|
threatIds |
|
|
analysis |
|
|
case_status |
|
|
remediation_status |
|
|
hostchain |
| ✓ |
tag |
| ✓ |
rawMessage |
| ✓ |
mail.abnormalsecurity.threats
Field | Type | Field transformation | Source field name | Extra fields |
---|---|---|---|---|
eventdate |
|
|
|
|
hostname |
|
|
|
|
threatId |
|
|
|
|
abxMessageId |
|
|
|
|
abxPortalUrl |
|
|
|
|
subject |
|
|
|
|
fromName |
|
|
|
|
fromAddress |
|
|
|
|
toAddresses |
|
|
|
|
recipientAddress |
|
|
|
|
receivedTime |
|
|
|
|
sentTime |
|
|
|
|
internetMessageId |
|
|
|
|
autoRemediated |
|
|
|
|
postRemediated |
|
|
|
|
attackType |
|
|
|
|
attackStrategy |
|
|
|
|
attachmentCount |
|
|
|
|
attackedParty |
|
|
|
|
returnPath |
|
|
|
|
replyToEmails_str |
| join(replyToEmails, ',') | replyToEmails |
|
ccEmails_str |
| join(ccEmails, ',') | ccEmails |
|
senderIpAddress |
|
|
|
|
impersonatedParty |
|
|
|
|
attackVector |
|
|
|
|
attachmentNames_str |
| join(attachmentNames, ',') | attachmentNames |
|
urls_str |
| urls |
| |
urlCount |
|
|
|
|
summaryInsights_str |
| summaryInsights |
| |
remediationTimestamp |
|
|
|
|
isRead |
|
|
|
|
remediationStatus |
|
|
|
|
senderDomain |
|
|
|
|
hostchain |
|
|
| ✓ |
tag |
|
|
| ✓ |
rawMessage |
|
|
| ✓ |