Loading

Cisco Duo

<div class="condensed-table">
| | |
| --- | --- |
| Version | 2.3.1 (View all) |
| Compatible Kibana version(s) | 8.13.0 or higher |
| Supported Serverless project types
What’s this? | Security
Observability |
| Subscription level
What’s this? | Basic |
| Level of support
What’s this? | Elastic |

</div>
The Cisco Duo integration collects and parses data from the Cisco Duo Admin APIs. The Duo Admin API provides programmatic access to the administrative functionality of Duo Security’s two-factor authentication platform.

This module has been tested against Cisco Duo Core Authentication Service: D224.13 and Admin Panel: D224.18

In order to ingest data from the Cisco Duo Admin API you must:

  • Have a the Cisco Duo administrator account with Owner role Sign up
  • Sign in to Duo Admin Panel
  • Go through following tabs Application > Protect an Application > Admin API > Protect
  • Now you will find your Hostname*, Integration key and *Secret key which will be required while configuring the integration package.
  • For this integration you will require Grant read information* and *Grant read log permissions.
  • Make sure you have whitelisted your IP Address.

More details for each step can be found at First steps.

The Cisco Duo integration collects logs for the following types of events.

Cisco Duo has implemented v2 handlers for some endpoints. In these cases, the API v1 handler remains supported, but will be limited or deprecated in the future.

From data streams listed above, v2 handlers are supported for Activity, Authentication and Telephony Logs at the moment. It is recommended to migrate data streams to the v2 endpoints when they become available.

The following considerations should be taken into account when configuring the integration.

  • Interval has to be greater or equal than 1m.
  • The Duo Admin API retrieves records from the last 180 days up to as recently as two minutes before the API request. Consider this when configuring the Initial interval parameter for the v2 API endpoints, as it doesn’t support d as a suffix, its maximum value is 4320h which corresponds to that 180 days.
  • For v2 API endpoints, a new parameter limit has been added to control the number of records per response. Default value is 100 and can be incresead until 1000.
  • Larger values of interval might cause delay in data ingestion.

This is the activity dataset.

This is the admin dataset.

This is the auth dataset.

This is the offline_enrollment dataset.

This is the summary dataset.

This is the telephony dataset.

This is the telephony_v2 dataset.

This is the trust_monitor dataset.