Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Custom Log Ingestion

 

Custom Log Ingestion Overview

Custom log ingestion was introduced in Juniper Advanced Threat Prevention software release version 5.0.4.

The custom log ingestion feature lets you create your own log parsers on the JATP appliance using sample logs you provide. This way, if you want to use logs from a vendor not supported by existing JATP log parsers, you can do so. By mapping fields in your sample logs to JATP event fields, you build your own custom parser, indicating which types of events will generate an incident. You can also view statistics on incoming logs and delete collected logs.

Configure the Log Parser

Use the following procedure to create your own custom log parser.

  1. Navigate to the JATP Central Manager Web UI Config>Environmental Settings>Custom External Event Collectors configuration page and click Create.
  2. In the Create New Source page, enter the following information:
    • Name—Create a unique, descriptive name for the log.

    • Description—Enter a description of the log file. (This field is optional.)

    • Type—Select the type of log from the following choices: Firewall, Web Gateway, Endpoint AV, Endpoint Response, or IPS.

    Once the required fields are complete, click Next.

    Figure 1: Configure Custom Log Source
    Configure Custom Log Source
  3. In the Parse Log File page, do the following:
    • Upload the raw log file by browsing to it or paste it into the field provided below the Browse button.

      Note

      The log file must contain an RFC-compliant syslog header.

    • From the choices provided, tell JATP what format the log file is. You can select XML, JSON, CSV, or Other.

      Figure 2: Provide Custom Log File
      Provide Custom Log File

      XML Log

      Here is an example XML Log:

      JSON Log

      Here is an example JSON log:

      CSV format

      If your log file is in CSV format, you may provide a comma delimited list of field names in the CSV Headers field. If the CSV headers are not provided, the fields will be named as csv[N] where N is the field position.

      For CSV format, here is an example PAN log:

      Other - Grok Pattern

      If you select Other, you must supply a grok pattern for the log file. A grok pattern may consist of one or more lines. The grok pattern line beginning with "LOGPATTERN" is the pattern which will be applied to the logs. A grok pattern must include a pattern named LOGPATTERN, otherwise the parser will not have any pattern to use. For example:

      For Grok pattern, here is an example Symantec EP log:

    When you click Next, JATP will parse and validate the provided log file data.

  4. In the Field Mapping page, on the left side, you select one or more check boxes beside a field that has been parsed from your log file. On the right side, you select a pre-defined description of the field from the provided options. For example, you might map a field on the left side called “interface_ip” to a JATP field on the right side called “Endpoint IP”.

    Once your check boxes are selected, click the Map button to link the fields. The mapped fields now appear in another section of the page which lists all fields that have been mapped to each other.

    Note

    Note the following details about the Field Mapping page:

    • Use the circular arrow in the Mapped Fields section to undo a mapping.

    • Click the filter icon in the Unmapped Fields section to enter text for searching.

    • You can select multiple fields from the left side and map them to one field from the right side. When you do this, a “Sort” icon appears. Use the Sort capability to select the order in which multiple fields will be applied based on whether those fields contain a valid value or not.

    • Select the “Counter” check box to count the number of times a field appears. You can then view the results of this counter in the External Event Collector page, which you will configure once your parser is complete.

      When selecting which fields to count, it is advised that you do not select items such as IP address, as those may be ubiquitous in the log file and not scalable.

    Click Next once all fields are mapped.

    Figure 3: Map Log File Fields
    Map Log File Fields
  5. You do not have to enter any text in the Date and Time page if your log file is using a standard time as dictated by RFC 3164 or RFC 5424. Those headers are automatically parsed. If the timestamp cannot be parsed, use the Ruby strftime to provide a format string so that JATP can interpret the date and time in your log file as the event start time.

    More about date and time format:

  6. In the Log Filtering page, you can create filters to tell JATP which events are malicious and which are not as you decide what logs are to be kept and which ones can be ignored. This removes logs that are “noisy” and not of particular interest and keep logs that are related to malicious events.

    With these filters, you can select “exact match” filters or “contains” for the string you enter.

    Click the Add button and configure filtering conditions as follows:

    • Select a log file field from the pulldown list.

    • Select Matches or Contains. If you select Matches, your provided string must match the selected field exactly. If you select Contains, your provided string must appear as a substring within the selected field.

    • In the edit field, enter a string for filtering log files and click Add.

    Click OK and your condition is added to the filter. You can add multiple filters. An “or” condition is applied to the list of filters, therefore the order of filters does not matter.

    Note

    Select the check box and click the Delete button to remove a filter.

    Figure 4: Create Log Filter
    Create Log Filter
  7. In the Severity Assignment page, you assign a severity level to an event based on filtering parameters you configure.

    Click the Add button and set conditions as follows:

    • Select a Severity level. The options are: Benign, Low, Medium, High, and Critical.

    • Select a field from the pulldown list to set the severity level for that field.

    • Select Matches or Contains. If you select Matches, your provided string must match the selected field exactly. If you select Contains, your provided string must appear as a substring within the selected field.

    • In the edit field, enter a string for filtering log files and click Add.

      For example, when you are finished, you may have set the following: field “threat_name” contains “Adware” = Low severity, but set “threat_name” contains “Virus” = High severity.

    Click OK and your severity level setting is added.

    Note

    You can drag and drop severity level settings in the list view on the main page to change the order. With Severity Assignment, the order does matter. The first match is the one that assigns severity.

    Figure 5: Configure Event Severity
    Configure Event Severity
    Figure 6: Severity Assignment Main Page
    Severity Assignment Main Page
  8. Click Finish and you are presented with the results of your custom parser as they are applied to the sample logs provided. Please review this carefully to determine whether your mapping, filtering, and severity assignment are as expected.

When you are finished configuring your custom log parser, the filters you created are combined to save only the logs you indicated with a threat level setting based on the criteria you configured.

Use the Log Parser

After you configure the custom log parser, you must apply it to the JATP Event Collector.

  1. Navigate to the JATP Central Manager Web UI Config>Environmental Settings>External Event Collectors configuration page and click Add Third Party Source.
  2. Select the Source Type. You must select the same type you chose when you configured the custom log parser: Firewall, Web Gateway, Endpoint AV, or Endpoint Response.
  3. In the Vendor Type field, you should see the name of the custom log parser you created. Select it.
  4. Select Log Collector and enter the host name of the machine the custom log originates from.
  5. Configure the rest of the parameters here, including Default Severity. If the custom log parser does not match any severity you set, the default severity here will be used instead.
  6. Under Create Incident, you can choose whether the events, which pass through the custom parser filtering, will create incidents. Regardless of this setting, events will appear in the Events Timeline and will provide context for malicious events occurring on the same endpoint at approximately the same time. If the Enabled field is selected, these events will also create incidents which appear in the Incidents tab.
  7. Click Add when you are finished.
    Figure 7: Add External Event Collector
    Add External Event Collector

Custom Log Statistics

When an External Event Collector is created for a custom log, counters are displayed in the External Event Collector page for that log source. The information displayed in the counter is the number of logs collected over 5 minutes, 1 hour, 1 day, 1 week intervals, and a total count, broken down by the fields you chose when creating the custom log parser.

Logs statistic may include the following:

  • All Incoming Logs: Aggregate (lifetime), Last 5 minutes, Last 1 hour, Last 24 hours, and Last 7 days

  • All Created Events: Aggregate(lifetime), Last 5 minutes, Last 1 hour, Last 24 hours, and Last 7 days

  • Parsed field counts (user selected for counting): From incoming logs, each value that appears is displayed, along with the number of times it has occurred in aggregate (lifetime) - last week, last day, last hour, and last 5 minutes.

From the External Event Collector page, click the Counters link to view log statistics.

Figure 8: External Event Collector - Counter
 External Event Collector - Counter

Related Documentation