Guidelines for Configuring Audora Connect: Drata Integration

Questions? Contact us at support@goaudora.com

Audora Connect integrates the platform with Drata, a leading compliance automation tool. Through Audora Connect, auditors can pull controls, policies, tests, evidence requests, and evidence from a client's Drata audit into Audora's collaborative dashboard - and evidence-request comments sync both ways. The result is the same as our Vanta integration: less time bouncing between platforms, less tool training, and Audora as a single, unified workspace for your engagement.

Unlike Vanta (which uses a client ID + client secret), Drata uses a single Auditor API key that you paste into Audora.

Prerequisites for the Drata integration

1. Your firm has Drata Auditor API access.
   Connecting Audora to Drata requires an auditor-level Drata account with the Auditor API enabled (part of Drata's Audit Alliance / auditor program). If you don't see an option to generate an Auditor API key in Drata, contact your Drata relationship manager - or reach out to us at support@goaudora.com and we can help.

2. Your audit client has added your firm to each audit.
   In Drata, your client grants you access per audit by adding your firm's alias email to the audit card in Drata AuditHub (this is the equivalent of a Vanta client "authorizing" your firm). Until your firm is added to a given audit, that audit will not appear in Audora when you create an engagement, and comments won't sync for it. If you've already worked with this client in Drata, you're likely set up already - it's worth confirming before you create the engagement.

Step 1 – Generate your Drata Auditor API key

1. Log into Drata as an auditor (your AuditHub workspace).

2. Open your Auditor API / API Keys settings.

3. Click Create (or Generate key) and give it a recognizable name - we suggest something like "Audora Connect" so you'll remember what it's for.

4. Copy the key immediately. Drata shows the full key value only once, so store it somewhere safe until you've pasted it into Audora.
   
   Note: Drata Auditor API keys are valid for about 12 months. Audora will remind you (in-app, by email, and on Slack if connected) before the key is due to expire, so syncs never silently break - see "Renewing your key" below.
   Exact menu labels in Drata's AuditHub may vary slightly by account; if you can't find the Auditor API key screen, your Drata relationship manager can point you to it.

Step 2 – Connect Drata in Audora

1. Log into Audora as the Auditor App Admin.

2. From the dashboard, select Integrations on the left-hand side.

3. Open the Connections tab and find the Drata card.

4. Click Connect, then paste your Drata Auditor API key into the field. (There is just one field - no client ID, client secret, or region.)

5. Click Connect. When the credentials check out, the card turns green / Connected, and Audora kicks off an initial sync of your active engagements. You are now ready to set up your first Drata engagement.

Step 3 – Create an engagement from Drata

1. Start Create engagement and choose the From GRC option.

2. Select the Drata audit you want to import. (Only standard, supported frameworks are listed - custom-framework audits in Drata aren't importable.)

3. Audora pulls in the audit's controls, maps them to the framework criteria, creates the engagement pre-populated and linked to its Drata counterpart, and runs a sync.

4. Because Drata's readiness data isn't auto-scoped, you'll complete a quick manual System scope step; the Controls list and Pre-check card are populated from Drata automatically.
   Evidence (manual uploads, linked library evidence, Drata-generated policies, and automated monitoring evidence) syncs into each evidence request, and comments sync both ways - just like the Vanta integration.

Renewing your key

Drata keys expire (about 12 months). Before yours does, Audora will prompt you to reconnect. To renew: generate a fresh Auditor API key in Drata (Step 1), open the Drata card on the Integrations → Connections page, and paste in the new key.

Troubleshooting

• "Couldn't connect" / invalid key - the key may be mistyped, expired, or revoked. Generate a fresh key in Drata and re-enter it.

• An audit doesn't appear when creating an engagement - confirm your firm's alias has been added to that specific audit in Drata AuditHub, and that it's a supported framework (custom frameworks aren't importable).

• Comments aren't syncing - Drata only lets your firm see a request once you've been added to that audit; confirm your alias is on the audit.

Questions? Contact us at support@goaudora.com