Security and privacy

Security posture in one paragraph

DeploySutra treats every manifest, annotation and plan as hostile text. It has no way to execute them, no network access, no subprocess in the analysis code, and no credentials to steal. Its main risks are therefore information leakage into reports, parser abuse, misleading output and tool-scope escape through the optional servers. Each has a control and a test.

Threats, controls and evidence

ThreatControlEvidence
Code execution through YAML (anchors, tags, templates, merge keys)Strict subset; unsupported syntax is an error18 parser rejection tests; 15 hostile inputs in every audit
Prototype pollution via keys__proto__, constructor, prototype rejected; maps use null prototypesparser tests
Resource exhaustion1 MiB, 200 documents, 400-level nesting, seeded 400-input mutation fuzzaudit "hostile input" section
Path traversal and symlinksRegular files only, symlinked parents refused; MCP accepts only relative paths inside one rootcore, integration and MCP tests
Secret disclosure in reportsInline secret-like env values flagged without echoing; Secret data, password-named keys and plan state redacted or discardedcanary test in the audit
Plan state leakageOnly types and action counts kept; addresses, values, providers dropped; discarded sections namedtofu tests
Report injection (HTML/Markdown)HTML escaping; Markdown neutralises `, backticks, newlines, <`; control characters strippedreporting tests
False assuranceTwo-state gate; declarations never verified; NOT_RUN listedaudit "gate safety"
TamperingCanonical SHA-256 seal; edit, extension and removal detectedintegrity tests
Local API abuseLoopback only, 20+ char token, constant-time compare, GET only, no-storeserver tests
Prompt injection via manifestsSkills state manifests are data; tools take no free-form commandsskill guardrails, MCP schema
Supply chainZero dependencies; secret scan and npm pack smoke test in CICI, audit

Privacy

Nothing leaves your machine. There is no telemetry, update check, analytics or account. Reports contain names of resources, namespaces, files and images, so share them as you would an infrastructure diff. Plan JSON can hold cleartext secrets: keep it out of Git and delete it after use.

Secure usage checklist

  1. Run on a copy of exported files, not on a machine holding production kubeconfigs you do not need.
  2. Never commit plan JSON.
  3. Use --profile production for production reviews.
  4. Treat verify as tamper evidence, not authentication.
  5. Do not expose serve beyond loopback; it is a demo service.
  6. Report vulnerabilities through a private GitHub security advisory.

Known limits

The mutation fuzz is part of this repository, not an independent campaign. Static rules cannot see admission mutation or network policy. HTML reports are static documents, not a hardened public site. Windows symlink checks rely on CI where symlinks can be created; some developer machines skip them and the test log says so.