<?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: Database Security in SAS Data Management</title>
    <link>https://communities.sas.com/t5/SAS-Data-Management/Database-Security/m-p/352274#M10486</link>
    <description>&lt;P&gt;May not apply, but the simplistic solution is: If you are storing the data in a shared library folder, you can make the shared library folder read only or exclude the user from the folder. &amp;nbsp;If you are using a server, another (albeit hacky) solution would be to create a scheduled task to copy the data to a folder that has your specified priveledges. &amp;nbsp;This way, the user will be restricted to the datasets based on your specifications via windows, and not SAS.&lt;/P&gt;</description>
    <pubDate>Fri, 21 Apr 2017 18:10:33 GMT</pubDate>
    <dc:creator>thomp7050</dc:creator>
    <dc:date>2017-04-21T18:10:33Z</dc:date>
    <item>
      <title>Database Security</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/Database-Security/m-p/351993#M10464</link>
      <description>&lt;P&gt;Is there any possibility to grant right in accessing database like read, write or read&amp;amp;write?&lt;/P&gt;&lt;P&gt;through role or any permission?&lt;/P&gt;&lt;P&gt;As I have gone through the capability and it seems nothing for me to do it.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Apr 2017 03:09:20 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/Database-Security/m-p/351993#M10464</guid>
      <dc:creator>R_Chung</dc:creator>
      <dc:date>2017-04-21T03:09:20Z</dc:date>
    </item>
    <item>
      <title>Re: Database Security</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/Database-Security/m-p/352042#M10465</link>
      <description>Capabilities is about functionality, not data itself. &lt;BR /&gt;Two options that you could investigate :&lt;BR /&gt;- have the RDBMS libref assigned with the  META engine, thus enforcing SAS metadata authorization. &lt;BR /&gt;- set authorization within the database. Use appropriate login from SAS (users own with AUTHDOMAIN, or some group login that fits your needs.</description>
      <pubDate>Fri, 21 Apr 2017 04:24:46 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/Database-Security/m-p/352042#M10465</guid>
      <dc:creator>LinusH</dc:creator>
      <dc:date>2017-04-21T04:24:46Z</dc:date>
    </item>
    <item>
      <title>Re: Database Security</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/Database-Security/m-p/352084#M10470</link>
      <description>What do you mean for the first statement?&lt;BR /&gt;For the second statement, do you mean that we directly set authorization in database?</description>
      <pubDate>Fri, 21 Apr 2017 08:01:41 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/Database-Security/m-p/352084#M10470</guid>
      <dc:creator>R_Chung</dc:creator>
      <dc:date>2017-04-21T08:01:41Z</dc:date>
    </item>
    <item>
      <title>Re: Database Security</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/Database-Security/m-p/352111#M10472</link>
      <description>I assumed that you had a Metadata Server, no?&lt;BR /&gt;If you have it, you will for the users assign a libref that points to the Metadata registration for that library. Then, any tables in that libref can fall under SAS metadata authorization. Check the doc for more info.&lt;BR /&gt;&lt;BR /&gt;And yes, and you need somehow get the client user token/login to be used when connecting to the database.</description>
      <pubDate>Fri, 21 Apr 2017 10:58:34 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/Database-Security/m-p/352111#M10472</guid>
      <dc:creator>LinusH</dc:creator>
      <dc:date>2017-04-21T10:58:34Z</dc:date>
    </item>
    <item>
      <title>Re: Database Security</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/Database-Security/m-p/352274#M10486</link>
      <description>&lt;P&gt;May not apply, but the simplistic solution is: If you are storing the data in a shared library folder, you can make the shared library folder read only or exclude the user from the folder. &amp;nbsp;If you are using a server, another (albeit hacky) solution would be to create a scheduled task to copy the data to a folder that has your specified priveledges. &amp;nbsp;This way, the user will be restricted to the datasets based on your specifications via windows, and not SAS.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Apr 2017 18:10:33 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/Database-Security/m-p/352274#M10486</guid>
      <dc:creator>thomp7050</dc:creator>
      <dc:date>2017-04-21T18:10:33Z</dc:date>
    </item>
  </channel>
</rss>

