Compromise wheel/package build machines mitigated

THREATQW34 · Mitigated: Controls in place bring the risk down to an acceptable level. · Defined in catalog.py:3498

Risk
High impact × Low likelihood = 6 medium
After mitigations
High impact × Low likelihood = 6 medium (unchanged)

How statuses and scores work

Should an adversary compromise a machine on which SecureDrop Workstation packages, including its kernel, or Python wheels are built, they may be able to introduce malicious code into an update to the SecureDrop Workstation.

Mitigations

No mitigations in place.

Residual risk

Some wheels are not reproducible, same with kernels and templates.

Where it applies

Applies to 1 component in 1 scenario.

Supply chain and dependencies · SecureDrop release & package build

Notes

Existing mitigations: Builds are independently validated by multiple developers. Release files containing hashes (MD5, SHA1, SHA256, SHA512) of Package file and package hashes are signed with an airgapped GPG key. Deb packages are reproducible. Build logs are available in build-logs github repo.

How this threat is matched

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