Introduction

The Cisco Event Streamer (also known as eStreamer) allows you to stream Firepower System events to external client applications. You can stream host, discovery, correlation, compliance white list, intrusion, user activity, file, malware, and connection data from a Management Center and you can stream intrusion data from 7000 and 8000 series devices.

Note that eStreamer is not supported on NGIPSv, Firepower Services, Firepower Threat Defense Virtual, and Firepower Threat Defense. To stream events from these devices, you can configure eStreamer on the Management Center that the device reports to.

eStreamer uses a custom application layer protocol to communicate with connected client applications. As the purpose of eStreamer is simply to return data that the client requests, the majority of this guide describes the eStreamer formats for the requested data.

There are three major steps to creating and integrating an eStreamer client with a Firepower System:

1. Write a client application that exchanges messages with the Management Center or managed device using the eStreamer application protocol. The eStreamer SDK includes a reference client application.

2. Configure a Management Center or device to send the required type of events to your client application.

3. Connect your client application to the Management Center or device and begin exchanging data.

This guide provides the information you need to successfully create and run an eStreamer Version 6.2.2 client application.

Major Changes in eStreamer Version 6.2.2

There are no new or changed events in Version 6.2.2.

Using this Guide

At the highest level, the eStreamer service is a mechanism for streaming data from the Firepower System to a requesting client. The service can stream the following categories of data:

  • Intrusion event data and event extra data
  • Correlation (compliance) event data
  • Discovery event data
  • User event data
  • Metadata for events
  • Host information
  • Malware event data

Descriptions of the data structures returned by eStreamer make up the majority of this book. The chapters in the book are:

  • Understanding the eStreamer Application Protocol, which provides an overview of eStreamer communications, details some of the requirements for writing eStreamer client applications, and describes the four types of messages used to send commands to and receive data from the eStreamer service.
  • Understanding Intrusion and Correlation Data Structures, which documents the data formats used to return event data generated by the intrusion detection and correlation components and the data formats used to represent the intrusion and correlation events.
  • Understanding Discovery & Connection Data Structures, which documents the data formats used to return discovery, user, and connection event data.
  • Understanding Host Data Structures, which documents the data formats that eStreamer uses to return full host information data when it receives a host information request message.
  • Configuring eStreamer, which documents how to configure the eStreamer on a Management Center or managed device. The chapter also documents the eStreamer command-line switches and provides instructions for manually starting and stopping the eStreamer service and for configuring the Management Center or managed device to start eStreamer automatically.
  • Data Structure Examples, which provides examples of eStreamer message packets in binary format.
  • Understanding Legacy Data Structures, which documents the structure of legacy data structures that are no longer in use by the currently shipping product but may be used by older clients.

Prerequisites

To understand the information in this guide, you should be familiar with the features and nomenclature of the Firepower System and the function of its components in general, and with the different types of event data these components generate in particular. Definitions of unfamiliar or product-specific terms can frequently be obtained from the Firepower eStreamer Integration Guide.

Product Versions for Firepower System Releases

Version numbers are used throughout this guide to describe the data format for events generated by the Management Center and managed devices. The Firepower System Product Versions table lists versions for each product by major release.

 

Table 1-1 Firepower System Product Versions

Release
Management Center Version
Master Management Center Version
Intrusion Sensor Version
Sensor Version
Managed Device Version

IMS 3.0

Management Console 3.0

N/A

Network Sensor 3.0

N/A

N/A

IMS 3.1

Management Console 3.1

N/A

Network Sensor 3.1

RNA Sensor 1.0

N/A

IMS 3.2

Management Console 3.2

N/A

Network Sensor 3.2

RNA Sensor 2.0

N/A

3D System 4.0

Management Center 4.0

N/A

Intrusion Sensor 4.0

RNA Sensor 3.0

N/A

3D System 4.5

Management Center 4.5

N/A

Intrusion Sensor 4.5

RNA Sensor 3.5

N/A

3D System 4.6.1

Management Center 4.6.1

Master Management Center 4.6.1

N/A

N/A

4.6.1

3D System 4.7

Management Center 4.7

Master Management Center 4.7

N/A

N/A

4.7

3D System 4.8

Management Center 4.8

Master Management Center 4.8

N/A

N/A

4.8

3D System 4.8.0.2

Management Center 4.8.0.2

Master Management Center 4.8.0.2

N/A

N/A

4.8.0.2

3D System 4.9

Management Center 4.9

Master Management Center 4.9

N/A

N/A

4.9

3D System 4.9.1

Management Center 4.9.1

Master Management Center 4.9.1

N/A

N/A

4.9.1

3D System 4.10

Management Center 4.10

Master Management Center 4.10

N/A

N/A

4.10

3D System 4.10.1

Management Center 4.10.1

Master Management Center 4.10.1

N/A

N/A

4.10.1

3D System 4.10.2

Management Center 4.10.2

Master Management Center 4.10.2

N/A

N/A

4.10.2

3D System 4.10.3

Management Center 4.10.3

Master Management Center 4.10.3

N/A

N/A

4.10.3

3D System 5.0

Management Center 5.0

N/A

N/A

N/A

5.0

3D System 5.1

Management Center 5.1

N/A

N/A

N/A

5.1

3D System 5.1.1

Management Center 5.1.1

N/A

N/A

N/A

5.1.1

3D System 5.2

Management Center 5.2

N/A

N/A

N/A

5.2

3D System 5.3

Management Center 5.3

N/A

N/A

N/A

5.3

Firepower System 5.3.1

Management Center 5.3.1

N/A

N/A

N/A

5.3.1

Firepower System 5.4

Management Center 5.4

N/A

N/A

N/A

5.4

Firepower System 6.0

Management Center 6.0

N/A

N/A

N/A

6.0

Firepower System 6.1

Management Center 6.1

N/A

N/A

N/A

6.1

Firepower System 6.2

Management Center 6.2

N/A

N/A

N/A

6.2

Firepower System 6.2.1

Management Center 6.2.1

N/A

N/A

N/A

6.2.1

Firepower System 6.2.2

Management Center 6.2.2

N/A

N/A

N/A

6.2.2

Document Conventions

The eStreamer Message Data Type Conventions table lists the names used in this book to describe the various data field formats employed in eStreamer messages. Numeric constants used by the eStreamer service are typically unsigned integer values. Bit fields use low-order bits unless otherwise noted. For example, in a one-byte field containing five bits of flag data, the low-order five bits will contain the data.

 

Table 1-2 eStreamer Message Data Type Conventions

Data Type
Description

nn-bit field

Bit field of nn bits

byte

8-bit byte containing data of arbitrary format

int8

Signed 8-bit byte

uint8

Unsigned 8-bit byte

int16

Signed 16-bit integer

uint16

Unsigned 16-bit integer

int32

Signed 32-bit integer

uint32

Unsigned 32-bit integer

uint64

Unsigned 64-bit integer

string

Variable length field containing character data

[n]

Array subscript following any of the above data types to indicate n instances of the indicated data type, for example, uint8[4]

variable

Collection of various data types

BLOB

Binary object of unspecified type, typically raw data as captured from a packet

IP Addresses

The Cisco database stores IPv4 and IPv6 addresses in the same fields in a BINARY format. To get IPv6 addresses, convert to hex notation, for example: 20010db8000000000000000000004321. The database follows the RFC for storing IPv4 addresses by filling in bits 80-95 with 1’s, which yields an invalid IPv6 address. For example, the IPv4 address 10.5.15.1 would be stored as 00000000000000000000FFFF0A050F01.