Skip to content
Open
Changes from all commits
Commits
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
2 changes: 1 addition & 1 deletion musings/workload-identity.md
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,7 @@ The workload identity problem space can be defined by the following set of key s
10. A workload's identity should coexist in a predictable manner with regular datacenter maintenance operations such as workload migration
* Operations that would change the workload identity (e.g., by modifying one of its claims) should require redeployment where the old workload is torn down and the new one stood up in its place with a new workload identity
* Operations that would preserve the workload identity, such as migration within the datacenter between equivalent hardware instances, should have no impact on the identity of the workload
11. Claims contained in workload credentials must be structured in such a way that the corresponding Relying party policies stay extra flexible over time
11. Claims contained in workload credentials must be structured in such a way that the corresponding Relying party policies stay extra stable over time
* In particular this means that frequently changing values such as workload binary measurements should not be present in the issued credentials.

So what does all that mean to Confidential Computing style Remote Attestation?
Expand Down