GRC connector for Slack: workspace 2FA, SSO/session, retention, app approvals, and DLP visibility to v1 finding contract

version
0.1.0
GitHub stars
436

Install

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

Slack Inspector Expert

Use this skill when reviewing output from slack-inspector or planning remediation for Slack workspace security.

Output Shape

slack-inspector writes Finding schema v1 documents to:

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

Each run emits a workspace-level slack_workspace resource with SCF evaluations for:

  • IAC-02: MFA / 2FA evidence
  • IAC-04: SSO and session-duration evidence
  • DCH-07: message and file retention visibility
  • TPM-03: app approval workflow visibility
  • DLP-01: DLP or discovery visibility
  • GOV-03: workspace metadata inventory

Coverage Limits

Slack exposes many workspace governance controls only through Enterprise Grid or admin-scoped APIs. Treat inconclusive as a coverage signal, not as a pass:

  • missing_scope, not_allowed_token_type, or not_authed: request an admin-approved token with the listed scope.
  • feature_not_enabled or enterprise_required: verify manually in Slack Enterprise Admin settings or document plan limitations.
  • channel_not_found on retention checks: configure a representative channel for retention policy sampling.

Review Guidance

  • Prefer SCF control IDs already present in the finding.
  • Do not claim Slack-wide 2FA, SSO, retention, app approvals, or DLP are compliant from a bot-token-only run.
  • For audit evidence, pair collector output with Slack admin screenshots or exported policy records when the API returns inconclusive.

Remediation Patterns

  • Require 2FA for all users, especially workspace owners and admins.
  • Enforce SSO and appropriate session duration through Enterprise settings.
  • Enable app approval workflows and periodically review approved applications.
  • Define retention rules for messages and files according to legal and compliance requirements.
  • Enable DLP or discovery integrations where regulated data may appear in Slack.

Commands 3

/slack-inspector:collect

Collect Slack workspace posture and write Finding documents to the shared cache:

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

The collector appends a run manifest to:

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

Coverage

  • Workspace authentication posture: 2FA and SSO signals
  • Session duration policy visibility
  • Message/file retention policy visibility
  • App install approval workflow visibility
  • DLP and discovery visibility

Slack exposes several of these controls only to Enterprise Grid or admin-scoped tokens. Missing privileges are emitted as inconclusive evaluations with a clear message.

Options

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

Example

node plugins/connectors/slack-inspector/scripts/collect.js --output=json

/slack-inspector:setup

Configure slack-inspector for a Slack workspace.

plugins/connectors/slack-inspector/scripts/setup.sh --token=xoxb-...

The setup command is idempotent. Re-running it validates the active token with auth.test and rewrites the same connector config at:

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

Required token

Use a Slack OAuth bot token with the least privilege scopes available for your plan. The collector can run with partial coverage and marks unavailable admin-only checks as inconclusive.

Recommended scopes:

  • team:read
  • users:read
  • admin.users.info:read
  • admin.apps:read
  • admin.conversations:read
  • discovery:read

Enterprise Grid or admin scopes may be required for 2FA, SSO, app approval, retention, and DLP checks.

Options

  • --token=<xoxb-or-xoxp-token> Slack OAuth token. If omitted, reads SLACK_TOKEN.
  • --workspace=<name> optional label stored in config.

Next

/slack-inspector:collect
/slack-inspector:status

/slack-inspector:status

Show whether slack-inspector is configured, whether the token is still valid, and the freshness of the latest cached run.

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

Output includes:

  • top-level status: ready, stale, not-configured, or credentials-expired
  • Slack team id and team name from auth.test
  • config path
  • latest cache file age and evaluation count

A cache older than seven days is reported as stale.

Sponsors

Details

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

More from GRCEngClub/claude-grc-engineering

All 70