Security

Cellix MVP preview — blast-radius reducer, not a hardened security boundary.

Supported versions

Version	Supported	Notes
0.2.x	Yes	Config v0.2, canonical `CELLIX_*` env keys.
0.1.x	Best-effort	Legacy env key names; upgrade to 0.2.x.

Type	Where to report
MXC / OS primitive	microsoft/mxc SECURITY.md
Cellix SDK	GitHub Security Advisories (preferred) or issue with `security` label
Malicious model output	Not a Cellix scope item — use IDE permissions + network controls

We aim to acknowledge reports within 5 business days and publish fixes or mitigations as semver patches.

Threat	Mitigation
Determined attacker / malicious model	Do not use Cellix as sole defense.
Kernel-level escape	MXC is public preview — upstream does not claim hardened boundaries.
Secret exfiltration	Pair with secret managers; use `CELLIX_MIRROR=minimal`.
Supply-chain in agent-generated code	Review + CI gates outside Cellix.

#	Practice
1	Scope `CELLIX_WORKSPACE` to the project — never `C:\`.
2	Run `getSupportStatus()` before accepting agent work.
3	Keep `@microsoft/mxc-sdk` pinned to versions tested with Cellix.
4	Run integration tests on Windows CI before fleet rollout.
5	Treat session logs (`.cellix/sessions/`) as sensitive — may contain command output.