GRC connector for Drata: wraps drata-cli workflows and normalizes compliance posture to v1 finding contract

version
0.1.0
GitHub stars
436

Install

/plugin install drata-inspector@grc-engineering-suite

Run it inside Claude Code after adding the marketplace with /plugin marketplace add GRCEngClub/claude-grc-engineering.

Contents

Discovered from source

Skills 1

Drata Inspector Expert

Use this skill when reviewing drata-inspector output or planning remediation from Drata workflow findings.

Source

drata-inspector wraps the MIT-licensed drata-cli workflow commands. It does not reimplement Drata APIs and does not require Drata MCP.

Output Shape

Findings are written to:

~/.cache/claude-grc/findings/drata-inspector/<run_id>.json

Resource types:

  • drata_tenant: summary status across controls, monitors, personnel, and integrations
  • drata_control: failing or incomplete controls from drata controls failing
  • drata_monitor: failed automated checks from drata monitors failing
  • drata_connection: disconnected, failed, or never-connected integrations
  • drata_personnel: personnel/device compliance issues
  • drata_evidence: stale or expiring evidence from drata evidence expiring

Review Guidance

  • Treat Drata-native control codes as source metadata. The connector emits SCF IDs for normalized downstream reporting.
  • Keep Drata as the evidence source of record; use these Findings for cross-framework gap analysis and engineering remediation.
  • inconclusive means a drata-cli workflow failed or permissions were insufficient.

Remediation Patterns

  • Assign owners for ownerless controls.
  • Refresh stale evidence and repair disconnected evidence sources.
  • Investigate failed monitors before assuming a control is ineffective.
  • Resolve personnel device compliance failures or document approved exceptions.
  • Reconnect Drata integrations that feed automated evidence.

Commands 3

/drata-inspector:collect

Run curated drata-cli workflows and write Finding documents to:

~/.cache/claude-grc/findings/drata-inspector/<run_id>.json

The collector appends a run manifest to:

~/.cache/claude-grc/runs.log

Workflow Source

This connector adapts drata-cli workflow commands:

  • drata summary --json --compact
  • drata controls failing --json --compact
  • drata monitors failing --json --compact
  • drata connections list --json --compact
  • drata personnel issues --json --compact
  • drata evidence expiring --json --compact

Options

  • --output=summary|json|silent controls stdout. Default: summary.
  • --quiet suppresses progress logs on stderr.
  • --limit=<n> passes a display cap through to workflow commands. Default: 50.
  • --max-pages=<n> bounds Drata API pagination. Default: 20.
  • --evidence-days=<n> marks evidence older than this as expiring/stale. Default: 60.

Notes

The connector prefers SCF IDs where there is a stable GRC meaning. Drata-native control codes are preserved in metadata and messages so downstream reviewers can trace findings back to Drata.

/drata-inspector:setup

Configure drata-inspector, a workflow wrapper over drata-cli.

plugins/connectors/drata-inspector/scripts/setup.sh

The setup command verifies that drata is available, checks read-only auth, and writes:

~/.config/claude-grc/connectors/drata-inspector.yaml

Auth

drata-inspector uses drata-cli auth directly. Configure one of:

  • drata auth login --api-key-stdin
  • DRATA_API_KEY
  • DRATA_API_KEY_CMD
  • DRATA_REGION=us|eu|apac
  • DRATA_BASE_URL

The connector runs Drata collection commands with DRATA_READ_ONLY=1.

Options

  • --region=us|eu|apac records the expected Drata region. Default: DRATA_REGION or us.
  • --command=<path> records a custom drata executable path.

Next

/drata-inspector:collect
/drata-inspector:status

/drata-inspector:status

Show drata-cli availability, auth state, and latest cache freshness.

plugins/connectors/drata-inspector/scripts/status.sh

A cache older than seven days is reported as stale.

Sponsors

Details

Marketplace
GRCEngClub/claude-grc-engineering
Source
plugins/connectors/drata-inspector
Category
Community

More from GRCEngClub/claude-grc-engineering

All 70