<?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 Blocking file export in SAS Enterprise Guide</title>
    <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Blocking-file-export/m-p/160741#M12470</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Can i block the export file feature to avoid data leak?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 15 May 2014 18:32:42 GMT</pubDate>
    <dc:creator>JoaoM</dc:creator>
    <dc:date>2014-05-15T18:32:42Z</dc:date>
    <item>
      <title>Blocking file export</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Blocking-file-export/m-p/160741#M12470</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Can i block the export file feature to avoid data leak?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 15 May 2014 18:32:42 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/Blocking-file-export/m-p/160741#M12470</guid>
      <dc:creator>JoaoM</dc:creator>
      <dc:date>2014-05-15T18:32:42Z</dc:date>
    </item>
    <item>
      <title>Re: Blocking file export</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Blocking-file-export/m-p/160742#M12471</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I think we need more details.&lt;/P&gt;&lt;P&gt;What type of export? PDF, Excel, SAS datasets?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 15 May 2014 18:51:46 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/Blocking-file-export/m-p/160742#M12471</guid>
      <dc:creator>Reeza</dc:creator>
      <dc:date>2014-05-15T18:51:46Z</dc:date>
    </item>
    <item>
      <title>Re: Blocking file export</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Blocking-file-export/m-p/160743#M12472</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What type of access to the data your users are having? &lt;BR /&gt;If they are responsible to have that data available, how would you prevent data-leaks by preventing some usage? &lt;/P&gt;&lt;P&gt;There are two mitigations:&lt;/P&gt;&lt;P&gt; - define your security controls in way that only&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; a/ personal keys are used by your users and&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; b/ those personal keys are limited to access just the data they are needing.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; This is part of the RBAC process. It includes the whole path of the used stack. (OS layer . external DBM, SAS metadata)&lt;BR /&gt;- Make the activities of the users traceable and auditable by using logging&lt;/P&gt;&lt;P&gt;This is SIEM Security Information and Event Management. &lt;/P&gt;&lt;P&gt;part of the "standard of good practice" included with ISO27k hipaa sox-404 and many more.&amp;nbsp; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 15 May 2014 19:05:35 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/Blocking-file-export/m-p/160743#M12472</guid>
      <dc:creator>jakarman</dc:creator>
      <dc:date>2014-05-15T19:05:35Z</dc:date>
    </item>
    <item>
      <title>Re: Blocking file export</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Blocking-file-export/m-p/160744#M12473</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I see little point in trying to block SAS's export capabilities as anyone with reasonable SAS knowledge can bypass them, for example using a DATA step with PUT statements to write external files.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If this is a data security issue, then it could be approached more from the who has access to what point of view - if you trust users to access the data, why can't you trust them to not export inappropriately?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 15 May 2014 19:49:46 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/Blocking-file-export/m-p/160744#M12473</guid>
      <dc:creator>SASKiwi</dc:creator>
      <dc:date>2014-05-15T19:49:46Z</dc:date>
    </item>
    <item>
      <title>Re: Blocking file export</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Blocking-file-export/m-p/160745#M12474</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Good points by all -- it can be a struggle to give users the tools they need to do their jobs, and then still try to lock down the capabilities that could potentially be abused.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SAS does have some options for this:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="active_link" href="http://blogs.sas.com/content/sgf/2014/03/19/sas-admin-superpowers/" title="http://blogs.sas.com/content/sgf/2014/03/19/sas-admin-superpowers/"&gt;New superpowers for SAS administrators - SAS Users Groups&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Even with these options, I wouldn't consider this a substitute for clear policies, diligent monitoring, and OS-level permissions that reflect who should be able to do what...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Chris&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 15 May 2014 20:52:52 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/Blocking-file-export/m-p/160745#M12474</guid>
      <dc:creator>ChrisHemedinger</dc:creator>
      <dc:date>2014-05-15T20:52:52Z</dc:date>
    </item>
    <item>
      <title>Re: Blocking file export</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Blocking-file-export/m-p/160746#M12475</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If you want additional info see: &lt;A href="http://www.securityinformationeventmanagement.com/siem.php" title="http://www.securityinformationeventmanagement.com/siem.php"&gt;SIEM&lt;/A&gt;&amp;nbsp; or &lt;A href="http://en.wikipedia.org/wiki/Security_information_management" title="http://en.wikipedia.org/wiki/Security_information_management"&gt;Security information management - Wikipedia, the free encyclopedia&lt;/A&gt; . You need a BI tool for log - analyses. SAS is not mentioned in this world although they could do or. The name popping up is Splunk.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 May 2014 06:55:16 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/Blocking-file-export/m-p/160746#M12475</guid>
      <dc:creator>jakarman</dc:creator>
      <dc:date>2014-05-16T06:55:16Z</dc:date>
    </item>
    <item>
      <title>Re: Blocking file export</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Blocking-file-export/m-p/160747#M12476</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Any user who can &lt;STRONG&gt;see&lt;/STRONG&gt; data can simply copy/paste it. Trust your users or not. If not, don't let them work with the data at all.&lt;/P&gt;&lt;P&gt;The only reasonable thing you can do is set logging to a level that lets you see all requests that were handled by the SAS system, so you can at least make a valid attempt to find out who accessed the relevant data at a given time, if something was leaked.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 May 2014 07:20:17 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/Blocking-file-export/m-p/160747#M12476</guid>
      <dc:creator>Kurt_Bremser</dc:creator>
      <dc:date>2014-05-16T07:20:17Z</dc:date>
    </item>
  </channel>
</rss>

