cisco/duo

VendorCisco Systems, Inc.
AuthorCrowdStrike
Version2.0.0
Minimum LogScale Version1.142.0

Duo (MFA) Multi-Factor Authentication correlates endpoint data and MFA data to spot anomalous user behavior so that you can quarantine potential compromised accounts or internal threats.

This package supports the following log types:

The parser normalizes data to a common schema based on CrowdStrike Parsing Standard (CPS) 1.0. 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.

Breaking Changes

This update includes parser changes, which means that data ingested after upgrade will not be backwards compatible with logs ingested with the previous version.

Updating to version 1.0.0 or newer will therefore result in issues with existing queries in for example dashboards or alerts created prior to this version.

See CrowdStrike Parsing Standard (CPS) 1.0 for more details on the new parser schema.

Follow the CPS Migration to update your queries to use the fields and tags that are available in data parsed with version 1.0.0.

Installing the Package in LogScale

Find the repository where you want to send the 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 (i.e. cisco/duo).

  3. In the right panel, click + Add Token to create a new token. Give the token an appropriate name and assign the parser.

    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

To get logs from Duo MFA into LogScale, you can use the Duo Log Sync which allows you to pull logs for adminaction, auth, telephony, activity endpoints and next send them into LogScale via the Log Collector.

First, in order to ingest data from the Duo Admin API you must follow the steps from Duo documentation to generate the integration key, secret key and API hostname. Those values will be required in next steps when configuring the Duo Log Sync

Follow the installation steps for the Duo Log Sync. Make sure to add the Duo keys as well as the Log Collector details into the config.yml.

Example Configurations:

yaml
version: "1.0.0"
     
     dls_settings:
     log_filepath: "/tmp/duologsync.log"
     log_format: "JSON"
     
     api:
     offset: 180
     timeout: 120
     
     checkpointing:
     enabled: True
     directory: "/tmp"
     
     #this is an example IP of the LogScale Collector 
     servers:
     - id: "logcollector_ciscoduo"
     hostname: "127.0.0.1"
     port: 1514
     protocol: "TCP"
     
     # The following keys are generated in the DUO Admin API console
     account:
     ikey: "admin-api-ikey"
     skey: "admin-api-skey"
     hostname: "host.name.com"
     
     # Here we are matching Duo MFA logs to LogScale
     endpoint_server_mappings:
     - endpoints:
     ["trustmonitor", "adminaction", "activity", "auth", "telephony"]
     server: "logcollector_ciscoduo"
     
     is_msp: false

Example LogScale Collector Configuration to send logs to LogScale, see the LogScale Collector Documentation for more information Sources & Examples

yaml
sources:
  # Collect cisco duo logs.
  ciscoduo:
    type: syslog
    mode: tcp
    port: 1514
    supportsOctetCounting: false
    strict: false
    sink: logscale_ciscoduo
sinks:
  logscale_ciscoduo:
    type: logscale
    # Replace with your ingest token for admin action logs
    token: XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
    # Replace with the "Ingest URL" on the FLC download page. It must include the "https://" at the beginning.
    url: https://XXX.YYY.ZZZ

Verify Data is Arriving in LogScale

Once you have completed the above steps the data should be arriving in your LogScale repository.

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

logscale
#Vendor = "cisco" 
        |#event.module="duo"

Package Contents Explained

This package parses incoming data, and normalizing the data as part of that parsing. The parser normalizes the data to CrowdStrike Parsing Standard (CPS) 1.0 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.