GPU acceleration & the security model

GPU acceleration for the detection engine - opt-in, by design.

The poison0 agent's detection engine runs CPU-only by default: a minimal, locked-down trusted computing base. GPU acceleration is an optional speed choice you turn on deliberately. Here is exactly what it changes, and how we keep the GPU path safe.

CPU-only is the defaultGPU is a separate, opt-in buildNetwork stays denied on both paths
GPU acceleration

Opt-in, separately hardened.

The detection engine runs CPU-only by default, the smallest and most auditable setup; GPU acceleration is a separate build you switch on deliberately for more speed.

  1. Separate binary.

    The GPU path ships as its own build; the CPU-only install is untouched.

  2. More code to trust.

    It adds the graphics driver and compute runtime to the trusted path, and VRAM is less tightly bounded.

  3. Network stays denied.

    On every platform the engine has no network access at the OS level, re-validated under the GPU stack before shipping.

    The engine sandbox

  4. Windows trade-off.

    To reach the GPU the engine leaves the AppContainer and drops the integrity lowering; restricted token, job object and network block still apply.

  5. No silent switch.

    The engine is signed and hash-pinned, and GPU mode needs an explicit, verified opt-in.

Availability

Where hardened GPU support is landing.

We ship GPU support platform by platform, only once its network isolation is re-validated under the GPU stack.

PlatformStatus
macOS (Apple Silicon, Metal)Shipping Same kernel-enforced isolation as the CPU path.
Linux (Vulkan)Shipping Same kernel-enforced isolation as the CPU path. Warm analysis 698 ms.
Windows (Vulkan)Shipping, with a stated trade-off Warm analysis 224 ms against 7,454 ms on the CPU. The GPU start leaves the AppContainer and drops the integrity lowering; restricted token, job object and the App-ID network block still apply. See the sandbox article.
CPU-only remains the default and stays available everywhere. On Windows, weigh the speed against the two isolation layers the GPU path gives up.

Read the docs

Run the secure default in under a minute.

Install the daemon and it runs CPU-only out of the box. Opt into GPU acceleration later, deliberately, when it ships for your platform.

Get the daemon