From dev-return-19950-archive-asf-public=cust-asf.ponee.io@ranger.apache.org Mon Nov 12 03:44:05 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 7C6A7180645 for ; Mon, 12 Nov 2018 03:44:04 +0100 (CET) Received: (qmail 82056 invoked by uid 500); 12 Nov 2018 02:44:03 -0000 Mailing-List: contact dev-help@ranger.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ranger.apache.org Delivered-To: mailing list dev@ranger.apache.org Received: (qmail 82045 invoked by uid 99); 12 Nov 2018 02:44:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Nov 2018 02:44:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 00692181289 for ; Mon, 12 Nov 2018 02:44:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -110.301 X-Spam-Level: X-Spam-Status: No, score=-110.301 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id ARI8BFCHOSXO for ; Mon, 12 Nov 2018 02:44:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 4C98861911 for ; Mon, 12 Nov 2018 02:44:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 8B23EE0F39 for ; Mon, 12 Nov 2018 02:44:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 1AB09266F5 for ; Mon, 12 Nov 2018 02:44:00 +0000 (UTC) Date: Mon, 12 Nov 2018 02:44:00 +0000 (UTC) From: "Don Bosco Durai (JIRA)" To: dev@ranger.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (RANGER-2232) Security Zones feature in Apache Ranger MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/RANGER-2232?page=3Dcom.atlassia= n.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D166= 83145#comment-16683145 ]=20 Don Bosco Durai commented on RANGER-2232: ----------------------------------------- [~abhayk] This is a very good feature and you have articulated it very well= in the document. +1 from my side. I do have a suggestion, while we are implementing this feature, let's not m= ake it very much tied to resource policies. We should be able to use securi= ty zones for other purposes also. E.g. In the future, we should be able to = implement other features like https://issues.apache.org/jira/browse/RANGER-= 693 using security zones. > Security Zones feature in Apache Ranger > --------------------------------------- > > Key: RANGER-2232 > URL: https://issues.apache.org/jira/browse/RANGER-2232 > Project: Ranger > Issue Type: New Feature > Components: admin > Reporter: Madhan Neethiraj > Assignee: Abhay Kulkarni > Priority: Major > Attachments: Apache Ranger - Security Zones.pdf > > > This is to introduce a new abstraction in Apache Ranger that would allow = carving/bucketing of resources in a service into multiple zones, for better= administration of security policies. This would enable multiple administra= tors to setup security policies for a service =E2=80=93 based on the zones = to which they have been granted administration rights.=C2=A0 > For example, let us consider 2 security zones =E2=80=98finance=E2=80=99 a= nd =E2=80=98sales=E2=80=99: > - Security zone =E2=80=98finance=E2=80=99 includes all contents in Hive = database named =E2=80=98finance=E2=80=99=C2=A0 > - Security zone =E2=80=98sales=E2=80=99 includes all contents in =E2=80= =98sales=E2=80=99 database=C2=A0 > - Set of users and groups are designated as administrators each zone=C2= =A0 > - Users are allowed to setup policies only in zones in which they are ad= ministrators=C2=A0 > - Policies defined in a zone are applicable only for resources of the zo= ne > - A zone can be extended to include resource from multiple services like= HDFS, Hive, HBase, Kafka, .., allowing administrators of a zone to setup p= olicies for resources owned by their organization across multiple services. > - Audit logs will include name of the zone in=C2=A0which the accessed re= source resides. Only users having appropriate permissions on the security z= one can view its audit logs. > Attached document=C2=A0has more details on various aspects of Security Zo= nes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)