<?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: Security Risk in Administration and Deployment</title>
    <link>https://communities.sas.com/t5/Administration-and-Deployment/Security-Risk/m-p/531128#M15524</link>
    <description>&lt;P&gt;It depends on your situation. If the network traffic between your SAS clients and SAS servers is going over the public internet then I would say it is a definite risk as without it some SAS traffic is not securely encrypted and is open to hackers.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;On the other hand, if all of your SAS network traffic runs on a protected company intranet or over secure VPN links then it is less of a problem. Having said that, there is a strong trend in many organisations to encrypt all network traffic regardless of where it flows. The idea is that you should have multiple layers of security in place, so it is less likely that hackers will be able break all of them.&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 29 Jan 2019 19:12:30 GMT</pubDate>
    <dc:creator>SASKiwi</dc:creator>
    <dc:date>2019-01-29T19:12:30Z</dc:date>
    <item>
      <title>Security Risk</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Security-Risk/m-p/531117#M15523</link>
      <description>&lt;P&gt;Is there any security issues/risks if we do not have SAS/Secure SSL enabled?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://support.sas.com/kb/57/595.html" target="_blank"&gt;https://support.sas.com/kb/57/595.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I'm encountering this known issue and want to know if there were any possible issues with having this not installed.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 29 Jan 2019 18:50:43 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Security-Risk/m-p/531117#M15523</guid>
      <dc:creator>Reeza</dc:creator>
      <dc:date>2019-01-29T18:50:43Z</dc:date>
    </item>
    <item>
      <title>Re: Security Risk</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Security-Risk/m-p/531128#M15524</link>
      <description>&lt;P&gt;It depends on your situation. If the network traffic between your SAS clients and SAS servers is going over the public internet then I would say it is a definite risk as without it some SAS traffic is not securely encrypted and is open to hackers.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;On the other hand, if all of your SAS network traffic runs on a protected company intranet or over secure VPN links then it is less of a problem. Having said that, there is a strong trend in many organisations to encrypt all network traffic regardless of where it flows. The idea is that you should have multiple layers of security in place, so it is less likely that hackers will be able break all of them.&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 29 Jan 2019 19:12:30 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Security-Risk/m-p/531128#M15524</guid>
      <dc:creator>SASKiwi</dc:creator>
      <dc:date>2019-01-29T19:12:30Z</dc:date>
    </item>
    <item>
      <title>Re: Security Risk</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Security-Risk/m-p/539414#M15765</link>
      <description>Thanks!</description>
      <pubDate>Thu, 28 Feb 2019 17:56:56 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Security-Risk/m-p/539414#M15765</guid>
      <dc:creator>Reeza</dc:creator>
      <dc:date>2019-02-28T17:56:56Z</dc:date>
    </item>
  </channel>
</rss>

