Github is compomised accepted
THREAT50
· Accepted: The team has decided to live with this risk.
· Defined in catalog.py:893
- Risk
- High impact × Low likelihood = 6 medium
- After mitigations
- High impact × Low likelihood = 6 medium (unchanged)
A resource adversary could compromise GitHub and modify SecureDrop source code and introduce vulnerabilities
Threat actors: Nation State / Law Enforcement
Mitigations
| Mitigation | Status |
|---|---|
| All SecureDrop and tor releases (Release file and tag) signed with airgapped key MITIG46 | implemented |
| Airgapped signing for release tags, public and controlled branches for development/release MITIG77 | implemented |
| 2FA required for SD maintainer GitHub accounts MITIG176 | implemented |
| All code is reviewed prior to merge MITIG47 | implemented |
| SecureDrop code is open source MITIG177 | implemented |
Residual risk
Remaining risk is accepted.
Where it applies
Applies to 1 component in 1 scenario.
Supply chain and dependencies · SecureDrop source repository
Notes
In scope: No. Existing mitigations: FPF Github org makes use of all of GitHub's security features: Signed code, signed releases (we sign the release tag with the airgap key) (MITIG46), develop (trunk for us) branch protection (MITIG77), 2-factor mandated (MITIG176), code owners, code reviews (MITIG47). External contributors and users may also audit the code (MITIG177). Automated test for mitigation: No.
How this threat is matched
Listed for these components. A boundary covers every component inside it.