# Security Policy

## Supported versions

| Version | Security fixes |
|---|---|
| Latest `0.1.x` | Yes |
| Older snapshots | No |

## Reporting a vulnerability

Do not open a public issue for vulnerabilities involving credential exposure, sandbox escape, cross-tenant data access, arbitrary Host execution, or authentication bypass.

Use GitHub's **Security → Report a vulnerability** private reporting flow for this repository. Include:

- affected commit/version and DSH version;
- minimal reproduction without real secrets;
- required configuration and platform;
- expected and observed security boundary;
- impact and any known mitigation.

If private reporting is unavailable, open a minimal issue asking the maintainer to enable a private channel, without publishing exploit details.

## Security model

- The plugin runs in the DSH Host process and must be treated as trusted application code.
- Task text, source material, trajectories, deliverables, and experience entries are untrusted data for model prompts.
- C8 middleware code generated by a model is never loaded.
- C7 scripts are disabled by default and require `ctx.shell` plus `ctx.sandboxPolicy`. DSH file sandboxing does not imply network isolation.
- Experience data is partitioned by tenant/project/domain, but filesystem access control and encryption belong to the deployment.
- `harness2/event` excludes task, trajectory, and deliverable content; Run Store records contain them and may be sensitive.
- Startup URLs, cookies, credentials, `$DSH_HOME`, Session logs, Run Store and experience libraries must never be committed.

## Deployment recommendations

1. Keep `k=1`, `libraryMode=off`, and `enableScripts=false` for first deployment.
2. Use a dedicated OS account and restrict the Harness² data directory.
3. Configure hard token limits and, when prices are known, hard cost limits.
4. Apply retention and backup policies to audit and experience data.
5. Re-run native integration tests for every DSH upgrade.
6. Do not grant exact-version compatibility exemptions without reviewing API changes.