Skip to content

Commit

Permalink
remove attacker goals from this pr
Browse files Browse the repository at this point in the history
Signed-off-by: Marina Moore <mnm678@gmail.com>
  • Loading branch information
mnm678 committed May 27, 2021
1 parent 3b36c20 commit f7340ac
Showing 1 changed file with 1 addition and 9 deletions.
10 changes: 1 addition & 9 deletions threatmodel.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,14 +6,6 @@ It is assumed that an attacker may perform one or more the following actions:
2. compromise some set of weak crypto algorithms which are supported in some legacy cases
3. compromise a repository, including gaining access to use any keys stored on the repository
4. compromise a signing key, for example due to malicious action or accidental disclosure by the key owner
5. compromise a step in the software supply chain. This can happen in many different ways, such as by gaining access to the server, compromising the software used in the step of the supply chain, passing different software to a subsequent step than what was intended, or causing an operator to make an error in a step.
5. compromise a step in the software supply chain. This can happen in many different ways, such as by gaining access to the server, compromising the software used in the step of the supply chain, passing different software to a subsequent step than what was intended, or causing an operator to make an error in a step.

While it is not always possible to protect against all scenarios, the system should to the extent possible mitigate and/or reduce the damage caused by a successful attack, detect the occurrence of an attack and notify appropriate parties, yet remain usable for parties operating the system. Furthermore, the system should recover from successful attacks in a way that presents low operational overhead and risk to users.

Attacker Goals:
1. Trying to have a party install a malicious image under the attackers control.
2. Trying to have a party install an outdated image. For example, one with known security vulnerabilities.
3. Making images unavailable for installation.
4. Preventing a party from learning about updates to currently installed images.
5. Convincing a party to download large amounts of data that interfere with the party's system.
6. Enabling future attacks of the above types to be carried out more easily. For example, by causing a party to trust the attacker's key.

0 comments on commit f7340ac

Please sign in to comment.