Skip to content

editorial: draft: update threat model to reflect source level changes #1500

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
TomHennen merged 1 commit into from
Oct 27, 2025
Merged

editorial: draft: update threat model to reflect source level changes #1500

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/spec/draft/threats.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -191,7 +191,7 @@ does enforce any controls. They then update the `release_1.2` tag to point to
Source Control System does not allow protected tags to be updated.

</details>
<details><summary>Skip required checks<span>(Source L2+)</span></summary>
<details><summary>Skip required checks<span>(Source L3+)</span></summary>

*Threat:* Code is submitted without following the producers documented
development process, introducing unintended behavior.
Expand Down Expand Up @@ -305,8 +305,8 @@ stamping."
discoverability of a change.

*Mitigation:* The Source Control System only attributes changes to authenticated
identities and, at Source L3+, records contemporaneous evidence of changes in
signed source provenance attestations.
identities and records contemporaneous evidence of changes in signed source
provenance attestations.

*Example:* Adversary 'X' creates a commit with unauthenticated metadata claiming
it was authored by 'Y'. Solution: The Source Control System records the identity
Expand Down