Drata
Reads Drata controls, policies and vendors to refresh pass/fail on the CIS program safeguards you map to Drata controls, sync the Drata vendor directory into the Draxis vendor book, and drive eight control-readiness, policy-currency and vendor-assessment KRIs. Read-only.
At a glance
| Vendor | Drata |
|---|---|
| Source type | grc |
| Vendor ID (slug) | drata |
| Base URL | https://public-api.drata.com (US, pre-filled). EU tenants use https://public-api.eu.drata.com, APAC tenants https://public-api.apac.drata.com. Draxis appends the /public/v2 path itself. |
| Auth method | api-key, Authorization: Bearer <drata-api-key> |
| Schedule default | daily |
| Availability | New in 2026.10. |
Required scopes & roles
Draxis authenticates with a Drata API key sent as a Bearer token against Drata’s v2 public API. Create the key with Custom access and enable only these four read scopes:
Workspaces: List Workspaces, finds your primary workspace (controls are workspace-scoped). BacksGET /public/v2/workspaces.Controls: List Controls, readiness flags and failing-test ids per control. BacksGET /public/v2/workspaces/{workspaceId}/controls.Policies: List Policies, policy status and renewal dates. BacksGET /public/v2/policies.Vendors: List Vendors, the vendor directory with risk levels and security reviews. BacksGET /public/v2/vendors. Requires a Drata TPRM plan.
Do not choose All read and write; the connector has no write code path. All read also works, but it grants every current and future read scope (personnel, assets, evidence) that Draxis never uses, so prefer Custom.
Policies and Vendors are optional. If the key lacks either scope (HTTP 403), or your Drata plan doesn’t include TPRM (HTTP 402), the run skips that section, records why in run history, and still refreshes controls.
Setup steps
- Open API key settings. In Drata, select your account in the bottom-left navigation, then Settings → API Keys → Create API Key.
- Name the key
draxis-readonly(or similar) so it is recognizable in Drata’s audit trail. The name can’t be changed once the key is active. - Set an expiration. Keep the 12-month default (or Custom) and schedule a rotation. Avoid Never.
- Restrict source IPs (optional). If your Draxis deployment egresses from fixed IPs, list them under Allowed IP Addresses. Left empty, the key accepts traffic from any source.
- Choose Custom access and enable exactly these scopes, leaving every Create / Update / Delete scope unchecked:
Workspaces: List Workspaces # GET /public/v2/workspaces Controls: List Controls # GET /public/v2/workspaces/{workspaceId}/controls Policies: List Policies # GET /public/v2/policies (optional, policy KRI) Vendors: List Vendors # GET /public/v2/vendors (optional, TPRM plan) - Save and copy the key. Drata shows the full key only once. Paste it into the Draxis API Key / Token field in the next section; Draxis encrypts it before storage.
- Non-primary workspace (optional). Draxis reads your primary Drata workspace. To read a different one, set
workspace_idin the integration’s extra config (see Extra config below).
Wire it into Draxis
- Open Settings → Integrations in your tenant.
- Click Add integration and pick grc as the source type.
- Pick Drata from the vendor dropdown. Draxis auto-fills the known-fixed values.
- Supply the credentials from the previous section and, if the base URL is per-tenant, your vendor URL (
https://public-api.eu.drata.com (EU) or https://public-api.apac.drata.com (APAC)). - Click Test. A green result means Draxis reached the vendor and the credentials authenticated.
- Under KRIs to import, tick the KRIs you want Draxis to manage for this integration. All are checked by default; uncheck any you don’t need. The selected KRI rows are created on save with the connector’s default thresholds (tunable later in the KRIs tab). Unchecking an already-imported KRI deletes it when you save, re-check to recreate with defaults.
- Save. The connector is now scheduled (
dailyby default) and will run on the next tick. To run immediately, click Run now.
KRIs produced
| Slug | Meaning | Derivation | Catalog signal |
|---|---|---|---|
drata_control_readiness_rate |
% of enabled Drata controls currently marked Ready, the audit-readiness headline | From GET /workspaces/{id}/controls?isEnabled=true&isArchived=false&expand[]=flags: round(count(flags.isReady) / count(controls) * 100, 1). Not written when the workspace has no enabled controls. |
— (Drata diagnostic) |
drata_controls_not_ready |
Enabled Drata controls that are not Ready, each an open framework control gap | count(controls where !flags.isReady), same fetch. |
evidences FRAMEWORK_CONTROL_GAP_COUNT |
drata_controls_failing_tests |
Enabled controls with at least one failing automated monitoring test | count(controls where testIds.failing is non-empty), same fetch with expand[]=testIds. |
— (Drata diagnostic) |
drata_policy_review_currency_rate |
% of published policies inside their review cycle | From GET /policies?statuses[]=ACTIVE&statuses[]=OUTDATED: round(count(status == ACTIVE && renewalDate >= today) / count(policies) * 100, 1). A policy with no renewal date counts as out of cycle. |
POLICY_REVIEW_CURRENCY_RATE → GV.PO-02 (canonical) |
drata_vendor_tiering_completeness |
% of in-book vendors with an assigned criticality | From GET /vendors: tiered = critical flag, an inherent risk level, or a scored impactLevel. Value = round(tiered / in_book * 100, 1). |
VENDOR_TIERING_COMPLETENESS → GV.SC-04 (canonical) |
drata_critical_vendor_assessment_rate |
% of tier-1 vendors whose latest security review is completed and approved | count(tier1 where latest SECURITY review status == COMPLETED && decision in [APPROVED, APPROVED_WITH_CONDITIONS]) / count(tier1) * 100. Not written when there are no tier-1 vendors. |
CRITICAL_VENDOR_SECURITY_ASSESSMENT_COMPLETION → GV.SC-06 (canonical) |
drata_critical_vendor_review_12m_rate |
% of tier-1 vendors reviewed in the last 12 months | count(tier1 where a COMPLETED security review was last updated, or a SOC report review dated, within 365 days) / count(tier1) * 100. |
THIRD_PARTY_VENDOR_SECURITY_REVIEW_COMPLETION → GV.SC-07 (canonical) |
drata_vendor_reviews_overdue |
In-book vendors whose scheduled review renewal date has passed | count(in_book where renewalScheduleType != NONE && renewalDate < today). |
— (Drata diagnostic) |
Definitions. In-book vendor: not archived, and status is not PROSPECTIVE, REJECTED, ARCHIVED or OFFBOARDED. Tier-1 vendor: Drata’s critical flag is set; otherwise an inherent risk level named like Critical or Tier 1; otherwise impactLevel == CRITICAL.
Each row is a slug the connector writes to. Draxis creates the matching kri rows automatically when you check them in the KRIs to import section of the integration form. Rows marked (canonical) feed a tool-independent catalog measurement mapped to the NIST CSF 2.0 subcategory shown — Draxis scores one shared measurement per signal, so swapping vendors later preserves the metric’s history and CSF posture contribution. Unmarked rows are vendor-specific diagnostics that evidence the listed catalog signals. Thresholds are seeded defaults; edit them freely in the KRIs tab afterwards.
How control mapping works
Program safeguards in the Draxis CIS Controls v8 catalog (for example CIS-14.1 “Establish and Maintain a Security Awareness Program”) can’t be measured from telemetry; they need an attestation system such as Drata. Map each one to the Drata control that attests to it: open the Risk Register, click Map program safeguards, choose drata as the vendor and enter the Drata control’s numeric id or its code (for example DCF-15; codes are matched case-insensitively).
Every run reads all enabled controls in the workspace once and writes a status for each mapped safeguard: pass when the Drata control is Ready, otherwise fail. A safeguard reads as covered when any of its mappings passes within the last 90 days, and covered safeguards drop off the recommended-controls list.
Vendor-book sync and extra config
With sync_vendors on (the default), every run imports the Drata vendor directory into the Draxis vendor book. Rows are matched on the Drata vendor id first and on name second, so re-runs don’t create duplicates and vendors you previously pushed by name are adopted. Only the fields Drata supplies are written; anything you edited in Draxis that Drata doesn’t carry is left alone. Prospective and rejected vendors are skipped. Archived and offboarded vendors only update vendors Draxis already holds, so their lifecycle change carries over without importing vendors you no longer use.
| Drata field | Draxis vendor field |
|---|---|
id | external reference (source drata) |
critical, inherentRiskLevel, impactLevel | criticality tier 1–4 (critical flag → 1; level named Critical / High / Moderate / Low or Tier 1–4; impact CRITICAL → 1, MAJOR → 2, MODERATE → 3, MINOR / INSIGNIFICANT → 4) |
residualRiskLevel, else risk | risk band (low / moderate / high / critical) |
status | status: ACTIVE, APPROVED → active; UNDER_REVIEW, FLAGGED → under review; ON_HOLD → suspended; ARCHIVED, OFFBOARDED → offboarded |
| latest security review | review status (decision when completed, otherwise progress) |
isSubProcessor | sub-processor flag |
dataAccessedOrProcessedList, hasPii | data types (PII, PHI, PCI, Financial, …) |
renewalDate | next assessment date |
| latest completed review or SOC report review date | last assessment date |
url, category, servicesProvided, contactAtVendor, contactsEmail | website, category, services description, primary contact |
The integration’s extra config is JSON, created as {"sync_vendors": true}. Set "sync_vendors": false to keep the vendor KRIs but stop writing to the vendor book, and add "workspace_id": <id> to read a workspace other than your primary one. The integration form doesn’t show extra config yet, so change it through the Draxis REST API (PUT /api/kri-sources/:id with extraConfigJson) or ask Draxis support; later saves from the form keep the value.
Vendor quirks
- API v2, cursor pagination. Draxis requests 500 rows per page and follows
pagination.cursor, capped at 40 pages (20,000 rows) per collection; a capped run logs a warning. A typical run makes 5 to 10 requests, well inside Drata’s 500 requests/minute per-IP limit. - Region is the base URL. Drata hosts US, EU and APAC tenants on separate API hosts. A key from one region returns 401 against another, so if Test fails with 401, check the host first.
- Readiness is Drata’s own
isReadyflag. Draxis doesn’t recompute it from tests, evidence or policies. Disabled and archived controls are excluded, and a mapped control that is disabled, archived or deleted reads asfail. - Security reviews carry no completion date. Drata’s vendor API exposes
requestedAtandupdatedAton security reviews but not a completed-at timestamp, so the 12-month KRI uses a completed review’s last update as its completion date. Editing an old completed review can therefore make it count as recent. - No AI-powered vendor flag. Drata’s vendor object has no AI field; if you track AI vendors in a Drata custom field, Draxis doesn’t read it yet.
- Plan-gated vendors.
/vendorsneeds a Drata TPRM plan. Without one Drata answers HTTP 402, and Draxis skips the vendor KRIs and the vendor-book sync for that run instead of failing it.
Troubleshooting
- HTTP 401 on test, regenerate the credential at the vendor and confirm the required scopes above.
- HTTP 403, the credential is valid but lacks a listed scope. Re-issue with the full set.
- HTTP 429, the connector backs off automatically. If you see repeated 429s in run history, reduce schedule frequency.
- rowsSkipped > 0 and rowsWritten = 0, your tenant hasn’t imported any KRIs for this integration yet. Open the integration in Settings → Integrations, tick the KRIs under KRIs to import, and save.
- Still stuck? Open a support ticket with the run ID (from Run history) and we’ll dig in.