GRC connector for Splunk: index retention, RBAC, audit coverage, search ACLs, and auth posture to v1 finding contract

version
0.1.0
GitHub stars
436

Install

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

Splunk Inspector Expert

Use this skill when reviewing splunk-inspector output or planning Splunk logging and access-control remediation.

Output Shape

Findings are written to:

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

Resource types:

  • splunk_deployment
  • splunk_index
  • splunk_role

Control Focus

  • LOG-05: log retention
  • LOG-08: audit event coverage
  • IAC-07: role and saved-search access control
  • IAC-04: SSO / authentication method visibility

Review Guidance

  • Treat missing API permissions as coverage gaps, not passes.
  • Confirm retention expectations with the user's regulatory and incident-response needs before accepting short retention.
  • Broad capabilities such as admin_all_objects, edit_roles, and indexes_edit require owner review.
  • Local authentication may be valid for break-glass accounts, but should be documented and monitored.

Remediation Patterns

  • Increase retention on regulated or security-relevant indexes.
  • Preserve _audit data and export it where long-term retention is required.
  • Restrict broad role capabilities and review inherited roles.
  • Limit saved-search sharing and write access.
  • Prefer SAML/LDAP/SSO-backed authentication for normal users.

Commands 3

/splunk-inspector:collect

Collect Splunk security posture and write Finding documents to:

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

The collector appends a run manifest to:

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

Coverage

  • Index retention
  • RBAC roles and broad admin capabilities
  • Audit-source coverage
  • Saved-search ACL sharing
  • User authentication method visibility

Unavailable API surfaces are emitted as inconclusive evaluations rather than silently passing.

Options

  • --output=summary|json|silent controls stdout. Default: summary.
  • --quiet suppresses progress logs on stderr.
  • --min-retention-days=<n> minimum acceptable retention for indexes. Default: 30.

/splunk-inspector:setup

Configure splunk-inspector for a Splunk management API endpoint.

plugins/connectors/splunk-inspector/scripts/setup.sh --base-url=https://splunk.example.com:8089 --token=<token>

The setup command validates /services/server/info and writes:

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

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

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

Auth

Prefer Splunk bearer tokens. Basic auth is supported for local/admin workflows.

Options:

  • --base-url=<url> Splunk management API base URL, usually port 8089.
  • --token=<token> or SPLUNK_TOKEN.
  • --username=<user> --password=<password> or SPLUNK_USERNAME / SPLUNK_PASSWORD.
  • --insecure allows self-signed certificates by setting NODE_TLS_REJECT_UNAUTHORIZED=0.

Next

/splunk-inspector:collect
/splunk-inspector:status

/splunk-inspector:status

Show Splunk API reachability, auth validity, and latest cache freshness.

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

A cache older than seven days is reported as stale.

Sponsors

Details

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

More from GRCEngClub/claude-grc-engineering

All 70