<?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 White List in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/white-list/m-p/1036019#M893029</link>
    <description>&lt;P&gt;I want to configure a couple of workstations on our network so that they can get only to URL's for Symantec, and then to a specific Web Server that we host that is public. &lt;/P&gt;&lt;P&gt;Short of configuring our ASA 5510 to use WebSense (which is pending), is there any other quick way to implement this control on the ASA for these two specific workstations?&lt;/P&gt;</description>
    <pubDate>Wed, 13 Mar 2019 00:58:42 GMT</pubDate>
    <dc:creator>Kevin Melton</dc:creator>
    <dc:date>2019-03-13T00:58:42Z</dc:date>
    <item>
      <title>White List</title>
      <link>https://community.cisco.com/t5/network-security/white-list/m-p/1036019#M893029</link>
      <description>&lt;P&gt;I want to configure a couple of workstations on our network so that they can get only to URL's for Symantec, and then to a specific Web Server that we host that is public. &lt;/P&gt;&lt;P&gt;Short of configuring our ASA 5510 to use WebSense (which is pending), is there any other quick way to implement this control on the ASA for these two specific workstations?&lt;/P&gt;</description>
      <pubDate>Wed, 13 Mar 2019 00:58:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/white-list/m-p/1036019#M893029</guid>
      <dc:creator>Kevin Melton</dc:creator>
      <dc:date>2019-03-13T00:58:42Z</dc:date>
    </item>
    <item>
      <title>Re: White List</title>
      <link>https://community.cisco.com/t5/network-security/white-list/m-p/1036020#M893034</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I've done this previously, but it's not pretty.  Here's what I would do:&lt;/P&gt;&lt;P&gt;1) Setup an Outbound ACL&lt;/P&gt;&lt;P&gt;  access-list Outbound-ACL permit ip host (workstation 1) host (Symantec1)&lt;/P&gt;&lt;P&gt;  access-list Outbound-ACL permit ip host (workstation 1) host (Symantec2)&lt;/P&gt;&lt;P&gt;  access-list Outbound-ACL permit ip host (workstation 1) host (Outside WebServer)&lt;/P&gt;&lt;P&gt;access-list Outbound-ACL deny ip host (workstation 1) any&lt;/P&gt;&lt;P&gt;*** Mirror this for Workstation 2, etc)&lt;/P&gt;&lt;P&gt;access-list Outbound-ACL permit ip any any&lt;/P&gt;&lt;P&gt; 2)  Apply the ACL to your inside interface&lt;/P&gt;&lt;P&gt;access-group Outbound-ACL in inter inside&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It can be a hassle, but it works.  I've also done blacklisting (not sure if this fits your environment) and the reference document is here.&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/products/ps6120/products_configuration_example09186a0080940e04.shtml" target="_blank"&gt;http://www.cisco.com/en/US/products/ps6120/products_configuration_example09186a0080940e04.shtml&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps, rate if it does, &lt;/P&gt;&lt;P&gt;JB&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 25 Nov 2008 20:52:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/white-list/m-p/1036020#M893034</guid>
      <dc:creator>jpoplawski</dc:creator>
      <dc:date>2008-11-25T20:52:40Z</dc:date>
    </item>
  </channel>
</rss>

