Integrations / Drata

Drata

Drata compliance automation for controls, evidence, tests, personnel, vendors, risks, and audit workflows.

OAuth 2.0

Indexes

Actions

Events

What Telara does

Capability matrix

Indexes Yes Tracks spend No Discovers shadow AI No Runs actions Yes Real-time events Yes

Before you connect

Prerequisites

A Drata workspace you can administer.

Admin, or a custom role that can create API tokens / approve connected apps.

Vendor setup

Get the credential

Prefer Connect

Settings → Integrations → Drata. Telara sends you to Drata. Approve access. You do not register a Drata OAuth app.

Token fallback

If the hosted button is unavailable, in Drata open Settings → API (or Account settings → Developer). Create an API token named for Telara. Copy it immediately. Paste it in Telara, and include the Drata URL if the form asks (us vs eu).

In Telara

Connect in Telara

OAuth 2.0

Drata OAuth client credentials.

In Telara, open Settings → Integrations, choose this connector, and click Connect. Telara sends you to the vendor to approve access, then returns you here. You do not create an OAuth app or paste a client secret.

Fields Telara asks for

Base Url

API key

Drata bearer token.

In Telara, open Settings → Integrations, choose this connector, and paste the key into the fields Telara shows.

Fields Telara asks for

API token

Knowledge

What gets indexed

Resource	Coverage
Compliance control	Partial — not every record the vendor holds is synced

Sync

Freshness & sync

Resource	Lag	Deletions
Compliance control	Up to 1 day	Removed records disappear on the next full sync

Data handling

Permissions & data handling

Telara has not published a permission list for this connector yet. Treat the vendor consent screen as the source of truth until this page lists scopes.

Excluded from semantic search: Compliance control.

After connect

Verify it worked

After you save, Telara runs a read-only check against the account. The integration shows as connected when that check succeeds.

Honesty

Known limitations

Sandbox and production workspaces are different. Connecting one does not cover the other.

A token from a viewer-only user cannot read the monitors Telara lists.