Skip to content

Commit 7d6f165

Browse files
committed
docs: clarify persistent storage rollback limits
1 parent 9836fb3 commit 7d6f165

1 file changed

Lines changed: 2 additions & 0 deletions

File tree

docs/security/security-model.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -24,6 +24,8 @@ dstack protects the execution environment, not your application code. Bugs in yo
2424

2525
Infrastructure operators can still deny service. They can shut down your workload, throttle resources, or block network access. If availability matters, plan for redundancy across providers.
2626

27+
**Persistent-storage freshness, integrity, and availability.** Disk encryption protects the confidentiality of data at rest. The default ZFS storage filesystem also provides integrity checking; switching the storage filesystem to ext4 may forgo strong integrity protection. Neither filesystem proves that an attached disk represents the latest application state. An infrastructure operator can withhold, delete, replace, or restore an earlier valid encrypted disk image. Applications that require rollback-resistant state must anchor a monotonic version or state commitment in an external trusted service, ledger, or equivalent freshness mechanism.
28+
2729
## Security Guarantees
2830

2931
### Confidentiality

0 commit comments

Comments
 (0)