Cisco ISE Identity Service Engine (Preview)

Cisco Identity Services Engine (ISE) is a security policy management and control platform. It facilitates the creation and enforcement of security and access policies across an enterprise network, helping to ensure that only authorized users and devices can access network resources.

It offers a range of features including authentication, authorization, and accounting (AAA), as well as device profiling, guest management, and posture assessment, among others.

Integrating Cisco ISE with LogScale can enhance the visibility and control over the security policies and activities within your network.

This package provides a parser for Cisco Identity Service Engine (ISE) events. It normalizes data to a common schema based on an OpenTelemetry standard. This schema allows you to search the data without knowing Cisco ISE's data specifically. It also enables you to combine the data more easily with other data sources which conform to the same schema.

Note: The initial release of this package focuses exclusively on IPv4 addresses and it parsers following ISE syslogs:

The full list can be found here. Parser should work for the other streams from that list as they follow the same log format however it was not tested.

The parser normalizes data to a common schema based on an OpenTelemetry standard. This schema allows you to search the data without knowing the data specifically, and just knowing the common schema instead. It also allows you to combine the data more easily with other data sources which conform to the same schema.

Preview Status

Note that this package is considered a PREVIEW. This means we are seeking feedback on the package, and may make breaking changes to the parser in the future. It means also it may not include all documentation which usually we publish for packages.

Given the preview status of this package there are some limitations to what the parser is able to do. Please check out the package on Marketplace to see the most recent list of limitations.

Installing the Package in LogScale

Find the repository where you want to send the Cisco ISE Identity Service Engine (Preview) events, or Creating a Repository or View.

  1. Navigate to your repository in the LogScale interface, click Settings and then Packages on the left.

  2. Click Marketplace and install the LogScale package for Cisco ISE Identity Service Engine (Preview) (i.e. cisco/ise).

  3. In the right panel, click + Add Token to create a new token. Give the token an appropriate name (e.g. the name of the Event Hub it will collect logs from), and leave the parser unassigned, you can assign the parser to the LogScale Collector Configuration as described in the documentation Sources & Examples.

    Before leaving this page, view the ingest token and copy it to your clipboard — to save it temporarily elsewhere.

    Now that you have a repository set up in LogScale along with an ingest token you're ready to send logs to LogScale.

Configurations and Sending the Logs to LogScale

First you need to configure Cisco ISE to send logs to the remote syslog server.

Sign in to Cisco ISE Portal and configure the Remote Syslog Collection Locations . Go to AdministrationSystemLoggingRemote Logging Targets and add remote server by providing below details:

  • Unique name for the remote target system

  • Description of your target system

  • IP Address of the remote syslog server

  • Insert 514 or use the port value that you configured for your remote syslog server

  • From the Facility Code list, select the syslog facility to use for logging events (for example LOCAL6)

  • For the Target Type select TCP Syslog

  • Set the maximum length to 8192 characters

Selecting TCP Syslog and 8192 as the Maximum Message Length will help you avoid issues with field mappings.

Next, configure the Falcon LogScale Collector to ship the logs from your syslog server into LogScale. Follow LogScale Collector Installing the LogScale Collector and Configuring LogScale Collector. LogScale Collector documentation also provides an example of how you can configure your syslog datasource, see Sources & Examples.

Verify Data is Arriving in LogScale

Once you have completed the above steps the Cisco ISE Identity Service Engine (Preview) data should be arriving in your LogScale repository.

You can verify this by doing a simple search for the events:

#Vendor = "cisco" 
| Product="ise"

Package Contents Explained

This package contains the following parser:

  • cisco-ise-syslog - a parser for Cisco ISE logs in the syslog format. More about log format can be found in Cisco documentation.

This package parses incoming data, and normalizing the data as part of that parsing. The parser normalizes the data to a subset of this schema based on OpenTelemetry standards, while still preserving the original data.

If you want to search using the original field names and values, you can access those in the fields whose names are prefixed with the word Vendor. Fields which are not prefixed with Vendor are standard fields which are either based on the schema (e.g. source.ip) or on LogScale conventions (e.g. @rawstring).

The fields which the parser currently maps the data to, are chosen based on what seems the most relevant, and will potentially be expanded in the future. But the parser won't necessarily normalize every field that has potential to be normalized.

Event Categorisation

As part of the schema, events are categorized by fields:

  • event.category

  • event.type

  • event.kind

event.kind can be searched using Field Filters fields, but event.category and event.type are arrays, so need to be searched using the following syntax:

array:contains("event.category[]", value="network")

For example, the following will find events where some event.type[n] field contains the value network, regardless of what n is.

Note that not all events will be categorized to this level of detail.

Normalized Fields

Here are some of the normalized fields which are being set by this parser:

  • source.* (e.g. source.ip , source.port )

  • destination.* (e.g. destination.ip , destination.port )

  • client.* (e.g. , client.ip , client.port )

  • user.* (e.g. , user.full_name )

  • related (e.g. related.ip , )

Next steps and use cases

You can get actionable insights from your Cisco Identity Service Engine data by hunting for suspicious activity in LogScale using the search UI, dashboards or alerts.