Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.
  • Madrid
  • London
  • Kingston
  • Jakarta
  • Istanbul
  • Helsinki
  • Geneva
  • Store

Create email parsers in Security Operations

Log in to subscribe to topics and get notified when content changes.

Create email parsers in Security Operations

Email Parsing creates Security Operations records from your email for security, vulnerability, and observables, improving detection time to expedite threat response and remidiation

Before you begin

Role required: sn_sec_cmn.admin
  • Set up external detection tools to send emails to a central emai address.
  • Set the email address in Security Operations Properties. For more information, see Create Security Operations email properties.
  • Assign a user account to this email address and give that user security access controls to create and update the email event records.
  • Have a copy of the relevant email from your external detection tool in front of you.
  • Decide what type of record you want to create, a security incident, vulnerability record, task and so on. This is determines the table you select.


  1. Navigate to Security Operations > Email Parsing.
  2. Click New.
  3. Fill in the fields on the form, as appropriate.
    Note: If more than one field is specified, all fields must match the email to create a record.
    Table 1. Email parser
    Field Description
    Name The name of the email parser.
    Email is from If filled in, only emails from this address are transformed by this email parser.
    Email is to If filled in, only emails from this address are transformed by this email parser.
    Email subject contains If filled in, only emails where the subject contains this phrase are transformed by this email parser.
    Application Name of the application.
    Destination table The table where you want to create records.
    Duplication rule Governs how to handle duplicate emails for any email this transform handles. For more information, see Security Operations email duplication rules
    Order In what order to consider the transforms. The first matching email transform is used. Typically, you want to set up the most specific email parsers in the lower numbers, with some fallback. Give catchall email parsers higher Order numbers so they run if nothing else matches. Default is 100. When everything matches, the most specific email parser (matches from, to, and subject) is used.
    Active Whether this transform is active, in use, or not active. If unchecked, no emails are transformed with this code.
    Record Separator When emails handled by this email parser can create multiple records, this field contains the separator between the information for those records. See Security Operations email parsing for more information.
    Description Description of this email parser – which tool it works with, the purpose, and so on.
  4. When you have completed your entries, right-click in the form header and select Save.
    A Field Transforms tab appears. This tab shows how individual fields within the destination table are set based on the email contents.
    Email transforms form
  5. To add Field Transforms, perform these steps.
    1. In the Field Transforms tab, click New.
    2. Fill in the fields on the form, as appropriate.
    Field Select the field to fill in with this value.

    For choice fields, matches are made to existing choices using the underlying choice label or value. If no match is found, the field is set, but no new entry is added to the choice list. For more information, see Choice lists.

    For reference fields, an entry is set only when a value matching the display name of the record or valid sys_id is found. For more information, see Reference fields.

    Email transform The transform this field transform belongs to.
    Destination table Destination table of the email transform. It contains informational data from the email transform.
    Search for value Select the location in the email to search. Choices include:
    • At the start of a line in the email body
    • Anywhere in the email body
    • In the email subject line
    • Always the static value

    When you have defined a Record Separator, more options (Anywhere within the record section and At the start of a line within the record section) enable you to search only within the current section instead of in the entire email body (See Security Operations email parsing for more information.

    Information that is in a header or footer, applying to all records, is searched for in the entire email body. The information that differs between records is searched for only within the section.

    Value prefix

    The text that always precedes the value to extract.

    Active The default is checked. When checked, the field transform is activated. Uncheck this box to deactivate the field transform.
    Order The order in which the field transforms run, from lowest to highest. A field transform with an order entry of 100 is attempted first. Only if that field transform fails to find a value will a field transform with a higher order (200) on the same field run.
    End of value

    Select what indicates the end of the value. Choices include: End of line, End of email (brings in all remaining text in the email), or Until (stops when it finds the specified text).

    Value suffix

    When the End of Value is set to Until, this field specifies what text always follows the value placed within this field.

    For example, looking for a value that comes after “The affected computer is”, and before “.” will parse out “AB123” from “The demented bunny virus has been found. The affected computer is AB123. Estimated time of infection was 3:45PM” in an email.

    1. Click Submit.
      The new record is used to parse the information in the email into a new record.