Skip to content
Connection Guide

Connect LogicGate Risk Cloud Without Breaking the Audit Trail

Use this guide to connect LogicGate Risk Cloud 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
CategoryGrc
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 LogicGate Risk Cloud and make sure the first collection lands cleanly.

  1. 1
    Enable the Risk Cloud API Access Add-On Feature for the tenant before onboarding Aurora.
  2. 2
    Generate a dedicated integration account access key and secret key and store them securely as client_id and client_secret.
  3. 3
    Grant only the Build Access and record-read permissions required for the applications and workflows Aurora should inventory.
  4. 4
    Configure the tenant base URL and, if desired, narrow the scoped record workflows or attachment value IDs in connection config.

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.