<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Restricting access to secrets in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/restricting-access-to-secrets/m-p/96608#M39304</link>
    <description>&lt;P&gt;There isn't a "no permission" ACL as far as I am aware - the lowest is "read" which means any user will still be able to read the secrets.&lt;/P&gt;</description>
    <pubDate>Tue, 29 Oct 2024 08:23:04 GMT</pubDate>
    <dc:creator>jar</dc:creator>
    <dc:date>2024-10-29T08:23:04Z</dc:date>
    <item>
      <title>Restricting access to secrets</title>
      <link>https://community.databricks.com/t5/data-engineering/restricting-access-to-secrets/m-p/96601#M39302</link>
      <description>&lt;P&gt;Hi.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I want to restrict access to secrets to a security group, as the secrets can be used to retrieve sensitive data only a few people should see. Up until now, we have been using KV-backed secret scopes, but as it's sufficient that Databricks has the (get, list) ACLs for any user to retrieve those secrets using dbutils.secrets.get(), that will not work in this case. How can we restrict access to these secrets?&lt;/P&gt;&lt;P&gt;Best,&lt;/P&gt;&lt;P&gt;Johan.&lt;/P&gt;</description>
      <pubDate>Tue, 29 Oct 2024 07:14:31 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/restricting-access-to-secrets/m-p/96601#M39302</guid>
      <dc:creator>jar</dc:creator>
      <dc:date>2024-10-29T07:14:31Z</dc:date>
    </item>
    <item>
      <title>Re: Restricting access to secrets</title>
      <link>https://community.databricks.com/t5/data-engineering/restricting-access-to-secrets/m-p/96603#M39303</link>
      <description>&lt;P&gt;Hi Johan,&amp;nbsp;&lt;/P&gt;&lt;P&gt;this should work for restriction:&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="h_h_ak_0-1730187189796.png" style="width: 400px;"&gt;&lt;img src="https://community.databricks.com/t5/image/serverpage/image-id/12352iA45F9864DCC5FD88/image-size/medium?v=v2&amp;amp;px=400" role="button" title="h_h_ak_0-1730187189796.png" alt="h_h_ak_0-1730187189796.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://learn.microsoft.com/en-us/azure/databricks/security/secrets/secrets" target="_blank"&gt;https://learn.microsoft.com/en-us/azure/databricks/security/secrets/secrets&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;Fine granulat access based on secrets is currently not possible.&lt;/P&gt;&lt;P&gt;BR&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 29 Oct 2024 07:34:02 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/restricting-access-to-secrets/m-p/96603#M39303</guid>
      <dc:creator>h_h_ak</dc:creator>
      <dc:date>2024-10-29T07:34:02Z</dc:date>
    </item>
    <item>
      <title>Re: Restricting access to secrets</title>
      <link>https://community.databricks.com/t5/data-engineering/restricting-access-to-secrets/m-p/96608#M39304</link>
      <description>&lt;P&gt;There isn't a "no permission" ACL as far as I am aware - the lowest is "read" which means any user will still be able to read the secrets.&lt;/P&gt;</description>
      <pubDate>Tue, 29 Oct 2024 08:23:04 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/restricting-access-to-secrets/m-p/96608#M39304</guid>
      <dc:creator>jar</dc:creator>
      <dc:date>2024-10-29T08:23:04Z</dc:date>
    </item>
    <item>
      <title>Re: Restricting access to secrets</title>
      <link>https://community.databricks.com/t5/data-engineering/restricting-access-to-secrets/m-p/96612#M39306</link>
      <description>&lt;P&gt;You can define "READ" &amp;amp; "MANAGE".&lt;/P&gt;&lt;P&gt;You can set a group e.g. secret_users_group to the secret-scope and assign READ, than only the secret_users_group and MANAGE user has access. All others who are not in the group or not have rights to manage.&lt;/P&gt;</description>
      <pubDate>Tue, 29 Oct 2024 08:42:27 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/restricting-access-to-secrets/m-p/96612#M39306</guid>
      <dc:creator>h_h_ak</dc:creator>
      <dc:date>2024-10-29T08:42:27Z</dc:date>
    </item>
    <item>
      <title>Re: Restricting access to secrets</title>
      <link>https://community.databricks.com/t5/data-engineering/restricting-access-to-secrets/m-p/96738#M39331</link>
      <description>&lt;P&gt;Brilliant, thank you! &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 30 Oct 2024 03:14:51 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/restricting-access-to-secrets/m-p/96738#M39331</guid>
      <dc:creator>jar</dc:creator>
      <dc:date>2024-10-30T03:14:51Z</dc:date>
    </item>
  </channel>
</rss>

