Outgoing feed - TAXII inbox feed

This article describes the specific configuration options to set up the feed.

To configure the general options for the feed, see Configure outgoing feeds general options.

Assign unique names to TAXII feeds: TAXII inbox and TAXII poll feeds in the platform, both incoming and outgoing, must have unique names.

	Specifications
Transport type	TAXII inbox
Content type	ArcSight CEF EclecticIQ Entities CSV EclecticIQ HTML Report EclecticIQ HTML Report Digest EclecticIQ JSON EclecticIQ Observables CSV PAN-OS External Dynamic List Plain text value STIX 1.2
Description	The feed publishes entities and observables in the selected content type to the TAXII inbox service configured for the feed. You can retrieve the content by accessing the TAXII inbox service endpoint for the feed configured in the platform, and by specifying: The name of the collection the outgoing feed belongs to. The name of the feed whose content you want to retrieve. Each time the outgoing feed task runs, it generates a data package containing zero or more entities and observables, depending on: The outgoing feed content update strategy. The feed data source containing data matching the feed configuration and any rule criteria that apply to the feed.

Before configuring a TAXII transport type for an incoming or an outgoing feed, make sure that the appropriate TAXII service is correctly configured in the platform system settings.

TAXII inbox and TAXII poll transport types require Cabby.
For more information, see official Cabby documentation, the Cabby public repo on GitHub, and the Cabby download page.

Configure the outgoing feed

Create or edit an outgoing feed.
From the Transport type drop-down menu, select TAXII inbox.
From the Content type drop-down menu, select the appropriate content type for the data you want to publish through the outgoing feed.
The selected content type for the feed should match the actual format of the source data you are publishing through the feed.
This can vary, depending on the dataset sources you retrieve the data for publication from.
From the Datasets drop-down menu, select one or more existing datasets to use as sources to populate the outgoing feed content.
For the feed not to be empty, at least one selected dataset should contain entities and observables in the same format as the configured content type for the feed.
From the Update strategy drop-down menu, select the preferred method to populate the outgoing feed with data before publishing it.
Update strategies help define how content is aggregated and packaged for publication when an outgoing feed task runs:
- Append: every time the outgoing feed task runs, it fetches only new, unpublished data to generate the content for publication.
  The published packages contain only new entities and observables ingested in the platform after the previous execution of the outgoing feed.
- Replace: every time the outgoing feed task runs, it fetches new and existing data to generate the content for publication.
  The published packages contain new and existing entities and observables included also in the previous execution of the outgoing feed.
- Diff : this option is available only for the EclecticIQ Entities CSV and EclecticIQ Observables CSV content types.
  Every time the outgoing feed task runs, new data is compared against existing data to identify any differences between the two datasets:
  - At entity level: any entities added to or removed from the set, if EclecticIQ Entities CSV is the designated content type for the feed.
  - At observable level: any observable added to or removed from the entities in the set, if EclecticIQ Observables CSV is the designated content type for the feed.
  Depending on the selected CSV content option, each row in the CSV output contains information about one entity being added or removed, or one observable being added or removed.
  An extra diff column is added to the output CSV to indicate if a row, and therefore either an entity or an observable, has been added to or removed from the set.
  This option enables identifying changes in a feed between two executions without downloading the whole feed every time.
  Update strategies help define how content is aggregated and packaged for publication when an outgoing feed task runs:
  
  Update strategies rely on the last_updated_at database field to identify entities whose timestamp value was updated since the previous execution of the outgoing feed.
  Entities with a more recent timestamp value compared to the previous execution of the outgoing feed are packaged and included in the published content of the outgoing feed.
  - Changes to the data section of an entity create a new version of the entity.
    They also add a new log entry to the entity history to record the changes.
  - Changes to the meta section of an entity do not create a new version of the entity.
    However, they do update the timestamp value of the last_update_at database field.
In the Inbox service URL field, enter the URL to the location of the TAXII data collections available through the TAXII inbox service.
In the Destination collection name field, enter an existing destination collection name identifying the target container for the outgoing feed data.
To store your changes, click Save; to discard them, click Cancel.

View and retrieve outgoing feed content

In the top navigation bar click Data configuration > Outgoing feeds.
In the Outgoing feeds view, click anywhere in the row corresponding to the outgoing feed whose content you want to view or retrieve.
In the selected outgoing feed detail pane, click the Created packages tab.
In the Created packages tab, under the Download column header, click the name of a package to download it, and to save it to a target location.