Supply Chain Attacks FAQ

Releases that flow through ATR with proper settings mitigate the following Supply Chain attack scenarios:

1. MFA signin prevents password theft attacks
2. Trusted Voting prevents unauthorised publication of a release
3. Prevent tampered artifacts (we ensure there's a signature for every artifact and we provide it alongside the artifact in the catalog. automated verification as a possible future enhancement), release not matching what was voted on (since the whole release flows through ATR, you have that guarantee)
4. Hidden or malicious archive content (since we validate archives and prevent things like abs paths, traversal, etc)
5. Dependency issues - we don't explicitly prevent these, but we provide the tools to do so by analysing and exposing any SBOMs uploaded, and in making those available in the catalog we help downstream consumers to avoid such attacks
6. Addition of files to source archives that weren't in the repository root, through our GitHub source comparison check
7. Various attacks prevented by OIDC in Trusted Publishing from GitHub, especially use of exfiltrated long term credentials
8. Cannot maliciously remove a key revocation from a block in a KEYS file if managed by ATR, since ATR key packets are additive only