VotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Closed
    • Major
    • Resolution: Won't Fix
    • None
    • None
    • Blob, cassandra
    • None

    Description

      Following JAMES-2921 Hybrid BlobStore we end up storing 'blobs' into Cassandra.

      Given a multi-tenant environment, if I run two James servers on top of the same Cassandra database, I don't want one server to be able to read the content of the other one.

      Such isolation is currently achievable by having separate keyspaces, and separate users with different right settings. However given a cassandra acls misconfiguration, such content could still be leaked from one tenant to the other one in case of James compromision.

      Encrypting blobs into cassandra, with an encryption key specific per James server can be a good second line of defense to mitigate this risk. Only metatdata would be readable, raw content (headers & body) staying encrypted.

      As such, I should be able to configure AES encryption of top of Cassandra storage (just like on top of ObjectStorage).

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            btellier Benoit Tellier
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Issue deployment