Standardization activity on how to do client-side data encryption for personal data storage is heating up in the wider standards community, led by the W3C Credentials Community group and the Decentralized Identify Foundation (DIF) (including Microsoft, Workday, Consensys, and others). This is also relevant to Solid, for use cases that have strong client-side data encryption requirements (such as storage of health records and other high-value items).
Standardization activity on how to do client-side data encryption for personal data storage is heating up in the wider standards community, led by the W3C Credentials Community group and the Decentralized Identify Foundation (DIF) (including Microsoft, Workday, Consensys, and others). This is also relevant to Solid, for use cases that have strong client-side data encryption requirements (such as storage of health records and other high-value items).
The current Linked-Data-friendly standard being incubated jointly by those groups is the Encrypted Data Vault spec (see the introductory Encrypted Data Vault requirements paper).
This is a placeholder issue to track pre-requisite specs and infrastructure to enable client-side encryption on Solid.
Pre-requisite infrastructure: