<?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 hiding Libname ODBC in DI_studio in Production in SAS Data Management</title>
    <link>https://communities.sas.com/t5/SAS-Data-Management/hiding-Libname-ODBC-in-DI-studio-in-Production/m-p/357237#M10722</link>
    <description>&lt;P&gt;A libname X&amp;nbsp;to &amp;nbsp;ODBC statetement with Authdomain parameter is&amp;nbsp;being used in&amp;nbsp; a Test environment in Di_Studio&amp;nbsp;4.6.&lt;/P&gt;&lt;P&gt;Libref contains tables with&amp;nbsp;high-confidential data.&lt;/P&gt;&lt;P&gt;In Acceptance enviroment Di_studio &amp;nbsp;the Libname X&amp;nbsp;is still visible for developers.&lt;/P&gt;&lt;P&gt;The libname definition X will&amp;nbsp;&amp;nbsp;be&amp;nbsp;secured.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;However,&amp;nbsp;the definition&amp;nbsp;may still&amp;nbsp;be derived by SAS&amp;nbsp; developer&amp;nbsp;using naming conventions.&amp;nbsp;Once the Authdomain parameter is&amp;nbsp;known,&amp;nbsp;the developer can have to the table. Also the SAS &amp;nbsp;log (which can be protected) may show the libname statement also.&lt;/P&gt;&lt;P&gt;The administrator (SAS) only should create/modify the libname in Acceptanace.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Are there best pratices within&amp;nbsp; SAS &amp;nbsp;to prevent a developer using&amp;nbsp;a Libname with the appropriate to access the tables in Production?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you&amp;nbsp;for suggestions. &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 10 May 2017 08:15:20 GMT</pubDate>
    <dc:creator>KC_Chan</dc:creator>
    <dc:date>2017-05-10T08:15:20Z</dc:date>
    <item>
      <title>hiding Libname ODBC in DI_studio in Production</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/hiding-Libname-ODBC-in-DI-studio-in-Production/m-p/357237#M10722</link>
      <description>&lt;P&gt;A libname X&amp;nbsp;to &amp;nbsp;ODBC statetement with Authdomain parameter is&amp;nbsp;being used in&amp;nbsp; a Test environment in Di_Studio&amp;nbsp;4.6.&lt;/P&gt;&lt;P&gt;Libref contains tables with&amp;nbsp;high-confidential data.&lt;/P&gt;&lt;P&gt;In Acceptance enviroment Di_studio &amp;nbsp;the Libname X&amp;nbsp;is still visible for developers.&lt;/P&gt;&lt;P&gt;The libname definition X will&amp;nbsp;&amp;nbsp;be&amp;nbsp;secured.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;However,&amp;nbsp;the definition&amp;nbsp;may still&amp;nbsp;be derived by SAS&amp;nbsp; developer&amp;nbsp;using naming conventions.&amp;nbsp;Once the Authdomain parameter is&amp;nbsp;known,&amp;nbsp;the developer can have to the table. Also the SAS &amp;nbsp;log (which can be protected) may show the libname statement also.&lt;/P&gt;&lt;P&gt;The administrator (SAS) only should create/modify the libname in Acceptanace.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Are there best pratices within&amp;nbsp; SAS &amp;nbsp;to prevent a developer using&amp;nbsp;a Libname with the appropriate to access the tables in Production?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you&amp;nbsp;for suggestions. &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 10 May 2017 08:15:20 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/hiding-Libname-ODBC-in-DI-studio-in-Production/m-p/357237#M10722</guid>
      <dc:creator>KC_Chan</dc:creator>
      <dc:date>2017-05-10T08:15:20Z</dc:date>
    </item>
    <item>
      <title>Re: hiding Libname ODBC in DI_studio in Production</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/hiding-Libname-ODBC-in-DI-studio-in-Production/m-p/357536#M10734</link>
      <description>You can't base security on having a secret syntax!&lt;BR /&gt;Protect the data at the source - hence a login from an unathorized user will be rejected or data that is not for him/her to see will not be visible.</description>
      <pubDate>Wed, 10 May 2017 15:37:56 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/hiding-Libname-ODBC-in-DI-studio-in-Production/m-p/357536#M10734</guid>
      <dc:creator>LinusH</dc:creator>
      <dc:date>2017-05-10T15:37:56Z</dc:date>
    </item>
  </channel>
</rss>

