
splunk-inspector
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-suiteRun it inside Claude Code after adding the marketplace with /plugin marketplace add GRCEngClub/claude-grc-engineering.
Contents
Discovered from sourceSkills 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_deploymentsplunk_indexsplunk_role
Control Focus
LOG-05: log retentionLOG-08: audit event coverageIAC-07: role and saved-search access controlIAC-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, andindexes_editrequire 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
_auditdata 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|silentcontrols stdout. Default:summary.--quietsuppresses 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 port8089.--token=<token>orSPLUNK_TOKEN.--username=<user> --password=<password>orSPLUNK_USERNAME/SPLUNK_PASSWORD.--insecureallows self-signed certificates by settingNODE_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- staterampv0.1.0
- teach-mev0.1.0
- tenable-inspectorv0.1.0
- testssl-inspectorv0.1.0
- trust-centerv0.1.0
- us-ccpav0.1.0
- us-exportv0.1.0
- us-finrav0.1.0
- us-hipaa-securityv0.1.0
- us-nerc-cipv0.1.0
- us-soxv0.1.0
- vault-kvv0.1.0
- wiz-inspectorv0.1.0
- academic-research-companionv0.1.0
- au-apra-cps-234v0.1.0
- aws-inspectorv0.1.0
- aws-secrets-inspectorv0.1.0
- azure-inspectorv0.1.0
- ch-fadpv0.1.0
- cis-controlsv0.1.0
- cmmcv0.1.0
- compliance-posture-dashboardv0.1.0
- crowdstrike-inspectorv0.1.0
- csa-ccmv0.1.0