Skip to content
Connection Guide

Connect Mimecast Awareness Training Without Breaking the Audit Trail

Use this guide to connect Mimecast Awareness Training 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
CategorySecurity Awareness
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 Mimecast Awareness Training and make sure the first collection lands cleanly.

  1. 1
    Create a dedicated Mimecast API 2.0 application with the documented `Awareness Training | Dashboard | Read` permission baseline.
  2. 2
    Store base_url, client_id, and client_secret securely and validate campaigns plus company-summary endpoints before enabling scheduled sync.
  3. 3
    Use repeated full-snapshot pulls for the reviewed report routes and do not invent cursor or delta behavior absent from the published examples.
  4. 4
    Keep governed write actions and unrelated Mimecast products out of scope for this baseline.

Credentials and Secrets

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

client_idclient_secret

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.