Skip to content
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.

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

Add page for Storj-managed vs. user-managed encryption #404

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
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
Original file line number Diff line number Diff line change
@@ -0,0 +1,38 @@
---
title: Storj Managed vs. User Managed Encryption
docId: aitie6rohXai9uuv
metadata:
title: Encryption passphrase management comparison
description:
Overview of the supported methods for managing an encryption passphrase
in a Storj project, and their advantages/disadvantages.
---

When creating a new Storj project, users are able to select between "Storj Managed Encryption" and "Self Managed Encryption". Each has its own benefits and tradeoffs, and once an option is selected, it cannot be changed for that project.

This page is intended to explain the difference between the two options, so that users can be better informed about which project encryption option is better suited to their use-case.

## Overivew

**Storj Managed Encryption** is best suited to:
* users who want a streamlined web browser experience, similar to other cloud storage providers
* users who want to collaborate with others on the same project

**Storj Managed Encryption** is best suited to:
* users who want complete ownership of their data encryption keys
* users who have more advanced/specialized encryption use-cases

## Storj Managed Encryption

* Encrypts data using a passphrase stored (encrypted) in the satellite's database.
* Users are not prompted for passphrases in the browser.
* Applies to entire projects, allowing seamless access for all project members.
* No path encryption; files listed in lexicographical order.

## User Managed Encryption

* Encrypts data using a user-provided passphrase, not stored in the satellite's database.
* Users must remember and share the passphrase; prompts appear in the browser for certain actions.
* Path encryption is enabled by default; extra steps needed to list files lexicographically.
* Allows multiple passphrases within a project/bucket, though not recommended.

Loading