[
https://issues.apache.org/jira/browse/HDFS-6134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14103250#comment-14103250
]
Andrew Wang commented on HDFS-6134:
-----------------------------------
I've filed MAPREDUCE-6040 to address Sanjay's point about automatically using
/.reserved/raw if running distcp as root.
I also filed HADOOP-10983 to address Suresh's point about auditing FS vs. KMS
permissions, we basically just need a new KMS API to fetch the ACLs for a key.
Then such an auditing tool could be built.
Hopefully this will take care of the most pressing feedback. I would like to
backport this to branch-2 relatively soon after the trunk merge to keep the
diff down, since it is a fairly large patch. Of course, we will address the
rest of the feedback before an actual branch-2 release.
> 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: 3.0.0, 2.3.0
> Reporter: Alejandro Abdelnur
> Assignee: Charles Lamb
> Attachments: HDFS-6134.001.patch, HDFS-6134.002.patch,
> HDFS-6134_test_plan.pdf, HDFSDataatRestEncryption.pdf,
> HDFSDataatRestEncryptionProposal_obsolete.pdf,
> HDFSEncryptionConceptualDesignProposal-2014-06-20.pdf,
> fs-encryption.2014-08-18.patch, fs-encryption.2014-08-19.patch
>
>
> 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, or WebHDFS REST API.
> The resulting implementation should be able to be used in compliance with
> different regulation requirements.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
