Vendor Risk Review with Claude Code: Sandbox Policy
A production playbook for vendor risk review in cross-industry operations using Claude Code: sandbox policy, run-scoped inputs, logs, typed results, and artifacts.
Audience: Procurement and security teams
The problem
Procurement and security teams need vendor risk review to run repeatedly against vendor docs, SOC reports, DPAs, and questionnaire answers. In cross-industry operations, the pain is not one good answer; it is repeatability, auditability, exception handling, and evidence that survives handoff.
Implementation path
Run vendor risk review in an ephemeral sandbox, keep provider credentials in the broker, expose narrow tools, and store logs outside the workspace for review.
Tradeoffs and failure modes
A narrower runtime blocks ambient machine behavior, but it gives security reviewers a concrete boundary. For vendor risk review, the practical test is whether a second run can be debugged, retried, and consumed by a product without reading the raw agent transcript.
Runtime boundary
filesystem: /skill and /skill/.argo/inputs only
network: deny by default
artifacts: /skill/output/artifacts
logs: retained outside sandbox
provider: Claude Code
Run this on Argo