
wiz-inspector
GRC connector for Wiz CNAPP: configuration findings, issues, vulnerabilities, and cloud inventory to v1 finding contract
- version
- 0.1.0
- GitHub stars
- 436
Install
/plugin install wiz-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
Wiz Inspector Expert
Use wiz-inspector when Wiz CNAPP is the source of cloud posture, vulnerability, toxic-combination, or inventory evidence.
Inputs:
WIZ_CLIENT_IDWIZ_CLIENT_SECRETWIZ_API_URL, for examplehttps://api.<region>.app.wiz.io/graphql- optional
WIZ_AUTH_URL, defaulting tohttps://auth.app.wiz.io/oauth/token - optional
WIZ_PROJECT_IDto constrain collection to a Wiz project - required read-only scopes:
read:projects,read:issues,read:vulnerabilities,read:inventory
Run /wiz-inspector:setup, then /wiz-inspector:collect. Findings are emitted using schemas/finding.schema.json and can feed GRC Engineering gap assessments, OSCAL exports, workpaper generation, and remediation workflows.
The collector handles cursor pagination, project scoping, Wiz severity/status normalization, and partial results. If a GraphQL resource query fails, it emits an inconclusive Finding for that endpoint and continues collecting the remaining resource types.
Commands 3
/wiz-inspector:collect
Query Wiz GraphQL resources and write Finding documents to:
~/.cache/claude-grc/findings/wiz-inspector/<run_id>.json
Coverage includes configuration findings, Wiz issues, vulnerabilities, and cloud resource inventory.
The collector uses cursor pagination for each Wiz GraphQL resource, preserves project/cloud account/region metadata, and emits partial inconclusive Findings when one query fails but other resource types can still be collected.
plugins/connectors/wiz-inspector/scripts/collect.js --project-id="<project-id>" --output=json
For fixture-backed validation, set WIZ_FIXTURE_DIR or pass --fixture-dir=<path> to read redacted Wiz GraphQL response samples instead of calling the live API.
/wiz-inspector:setup
Configure Wiz GraphQL API credentials for local evidence collection.
export WIZ_CLIENT_ID="..."
export WIZ_CLIENT_SECRET="..."
export WIZ_API_URL="https://api.<region>.app.wiz.io/graphql"
plugins/connectors/wiz-inspector/scripts/setup.sh \
--api-url="$WIZ_API_URL" \
--project-id="<optional-project-id>"
Required Wiz service-account scopes for the MVP collector:
read:projectsread:issuesread:vulnerabilitiesread:inventory
Optional flags:
--auth-url=...for non-standard or GovCloud tenants.--client-id-env=...and--client-secret-env=...when credentials use non-default env var names.--project-id=...to constrain collection to one Wiz project.--limit=...to set the GraphQL page size.
The setup check validates the credentials but persists only config and env-var names, not the client secret.
/wiz-inspector:status
Check whether Wiz credentials are configured and whether recent cached findings exist.
plugins/connectors/wiz-inspector/scripts/status.sh
Sponsors
Details
- Marketplace
- GRCEngClub/claude-grc-engineering
- Source
- plugins/connectors/wiz-inspector
- Category
- Community
More from GRCEngClub/claude-grc-engineering
All 70- 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
- cyber-essentials-plusv0.1.0
- datadog-inspectorv0.1.0
- dorav0.1.0
- drata-inspectorv0.1.0
- essential8v0.1.0
- eu-nis2v0.1.0
- fedramp-20xv0.1.0
- fedramp-rev5v0.1.0
- fedramp-sspv0.1.0
- gcp-docsv0.1.0
- gcp-inspectorv0.1.0
- gcp-secret-metadatav0.1.0
- gdprv0.1.0