<?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: Fill out Security Technical Implementation Guide (STIG) Information in Administration and Deployment</title>
    <link>https://communities.sas.com/t5/Administration-and-Deployment/Fill-out-Security-Technical-Implementation-Guide-STIG/m-p/323189#M6946</link>
    <description>&lt;P&gt;In my experience the security requirements are included in the overall implementation design document. I don't believe there is such a thing as a 'standard' STIG, as each customer tends to have different requirements. Also bear in mind each customer has different security standards, something which should have been captured during the SAS design phase.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;As a starting point I would simply take the security requirements from the overall design doc and put them in a separate one, then ask the customer to review it and provide feedback.&lt;/P&gt;</description>
    <pubDate>Sun, 08 Jan 2017 01:12:29 GMT</pubDate>
    <dc:creator>SASKiwi</dc:creator>
    <dc:date>2017-01-08T01:12:29Z</dc:date>
    <item>
      <title>Fill out Security Technical Implementation Guide (STIG) Information</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Fill-out-Security-Technical-Implementation-Guide-STIG/m-p/323176#M6944</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Has anyone filled out a STIG for their client?&amp;nbsp; We have deployed SAS 9.4 M3 Grid for&amp;nbsp; our client and they want us to fill out a STIG.&amp;nbsp; Has anyone has experience filling out a STIG?&amp;nbsp; Thanks,&lt;/P&gt;&lt;P&gt;DJ&lt;/P&gt;</description>
      <pubDate>Sat, 07 Jan 2017 20:17:04 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Fill-out-Security-Technical-Implementation-Guide-STIG/m-p/323176#M6944</guid>
      <dc:creator>kdjamboe</dc:creator>
      <dc:date>2017-01-07T20:17:04Z</dc:date>
    </item>
    <item>
      <title>Re: Fill out Security Technical Implementation Guide (STIG) Information</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Fill-out-Security-Technical-Implementation-Guide-STIG/m-p/323189#M6946</link>
      <description>&lt;P&gt;In my experience the security requirements are included in the overall implementation design document. I don't believe there is such a thing as a 'standard' STIG, as each customer tends to have different requirements. Also bear in mind each customer has different security standards, something which should have been captured during the SAS design phase.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;As a starting point I would simply take the security requirements from the overall design doc and put them in a separate one, then ask the customer to review it and provide feedback.&lt;/P&gt;</description>
      <pubDate>Sun, 08 Jan 2017 01:12:29 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Fill-out-Security-Technical-Implementation-Guide-STIG/m-p/323189#M6946</guid>
      <dc:creator>SASKiwi</dc:creator>
      <dc:date>2017-01-08T01:12:29Z</dc:date>
    </item>
  </channel>
</rss>

