GRC connector for Datadog: log retention, audit logs, monitor coverage, SSO, and RBAC to v1 finding contract

version
0.1.0
GitHub stars
436

Install

/plugin install datadog-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

Datadog Inspector Expert

Use this skill when reviewing datadog-inspector output or planning Datadog control remediation.

Output Shape

Findings are written to:

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

The connector emits a datadog_organization resource with SCF evaluations for:

  • DCH-07: log retention
  • LOG-08: audit log availability
  • MON-01.2: critical monitor coverage
  • IAC-04: SSO enforcement visibility
  • IAC-07: RBAC role inventory visibility
  • GOV-03: organization/API inventory

Review Guidance

  • Treat inconclusive as a permission or plan-coverage gap, not a pass.
  • Confirm monitor coverage against the user's actual critical service inventory; the collector can only infer criticality from Datadog monitor metadata.
  • Pair API output with Datadog org settings screenshots when SSO or audit APIs are unavailable.

Remediation Patterns

  • Set log index retention according to incident-response and regulatory requirements.
  • Ensure audit events are retained and exportable to long-term evidence storage.
  • Create monitors for production services and route critical alerts to incident response.
  • Enforce SSO and review local-user exceptions.
  • Review custom roles for least privilege.

Commands 3

/datadog-inspector:collect

Collect Datadog organization posture and write Finding documents to:

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

The collector appends a run manifest to:

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

Coverage

  • Log index retention and audit log visibility
  • Monitor coverage for critical resources
  • SSO enforcement visibility
  • RBAC role inventory visibility

Unavailable API surfaces are emitted as inconclusive evaluations instead of silently passing.

Options

  • --output=summary|json|silent controls stdout. Default: summary; silent suppresses stdout summary.
  • --quiet suppresses progress logs on stderr.

/datadog-inspector:setup

Configure datadog-inspector with a Datadog API key and application key.

plugins/connectors/datadog-inspector/scripts/setup.sh --api-key=<key> --app-key=<key>

The setup command validates credentials against the Datadog API and writes:

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

Secrets are stored separately with user-only file permissions at:

~/.config/claude-grc/connectors/datadog-inspector.env

Options

  • --api-key=<key> or DD_API_KEY
  • --app-key=<key> or DD_APP_KEY
  • --site=<site> defaults to datadoghq.com

Next

/datadog-inspector:collect
/datadog-inspector:status

/datadog-inspector:status

Show whether Datadog credentials are configured, whether they validate, and whether cached findings are fresh.

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

A cache older than seven days is reported as stale.

Sponsors

Details

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

More from GRCEngClub/claude-grc-engineering

All 70