Lingering files in VMs (sd-proxy, sd-devices) are not deleted after use partially mitigated

THREATQW67 · Partially mitigated: Some controls are in place, but the risk is still too high. · Defined in catalog.py:3931

Risk
Medium impact × Low likelihood = 4 medium
After mitigations
Low impact × Low likelihood = 2 low

How statuses and scores work

sd-proxy temporarily stores encrypted files and messages prior to sending to sd-app, and sd-devices temporarily stores decrypted files for export. Handling scripts should delete these files, but programming or use error may result in the files remaining available

Threat actors: Any

Mitigations

No mitigations in place.

Where it applies

Applies to 2 components in 2 scenarios.

Workstation: reading submissions · sd-proxy
Workstation: export and print · sd-devices (export and print)

Notes

Existing mitigations: sd-devices and sd-proxy are both disposable VMs whose state is reset after reboot (MITIGQW18). Further mitigations: make sd-proxy a disposable VM.

How this threat is matched

Listed for these components. A boundary covers every component inside it.