Skip to content
Connection Guide

Connect ThreatConnect Without Breaking the Audit Trail

Use this guide to connect ThreatConnect 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
CategorySecops
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 ThreatConnect and make sure the first collection lands cleanly.

  1. 1
    Create a dedicated API-enabled ThreatConnect user with the documented Api User system role and Read Only User organization role.
  2. 2
    Store base_url and api_token securely and validate /v3/security/owners plus /v3/cases access before enabling scheduled sync.
  3. 3
    Keep Workflow-dependent objects limited to the documented read-only Cases and Artifacts surfaces unless a tenant proves additional endpoints safely.
  4. 4
    Do not provision Exchange Admin or governed-action privileges for this baseline.

Credentials and Secrets

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

api_token

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.