| <?xml version="1.0" encoding="ISO-8859-1"?> | |
| <!-- | |
| Licensed to the Apache Software Foundation (ASF) under one or more | |
| contributor license agreements. See the NOTICE file distributed with | |
| this work for additional information regarding copyright ownership. | |
| The ASF licenses this file to You under the Apache License, Version 2.0 | |
| (the "License"); you may not use this file except in compliance with | |
| the License. You may obtain a copy of the License at | |
| http://www.apache.org/licenses/LICENSE-2.0 | |
| Unless required by applicable law or agreed to in writing, software | |
| distributed under the License is distributed on an "AS IS" BASIS, | |
| WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. | |
| See the License for the specific language governing permissions and | |
| limitations under the License. | |
| --> | |
| <document> | |
| <body> | |
| <section name="Apache Ranger Policy Model"> | |
| <div class="ranger-blog-post"> | |
| <div class="ranger-blog__header"> | |
| <p class="ranger-blog__back"><a href="../blogs.html">← All blogs</a></p> | |
| <p class="ranger-blog__meta">Madhan Neethiraj, Apache Ranger committer · Mar 08, 2022</p> | |
| </div> | |
| <div class="ranger-blog__body"> | |
| <h1>Introduction</h1> | |
| <p> | |
| Apache Ranger is an extensible framework that enables enterprises to adopt a consistent approach to authorize | |
| access to their resources across multiple services/applications/cloud. Apache Ranger framework also enables | |
| enterprises to collect audit logs of access to their resources, to help meet various compliance requirements. | |
| </p><p> | |
| Apache Ranger is a central part of security in many large deployments in enterprises across various domains | |
| like finance, retail, insurance, healthcare, services. Apache Ranger has out-of-the box support for a large | |
| number of popular services and many more services are supported by commercial vendors. Apache Ranger is highly | |
| optimized for performance, adds negligible overhead in authorizing access to resources. It has been very well | |
| proven in very high throughput services like Apache Kafka, Apache HBase which perform thousands of | |
| authorizations per second. | |
| </p><p> | |
| Apache Ranger provides an intuitive web user interface to manage authorization policies and audit logs for | |
| access to resources across a large number of services. Apache Ranger also provides REST, Python, Java APIs for | |
| programmatic integration with tools used by enterprises. Open framework provided by Apache Ranger enables | |
| enterprises to extend Apache Ranger authorization to their own applications and services as well. | |
| </p><p> | |
| Here are few key points that make Apache Ranger a compelling option for enterprises looking to standardize | |
| authorization of access to their resources: | |
| </p> | |
| <p class="ranger-blog__list-item">1. out-of-the-box support for more than a dozen popular services like Apache Hive, Apache HBase, Apache Kafka, Apache Solr, Elasticsearch, Apache NiFi and Presto.</p> | |
| <p class="ranger-blog__list-item">2. support for services like Amazon EMR, AWS S3, ADLS-Gen2, GCS, Snowflake, Google BigQuery, Trino, Dremio, Starburst, Apache Impala, Postgres, MS-SQL and Amazon Redshift by commercial vendors.</p> | |
| <p class="ranger-blog__list-item">3. policies for access authorization, row-filters, data masking.</p> | |
| <p class="ranger-blog__list-item">4. resource-based, classification-based policies, role-based, attribute-based policies.</p> | |
| <p class="ranger-blog__list-item">5. delegated administration, deny and exceptions in policies, custom conditions.</p> | |
| <p class="ranger-blog__list-item">6. centralized audit logs of accesses to enterprise resources across multiple services, interactive user interface to view audit logs of accesses.</p> | |
| <p class="ranger-blog__list-item">7. intuitive policy management UI.</p> | |
| <p class="ranger-blog__list-item">8. Java, Python, REST APIs for programmatic integration for policy management.</p> | |
| <p class="ranger-blog__list-item">9. open framework which enables enterprises to extend Apache Ranger authorization to their own applications and services.</p> | |
| <h2>Contents</h2> | |
| <p><a href="#s1">1. Policy Model</a></p> | |
| <p><a href="#s2">2. Attribute based access control</a></p> | |
| <p><a href="#s3">3. Resource based access control</a></p> | |
| <p><a href="#s4">4. Tag based access control</a></p> | |
| <p><a href="#s5">5. Data masking</a></p> | |
| <p><a href="#s6">6. Row-filter</a></p> | |
| <p><a href="#s7">7. Access audit logs</a></p> | |
| <p><a href="#references">References</a></p> | |
| <h1 id="s1">Policy Model</h1> | |
| <p> | |
| At the core of Apache Ranger authorization is its policy model. We will go through key aspects of the Apache | |
| Ranger policy model in this section. | |
| </p> | |
| <h2>Resources</h2> | |
| <p> | |
| A resource is a fundamental element in the Apache Ranger policy model. Apache Ranger enables policies to | |
| authorize access to resources. In this context, a resource is anything whose access needs to be authorized, | |
| like a file/path, database, table, column, topic; but can also be a service – like Apache Knox topology. | |
| Apache Ranger policy model captures details of resources of a service in a declarative way – details like | |
| hierarchy, case-sensitivity, supports row-filter/data-masking, etc. | |
| </p><p> | |
| Type of resources vary across services/applications, as seen in the table below: | |
| </p><table> | |
| <tr> | |
| <td><p><b>Service</b></p></td> | |
| <td><p><b>Resources</b></p></td> | |
| </tr> | |
| <tr> | |
| <td><p>Apache Hive</p></td> | |
| <td><p>databases, tables, columns, udfs</p></td> | |
| </tr> | |
| <tr> | |
| <td><p>Apache Kafka</p></td> | |
| <td><p>topics</p></td> | |
| </tr> | |
| <tr> | |
| <td><p>Apache Solr</p></td> | |
| <td><p>collections</p></td> | |
| </tr> | |
| <tr> | |
| <td><p>AWS S3</p></td> | |
| <td><p>buckets, objects</p></td> | |
| </tr> | |
| <tr> | |
| <td><p>ADLS-Gen2</p></td> | |
| <td><p>storage-accounts, containers, objects</p></td> | |
| </tr> | |
| <tr> | |
| <td><p>Azure PowerBI</p></td> | |
| <td><p>workspaces</p></td> | |
| </tr> | |
| <tr> | |
| <td><p>Google BigQuery</p></td> | |
| <td><p>projects, datasets, tables, columns</p></td> | |
| </tr> | |
| <tr> | |
| <td><p>Snowflake</p></td> | |
| <td><p>databases, schemas, tables, columns, warehouses</p></td> | |
| </tr> | |
| <tr> | |
| <td><p>Trino</p></td> | |
| <td><p>catalogs, schemas, tables, columns, procedures</p></td> | |
| </tr> | |
| <tr> | |
| <td><p>...</p></td> | |
| <td></td> | |
| </tr> | |
| </table> | |
| <h2>Permissions</h2> | |
| <p> | |
| A permission is another fundamental element in the Apache Ranger policy model. A permission is an action | |
| performed on a resource, like reading a file, creating a directory, querying a table, or publishing a message | |
| to a topic. Apache Ranger policy model captures details of permissions of a service in a declarative way – | |
| details like which permissions are applicable to specific resource types, implied permissions, etc. | |
| </p><p> | |
| Like resources, list of permissions varies across services/applications, as seen in the table below: | |
| </p><table> | |
| <tr> | |
| <td><p><b>Service</b></p></td> | |
| <td><p><b>Permissions</b></p></td> | |
| </tr> | |
| <tr> | |
| <td><p>Apache Hive</p></td> | |
| <td><p>create, alter, drop, select, insert, ..</p></td> | |
| </tr> | |
| <tr> | |
| <td><p>Apache Kafka</p></td> | |
| <td><p>publish, consume, create, delete, describe, configure, ..</p></td> | |
| </tr> | |
| <tr> | |
| <td><p>Apache Solr</p></td> | |
| <td><p>query, update, others, Solr admin</p></td> | |
| </tr> | |
| <tr> | |
| <td><p>AWS S3</p></td> | |
| <td><p>read, write, delete, ..</p></td> | |
| </tr> | |
| <tr> | |
| <td><p>ADLS-Gen2</p></td> | |
| <td><p>read, write, delete, ..</p></td> | |
| </tr> | |
| <tr> | |
| <td><p>Azure PowerBI</p></td> | |
| <td><p>contributor, member, admin, none</p></td> | |
| </tr> | |
| <tr> | |
| <td><p>Google BigQuery</p></td> | |
| <td><p>project-list, dataset-create, table-create, table-list, query, ..</p></td> | |
| </tr> | |
| <tr> | |
| <td><p>Snowflake</p></td> | |
| <td><p>CreateSchema, CreateTable, Select, Insert, Update, ..</p></td> | |
| </tr> | |
| <tr> | |
| <td><p>Trino</p></td> | |
| <td><p>create, alter, drop, select, insert, ..</p></td> | |
| </tr> | |
| <tr> | |
| <td><p>...</p></td> | |
| <td></td> | |
| </tr> | |
| </table> | |
| <h2>Users, Groups, Roles</h2> | |
| <p> | |
| Apache Ranger enables authorization policies to be set up to allow/deny permissions to users, groups, and | |
| roles. Users and groups are typically obtained from an enterprise directory like AD/LDAP. Apache Ranger | |
| user-sync module handles details of bringing users and groups from sources like LDAP/AD/OS, and keeping up | |
| with the changes in the sources - like addition of users and groups, addition/removal of a user from a group. | |
| </p><p> | |
| Apache Ranger user-sync supports retrieving attributes of users and groups as well. Such attributes, like | |
| dept/location/site-id, can be used in authorization policies to allow/deny access to resources, and set up | |
| row-filters that restrict users to access relevant subset of data. More on this later in this document. | |
| </p><p> | |
| In addition to users and groups, Apache Ranger supports roles to be used in authorization policies. A role in | |
| Apache Ranger is a grouping of users, groups, and other roles. Roles can be managed using Apache Ranger UI and | |
| REST APIs by authorized users. Role based authorization is widely used in enterprises and having support for | |
| roles in Apache Ranger makes it possible to use well established enterprise security practices in Apache Ranger | |
| authorization policies. | |
| </p> | |
| <h2>Delegated Admin</h2> | |
| <p> | |
| Apache Ranger enables decentralization of authorization policies management with support for delegated-admin | |
| feature. A set of users, groups and roles can be granted permission, via an Apache Ranger policy (what else!), | |
| to manage authorization policies for a subset of resources and permissions. For example, users in | |
| <samp>finance-admin</samp> group can be granted permissions to manage authorization policies for contents of | |
| Snowflake database named <samp>finance</samp>, and AWS S3 objects under <samp>s3://mybucket/dept/finance</samp>. | |
| This offers a scalable approach to manage authorization in large deployments. | |
| </p> | |
| <h2>Security Zone</h2> | |
| <p> | |
| Apache Ranger supports security zones to enable multi-tenancy within an organization where admins from | |
| different lines of businesses can manage security policies for their own resources. For example, data that | |
| belongs to the sales team can be managed by administrators of the sales team, similarly data of marketing, | |
| sales, operations teams can be managed by respective administrators. | |
| </p><p> | |
| Also, security zones can be used to isolate resources based on purpose. For example, it is common for a data | |
| lake to have distinct areas and authorization policies for test data, unprocessed/raw data, semi-processed | |
| data, and production data. Apache Ranger makes it easier to manage security policies in such deployments with | |
| use of security zones like: | |
| </p> | |
| <p class="ranger-blog__list-item">-Test zone</p> | |
| <p class="ranger-blog__list-item">-Landing zone</p> | |
| <p class="ranger-blog__list-item">-Staging zone</p> | |
| <p class="ranger-blog__list-item">-Production zone</p> | |
| <p> | |
| A security zone can contain resources from multiple services/applications, like AWS S3, ADLS-Gen2, GCS, | |
| Snowflake, Amazon Redshift, Postgres, Apache Hadoop, Apache Hive, Apache HBase, Apache Kafka. This makes it | |
| easier to set up consistent authorization policies across multiple services by a set of administrators | |
| designated for each security zone. | |
| </p> | |
| <h2>Allow, Deny, Exceptions</h2> | |
| <p> | |
| In addition to authorization policies that can grant access to resources, Apache Ranger also enables policies | |
| to be setup to: | |
| </p> | |
| <p class="ranger-blog__list-item">-deny access to users/groups/roles on resources</p> | |
| <p class="ranger-blog__list-item">-exclude a subset of users from accesses allowed/denied above</p> | |
| <p class="ranger-blog__list-item">-deny all access to specific resources other than the ones allowed in the policy</p> | |
| <p> | |
| This makes it easier to set up policies to protect sensitive resources. | |
| </p> | |
| <h2>Wildcards, macros, variables in resource names</h2> | |
| <p> | |
| Apache Ranger policies support use of wildcards, macros, and variables in resource names. This makes it | |
| possible to use small number of policies for a large number of resources, as shown below: | |
| </p><table> | |
| <tr> | |
| <td><p><b>Policy Resource</b></p></td> | |
| <td><p><b>Description</b></p></td> | |
| </tr> | |
| <tr> | |
| <td><p><samp>test_<b>*</b></samp></p></td> | |
| <td><p>matches all resources having name that start with test_</p></td> | |
| </tr> | |
| <tr> | |
| <td><p><samp>/home/<b>{USER}</b></samp></p></td> | |
| <td><p>a path under /home having name of current user</p></td> | |
| </tr> | |
| <tr> | |
| <td><p><samp>/dept/<b>${{USER.dept}}</b></samp></p></td> | |
| <td><p>a path under /dept having name of current user’s department</p></td> | |
| </tr> | |
| </table><h2>Policy validity schedule</h2> | |
| <p> | |
| Apache Ranger enables policies to be effective only for specific time schedules. This feature can be used to | |
| create policies that need to be effective at a future time, for example to allow access to revenue reports for | |
| a wider audience only after a specific time. This feature can also be used to allow temporary access to | |
| specific users/groups/roles, with a specific start and end times. | |
| </p><h1 id="s2">Attribute based access control</h1> | |
| <p> | |
| Apache Ranger enables use of user, group, resource, classification, and the environment attributes in | |
| authorization policies. ABAC makes it possible to express authorization policies without prior knowledge of | |
| specific resources, specific users – which helps avoid the need for new policies as new resources or users are | |
| introduced. | |
| </p> | |
| <br/> | |
| <p> | |
| For example: | |
| </p> | |
| <p class="ranger-blog__list-item">-allow each user to access all tables owned by them, using <b><i>{OWNER}</i></b> macro:</p> | |
| <table class="ranger-blog-table--kv"> | |
| <tr> | |
| <td><p><samp>resource</samp></p></td> | |
| <td><p>database=*, table=*</p></td> | |
| </tr> | |
| <tr> | |
| <td><p>users</p></td> | |
| <td><p><b>{OWNER}</b></p></td> | |
| </tr> | |
| <tr> | |
| <td><p>permissions</p></td> | |
| <td><p>all</p></td> | |
| </tr> | |
| </table> | |
| <p></p> | |
| <p class="ranger-blog__list-item">-allow users to access their department data in AWS S3, by using user attribute <b><i>${{USER.dept}}</i></b>:</p> | |
| <table class="ranger-blog-table--kv"> | |
| <tr> | |
| <td><p><samp>resource</samp></p></td> | |
| <td><p>bucket=mycompany, object=/data/<b><i>${{USER.dept}}</i></b>/*</p></td> | |
| </tr> | |
| <tr> | |
| <td><p>users</p></td> | |
| <td><p><b>{USER}</b></p></td> | |
| </tr> | |
| <tr> | |
| <td><p>permissions</p></td> | |
| <td><p>read,write</p></td> | |
| </tr> | |
| </table> | |
| <p></p> | |
| <p class="ranger-blog__list-item">-allow users in mktg group to access <samp>PII</samp> data of email type, by using tag attribute <b><i>TAG.piiType</i></b>:</p> | |
| <table class="ranger-blog-table--kv"> | |
| <tr> | |
| <td><p><samp>resource</samp></p></td> | |
| <td><p>tag=PII</p></td> | |
| </tr> | |
| <tr> | |
| <td><p>groups</p></td> | |
| <td><p>mktg</p></td> | |
| </tr> | |
| <tr> | |
| <td><p>condition</p></td> | |
| <td><p><b><i>TAG.piiType == 'email'</i></b></p></td> | |
| </tr> | |
| <tr> | |
| <td><p>permissions</p></td> | |
| <td><p>select</p></td> | |
| </tr> | |
| </table> | |
| <p></p> | |
| <p class="ranger-blog__list-item">-tables with <samp>SENSITIVE</samp> classification should be accessible only by users having privileges for that sensitive level</p> | |
| <table class="ranger-blog-table--kv"> | |
| <tr> | |
| <td><p><samp>resource</samp></p></td> | |
| <td><p>tag=SENSITIVE</p></td> | |
| </tr> | |
| <tr> | |
| <td><p>groups</p></td> | |
| <td><p>public</p></td> | |
| </tr> | |
| <tr> | |
| <td><p>condition</p></td> | |
| <td><p><b><i>TAG.sensitiveLevel < USER.allowedSensitiveLevel</i></b></p></td> | |
| </tr> | |
| <tr> | |
| <td><p>permissions</p></td> | |
| <td><p>select</p></td> | |
| </tr> | |
| </table> | |
| <h1 id="s3">Resource based access control</h1> | |
| <p> | |
| Apache Ranger enables setting up policies to grant or deny permissions to users/group/roles based on specific | |
| resource names, like: | |
| </p> | |
| <br/> | |
| <table class="ranger-blog-table--resource"> | |
| <tr> | |
| <td><p><b>Service</b></p></td> | |
| <td><p><b>Resource</b></p></td> | |
| <td><p><b>Permission</b></p></td> | |
| </tr> | |
| <tr> | |
| <td><p>Apache Hive</p></td> | |
| <td> | |
| <table class="ranger-blog-table--kv"> | |
| <tr> | |
| <td>database</td> | |
| <td>sales</td> | |
| </tr> | |
| <tr> | |
| <td>table</td> | |
| <td>order_data</td> | |
| </tr> | |
| <tr> | |
| <td>column</td> | |
| <td>order_amount</td> | |
| </tr> | |
| </table> | |
| </td> | |
| <td><p>select</p></td> | |
| </tr> | |
| <tr> | |
| <td><p>Apache Kafka</p></td> | |
| <td> | |
| <table class="ranger-blog-table--kv"> | |
| <tr> | |
| <td>topic</td> | |
| <td>finance</td> | |
| </tr> | |
| </table> | |
| </td> | |
| <td><p>publish, consume</p></td> | |
| </tr> | |
| <tr> | |
| <td><p>AWS S3</p></td> | |
| <td> | |
| <table class="ranger-blog-table--kv"> | |
| <tr> | |
| <td>bucket</td> | |
| <td>mycompany</td> | |
| </tr> | |
| <tr> | |
| <td>path</td> | |
| <td>/home/{USER}</td> | |
| </tr> | |
| </table> | |
| </td> | |
| <td><p>read, write, delete</p></td> | |
| </tr> | |
| <tr> | |
| <td><p>ADLS-Gen2</p></td> | |
| <td> | |
| <table class="ranger-blog-table--kv"> | |
| <tr> | |
| <td>storage-account</td> | |
| <td>mycompany</td> | |
| </tr> | |
| <tr> | |
| <td>container</td> | |
| <td>home</td> | |
| </tr> | |
| <tr> | |
| <td>path</td> | |
| <td>/{USER}</td> | |
| </tr> | |
| </table> | |
| </td> | |
| <td><p>read, write, delete</p></td> | |
| </tr> | |
| <tr> | |
| <td><p>...</p></td> | |
| <td></td> | |
| <td></td> | |
| </tr> | |
| </table> | |
| <h1 id="s4">Tag based access control</h1> | |
| <p> | |
| In addition to authorization policies on resources, Apache Ranger enables policies to be set up on | |
| classifications (tags) associated with resources. This feature enables enterprises to separate responsibility | |
| of classification of resources (PII, PCI, PHI, credit card number, etc.) from setting up access-control | |
| policies. Classifications created, by a team of data stewards and tools that scan data for sensitive | |
| information, can be leveraged to drive authorization to access the resources. | |
| </p><p> | |
| Authorization policies on the classifications themselves, instead of directly on the resources, will ensure | |
| that appropriate policies will automatically be applied as classifications are added, removed, and updated on | |
| resources. Also, a single tag-based policy (for example on PII) can be used to authorize access to resources | |
| across multiple services like AWS S3, ADLS-Gen2, Snowflake, Databricks SQL, Apache Hive, Apache HBase, Apache | |
| Kafka. This can significantly reduce the complexity in managing authorization policies. | |
| </p> | |
| <h1 id="s5">Data masking</h1> | |
| <p> | |
| Apache Ranger data-masking policies enable enterprises to allow access to sensitive data suitably masked | |
| depending on the context in which a user accesses the data. Some users will need the data without masking, | |
| while some other users can only be allowed to see partial or masked or transformed value. While authorization | |
| policies can be used to either allow or deny access to certain data, data-masking policies enable dynamically | |
| mask sensitive data as users access the data, for example to ensure that: | |
| </p> | |
| <p class="ranger-blog__list-item">-analysts have access to only specific part of birthday (year or month or day)</p> | |
| <p class="ranger-blog__list-item">-only last 4 digits of a national id are available to customer service representatives</p> | |
| <p class="ranger-blog__list-item">-only salary ranges of employees (i.e., not the salary) are available to analysts</p><p> | |
| In addition to supporting data-masking policies on resources, like columns in Apache Hive/Snowflake/Databricks | |
| SQL/Presto, Apache Ranger enables setting up data-masking policies based on classifications (tags) associated | |
| with resources. This can significantly reduce the complexity in managing masking policies. In addition, | |
| tag-based masking policies leverage classifications added to resources by data stewards and tools that scan | |
| data for sensitive information. | |
| </p> | |
| <h1 id="s6">Row-filter</h1> | |
| <p> | |
| Apache Ranger row-filter policies enable enterprises to allow users to access only a subset of data depending | |
| upon the context in which a user accesses the data. When a table having a row-filter is accessed by the user, | |
| only a subset of rows will be visible to the user – depending upon the filter setup in row-filter policy. | |
| Row-filters can be used for example to ensure that: | |
| </p> | |
| <p class="ranger-blog__list-item">-data of customers residing in a country is available only to analysts authorized to access the country’s data</p> | |
| <p class="ranger-blog__list-item">-a store manager has access to only data relevant to the store she/he works in</p> | |
| <p class="ranger-blog__list-item">-analysts don’t have access to sensitive records</p> | |
| <h1 id="s7">Access audit logs</h1> | |
| <p> | |
| Apache Ranger generates audit logs of accesses to resources protected by Apache Ranger authorization. Apache | |
| Ranger can be configured to store audit logs in multiple destinations, including Solr, HDFS, AWS S3, AWS | |
| CloudWatch, ADLS-Gen2, Elasticsearch. Audit logs generated by Apache Ranger include following details, which | |
| can help enterprises to satisfy various compliance requirements: | |
| </p><p class="ranger-blog__list-item">-resource accessed; action performed; was access allowed</p> | |
| <p class="ranger-blog__list-item">-time of access, tags associated with the resource (PII, PCI, PHI, ..)</p> | |
| <p class="ranger-blog__list-item">-who performed the access, IP address from which the access was performed</p> | |
| <p class="ranger-blog__list-item">-ID of Apache Ranger policy that allowed or denied the access</p><p> | |
| Apache Ranger provides an interactive user interface to view audit logs stored in Solr, Elasticsearch or AWS | |
| CloudWatch, with search capabilities to look for access audits for specific resources, specific users, client | |
| IP addresses, within a given time frame, specific classifications. Apache Ranger audit logs can be stored in | |
| ORC or JSON formats, which can then be loaded into various tools for analysis. | |
| </p><h1 id="references">References</h1> | |
| <p class="ranger-blog__list-item">-<a href="https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=61322361">Apache Ranger: tag-based policies</a></p> | |
| <p class="ranger-blog__list-item">-<a href="https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=65868896">Apache Ranger: row-filter and data-masking policies</a></p> | |
| <p class="ranger-blog__list-item">-<a href="https://cwiki.apache.org/confluence/display/RANGER/Introduction+of+Security+Zones+in+Ranger">Apache Ranger: security zones</a></p> | |
| <p class="ranger-blog__list-item">-<a href="https://pypi.org/project/apache-ranger/">Apache Ranger: Python</a></p> | |
| <p class="ranger-blog__list-item">-<a href="https://cwiki.apache.org/confluence/display/RANGER/Ranger+Client+Libraries">Apache Ranger: Java</a></p> | |
| <p class="ranger-blog__list-item">-<a href="https://ranger.apache.org/apidocs/index.html">Apache Ranger: REST</a></p> | |
| </div> | |
| </div> | |
| </section> | |
| </body> | |
| </document> |