Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Thu, 12 Sep 2013 18:17:51 +0000 (UTC)
From: "Jason Brown (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12668322.1379009802194.124248.1379009871610@arcas>
In-Reply-To: <JIRA.12668322.1379009802194@arcas>
References: <JIRA.12668322.1379009802194@arcas>
Subject: [jira] [Created] (CASSANDRA-6018) Add option to encrypt commitlog
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Jason Brown created CASSANDRA-6018:
--------------------------------------

             Summary: Add option to encrypt commitlog 
                 Key: CASSANDRA-6018
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6018
             Project: Cassandra
          Issue Type: Task
          Components: Core
            Reporter: Jason Brown
            Assignee: Jason Brown
             Fix For: 1.2.10, 2.0.1


We are going to start using cassandra for a billing system, and while I can encrypt sstables at rest (via Datastax Enterprise), commit logs are more or less plain text. Thus, an attacker would be able to easily read, for example, credit card numbers in the clear if the calling app does not encrypt the data itself before sending it to cassandra.

I want to allow the option of encrypting the commit logs, most likely controlled by a property in the yaml.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira