Docs / Controls / NC-OC-002
NC-OC-002

Sandbox mode appropriate for deployment context

🟠 High ⚗️ Experimental ⚗️ Experimental not scored

What this checks

Checks that sandbox mode is appropriately configured when multi-user heuristics are detected.

Why it matters

Running without sandbox in a multi-user context allows any user to execute arbitrary code on the host system through prompt injection.

How to fix it

This is an experimental informational control it does not fail automatically and does not affect your score. It fires when heuristics suggest multiple users may be accessing a single gateway.

Option A Personal assistant setup (single trusted user). If this is a personal installation with one trusted operator, this is expected. Acknowledge and silence the note:

clawvitals exclude NC-OC-002 reason "personal assistant single trusted user"

Option B Shared or multi-user setup. If multiple people genuinely share this gateway and may be mutually untrusted, harden the configuration:

1. Enable sandbox mode for all agents:

agents:
  defaults:
    sandbox:
      mode: all

2. Scope file access to the workspace only:

tools:
  fs:
    workspaceOnly: true

3. Disable runtime/exec tools unless strictly required:

tools:
  exec:
    enabled: false

Option C Fully isolated users. For genuine multi-tenant use, run separate OpenClaw instances per user (separate OS users, separate credentials, separate gateway processes). A shared gateway is not designed for hostile multi-tenant isolation.

Technical details

FieldValue
Control IDNC-OC-002
DomainOC
SeverityHigh
StatusExperimental
Data sourceopenclaw_security_audit
Source typeauthoritative
ModeMode 1 (OpenClaw native)
Introduced inLibrary v0.1.0
OWASP LLM 2025LLM06: Excessive Agency

False positive notes

Single-user personal-assistant deployments will not trigger this only multi-user heuristic scenarios.

Suppress this finding

If this finding is intentional or not applicable to your setup, you can exclude it:

clawvitals exclude NC-OC-002 reason "your reason here"

Exclusions are auditable and expire automatically. See the exclusions guide.

← NC-OC-001All controlsNC-OC-003 →