hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Larry McCay (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-6134) Transparent data at rest encryption
Date Wed, 18 Jun 2014 22:32:29 GMT

    [ https://issues.apache.org/jira/browse/HDFS-6134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14036560#comment-14036560

Larry McCay commented on HDFS-6134:

[~tucu00] - I realize that it is the first usecase - that doesn't make it the only one that
we have in mind or in the works. The fact that you have run into an issue with the EZ key
granularity while using the CTR mode is a problem with the usecase design not necessarily
with the abstraction of key providers. The question is whether wrapped keys will be required
by other usecases where either the key usage pattern or the encryption modes in use may not
require them. 

Currently, the KeyProvider API doesn't do any encryption itself - I just want to make sure
that adding the additional complexity and responsibility to this interface is really necessary.

Additional questions:

* how does the keyprovider know what EZ key to use - is it the key that is referenced by the
* how do we key HDFS clients from asking for the EZ key - if it is stored by the passed in
** will this require special access control protection for EZ keys?
* would the unique DEK be stored in the provider as well or only in the extended attributes
of the file?
** if stored in the provider what is the keyVersionName for it?

> Transparent data at rest encryption
> -----------------------------------
>                 Key: HDFS-6134
>                 URL: https://issues.apache.org/jira/browse/HDFS-6134
>             Project: Hadoop HDFS
>          Issue Type: New Feature
>          Components: security
>    Affects Versions: 2.3.0
>            Reporter: Alejandro Abdelnur
>            Assignee: Alejandro Abdelnur
>         Attachments: HDFSDataAtRestEncryption.pdf
> Because of privacy and security regulations, for many industries, sensitive data at rest
must be in encrypted form. For example: the health­care industry (HIPAA regulations), the
card payment industry (PCI DSS regulations) or the US government (FISMA regulations).
> This JIRA aims to provide a mechanism to encrypt HDFS data at rest that can be used transparently
by any application accessing HDFS via Hadoop Filesystem Java API, Hadoop libhdfs C library,
> The resulting implementation should be able to be used in compliance with different regulation

This message was sent by Atlassian JIRA

View raw message