Skip to content
Connection Guide

Connect Duo MFA Without Breaking the Audit Trail

Use this guide to connect Duo MFA or confirm the export-based path that fits your environment. Aurora keeps source, timestamps, ownership, and collection history attached so the first run becomes reusable proof instead of one-off setup work.

Connector Summary
Connection typeDirect connection
CategoryIdentity
Checklist4 steps
Want help with rollout?
We'll confirm what can be automated, what stays export-based, and how to keep the first evidence record clean.

First-Run Checklist

Use this sequence to connect Duo MFA and make sure the first collection lands cleanly.

  1. 1
    Create a dedicated Duo Admin API application for Aurora.
  2. 2
    Grant only the read permissions required for users, policies, settings, and logs.
  3. 3
    Enter api_hostname and integration_key and store secret_key securely.
  4. 4
    Validate baseline access before enabling incremental sync.

Credentials and Secrets

The keys, secrets, or tokens Aurora uses to authenticate and collect proof.

secret_key

Recommended Access

Aurora only asks for the minimum read access needed for collection and checks.

Access requirements depend on the collection mode and scope you choose.