This topic provides instructions for creating a custom feed using a .csv or STIX formatted feed data file in RSA NetWitness Suite.
You can easily create a custom feed using the Custom Feed wizard. To complete this procedure, you need a feed data file in .csvor .xml format. If you also have an associated feed definition file in .xml format, which describes the structure of the feed data file, you can use the feed definition file to create a feed. The Custom Feed wizard can create the feed based on a feed data file, or based on a feed data file and corresponding feed definition file.
After completing this procedure, you will have created a custom feed.
The feed data file (.csv or STIX (.xml)) and optionally the feed definition file (.xml) must be available on the local file system for an on-demand custom feed. For a recurring custom feed, the files must be available at a URL that is accessible to the NetWitness Suite server.
To create a custom feed:
Go to t CONFIGURE > CUSTOM FEEDS.
The Custom Feeds view is displayed.
The Setup Feed dialog is displayed.
To select the feed type, click Custom Feed and Next.
The Configure a Custom Feed wizard is displayed, with the Define Feed form open.
To define a feed based on a .csv formatted feed data file, select Default in the Feed Type field.
To define an on-demand feed task that executes once, select Adhoc in the Feed Task Type field and do one of the following:
- (Conditional) To define a feed based on a .csv formatted feed data file, type the feed Name, select a .csv content File from the local file system, and click Next.
(Conditional) To define a feed based on an XML feed file, select Advanced Options.
The Advanced Options are displayed:
- Select an XML feed file from the local file system, choose the Separator (default is comma), and specify the Comment characters used in the feed data file (default is #), and click Next.
The Select Services form is displayed. This is an example of the form for a feed based on a feed data file with no feed definition file. If you are defining a feed based on a feed definition file, the Define Columns tab is not needed.
To define a recurring feed task that executes repeatedly at specified intervals, during a specified date range.
Select Recurring in the Feed Task Type field.
The Define Feed form includes the fields for a recurring feed.
In the URL field, enter the URL where the feed data file is located, for example, http://<hostname>/<feeddatafile>.csv, and click Verify.
NetWitness Suite verifiies the location where the file is stored, so that NetWitness Suite can check for the latest file automatically before each recurrence.
(Optional) If the URL has restricted access and requires authentication using your username and password, select Authenticated.
NetWitness Suite provides your user name and password for authentication to the URL.
- If you want the NetWitness Suite server to access the Feed URL through a proxy, select Use Proxy. For more information on configuring a proxy, see the Configure Proxy for NetWitness Suite topic in the System Configuration Guide. By default, the Use Proxy checkbox is not selected.
To define the interval for recurrence, do one of the following:
- Specify the number of minutes, hours, or days between recurrences of the feed.
- Specify recurrence every week, and select the days of the week.
(Conditional) If you want to define a feed based on an XML feed file:
Type the feed Name, select Advanced Options.
The Advanced Options fields are displayed.
Select an XML feed file from the local file system, choose the Separator (default is comma), specify the Comment characters used in the feed data file (default is #) and click Next.
The Select Services form is displayed.
To identify services on which to deploy the feed, do one of the following:
- Select one or more Decoders and Log Decoders, and click Next.
Click the Groups tab and select a group. Click Next.
The Define Columns form is displayed.
To map columns in the Define Columns form:
- Define the Index type: IP, IP Range, or Non IP, and select the index column.
- (Conditional) If the index type is IP or IP Range and the IP address is in CIDR notation, select CIDR.
(Conditional) If the index type is Non IP, additional settings are displayed. Select the service type and Callback Keys, and optionally select the Truncate Domain option.
Select the language key to apply to the data in each column from the drop-down list. The meta displayed in the drop-down list is based on the meta available for the service define values. You can also add other meta based on advanced expertise.
The Review form is displayed.
Anytime before you click Finish, you can:
- Click Cancel to close the wizard without saving your feed definition.
- Click Reset to clear the data in the wizard.
- Click Next to display the next form (if not viewing the last form).
- Click Prev to display the previous form (if not viewing the first form).
- Review the feed information, and if correct, click Finish.
- Upon successful creation of the feed definition file, the Create Feed wizard closes, and the feed and corresponding token file are listed in the Feed grid and progress bar tracks completion. You can expand or collapse the entry to see how many services are included, and which services were successful.
MetaCallback Feeds using CIDR Index Range for IPv4 and IPv6
This section describes how to use CIDR index ranges for IPv4 and IPv6 in custom MetaCallback feeds. As with other custom feeds, you must create feed data file in .csv format, and a feed definition file in .xml format.
The following example shows the contents of both a .csv file and an .xml file for a MetaCallback feed using CIDR index ranges for IPv4 or IPv6.
<?xml version="1.0" encoding="UTF-8"?>
<FDF xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="feed-definitions.xsd">
<FlatFileFeed name="ip_test" path="ip_test.csv" separator="," comment="#">
<MetaCallback name="DstIP" valuetype="IPv4" apptype="0" truncdomain="false">
<LanguageKey name="alert" valuetype="Text" />
<Field index="1" type="index" range="cidr"/>
<Field index="2" type="value" key="alert" />