From issues-return-13846-archive-asf-public=cust-asf.ponee.io@sentry.apache.org Fri May 11 22:07:04 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 E51B7180647 for ; Fri, 11 May 2018 22:07:03 +0200 (CEST) Received: (qmail 99576 invoked by uid 500); 11 May 2018 20:07:03 -0000 Mailing-List: contact issues-help@sentry.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@sentry.apache.org Received: (qmail 99566 invoked by uid 99); 11 May 2018 20:07: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; Fri, 11 May 2018 20:07: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 952E71807FD for ; Fri, 11 May 2018 20:07:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -110.31 X-Spam-Level: X-Spam-Status: No, score=-110.31 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id S3GZJtQS8qpK for ; Fri, 11 May 2018 20:07:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id EE6E35F59D for ; Fri, 11 May 2018 20:07:00 +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 69A52E0F31 for ; Fri, 11 May 2018 20:07: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 2093A21298 for ; Fri, 11 May 2018 20:07:00 +0000 (UTC) Date: Fri, 11 May 2018 20:07:00 +0000 (UTC) From: "Brian Towles (JIRA)" To: issues@sentry.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (SENTRY-2225) Generic Attribute Ingestion and Default Implementation 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/SENTRY-2225?page=3Dcom.atlassia= n.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D164= 72570#comment-16472570 ]=20 Brian Towles commented on SENTRY-2225: -------------------------------------- Its not really about re-storage of attributes.=C2=A0 This is about collecti= on of attributes (not persistence in the long term) for use in other parts = of Sentry. So lets step back a bit and look at what an=C2=A0ABAC system needs, not jus= t for the column masking subsystem.=C2=A0 I think we have a bit of a discon= nect on the relation of attributes to=C2=A0things=C2=A0like access control = and=C2=A0column masking. The ability for a user to tie different sources of attributes into their ac= cess control decisions and data presentation systems is very powerful and d= esired.=C2=A0 The [Guide to Attribute Based Access Control (ABAC) Definitio= n and Considerations|https://nvlpubs.nist.gov/nistpubs/specialpublications/= nist.sp.800-162.pdf]=C2=A0talks about this and is a good reference. One of the key parts of this is that the Policy Information Point (PIP) is = about the retrieval of attributes and not the system of record for those at= tributes and the attributes themselves could be volatile and potentially ch= ange frequently.=C2=A0=C2=A0 For=C2=A0the general collection and aggregation of attributes I do not feel= that the=C2=A0permanent storage of attributes is needed or desired.=C2=A0 = What the PIP side of this becomes is a attribute collection, aggregation, a= nd distribution source but not outright persistence.=C2=A0 It collects the = attributes from multiple sources based on the plugins developed for attribu= te collection.=C2=A0 It aggregates this into a central attribute=C2=A0colle= ction=C2=A0that it is able to distribute to the bindings or Policy Decision= Points (PDP).=C2=A0 This allows the access control engine or column maskin= g decision engine to have access to the attributes where the decision is be= ing made for speed and easy lookup. The different attribute collection mechanisms would allow=C2=A0attributes t= hat have a different valid life spans to be taken into account. User or Sub= ject level attributes might have a different valid life span then HMS Objec= t data.=C2=A0 It allows for the ability to implement different collection p= atterns that may need to be put into place, push versus pull as needed by t= he system providing the attributes. Implementation of attribute collection can be done with a pluggable solutio= n using Java Service Loader SPI framework to allow for multiple attribute c= ollection sources at one time.=C2=A0 It would also provide set interfaces a= nd loading mechanism for end user custom provided attribute loading mechani= sms as well as additional attribute collection that could come from the pro= ject. Once attributes are=C2=A0ingested, column masking and other components in t= he system can make use of the attributes in order to make decisions.=C2=A0 = The aggregated set of attributes can be distributed to the server or bindin= gs, what ever is being the decision point and allow for quick local access = quickly. The way I see it the initial sources can be the HMS Table Properties I ment= ioned above as well as the Static File mechanism that could be used more fo= r development and testing. =C2=A0 > Generic Attribute Ingestion and Default Implementation > ------------------------------------------------------ > > Key: SENTRY-2225 > URL: https://issues.apache.org/jira/browse/SENTRY-2225 > Project: Sentry > Issue Type: Sub-task > Components: Core > Affects Versions: 2.1.0 > Reporter: Anthony Young-Garner > Priority: Major > Labels: ABAC > > As discussed in the=C2=A0design=C2=A0document linked on SENTRY-2140, attr= ibutes and their mapping to columns are created and stored in an external s= ystem. In order for Sentry to make masking decisions based upon these attri= butes and mappings, this information must be ingested from the external sys= tem. The scope of this Jira is to : > # implement the generic extensible framework by which different external= systems may contribute attributes (the specific details of the design are = still under discussion on the parent Jira; whether there is a full plugin m= odel implemented in Sentry or whether the ingestion process will run entire= ly external to Sentry and send the information to Sentry via Thrift API is = not yet decided). > # Implement at least one default implementation (whether this will be an= example implementation only for reference like a static text file or a ful= l-featured implementation more suitable for production use is under discuss= ion)=C2=A0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)