<?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: web access on vpn in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/web-access-on-vpn/m-p/1576474#M695713</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;i.e&lt;/P&gt;&lt;P&gt;You know how you can have multiple VPN groups (IPsec or SSL), each one has its own tunnel-group configuration.&lt;/P&gt;&lt;P&gt;Then, you can call a different group-policy for each tunnel-group that you have configured.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So, a particular tunnel-group that needs to have split-tunneling, could have a configuration like:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;group-policy vpnclient internal&lt;BR /&gt;group-policy vpnclient attributes&lt;BR /&gt; split-tunnel-policy tunnelspecified&lt;BR /&gt; split-tunnel-network-list value 102&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Where ACL 102 dictates the traffic to be encrypted.&lt;/P&gt;&lt;P&gt;If ACL 102 is something like:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;access-list 102 permit ip any 10.1.1.0 255.255.255.0&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;where 10.1.1.0/24 is the VPN pool of addresses, you're effectively sending all traffic through the tunnel.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then, if you configure regular NAT:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;nat (outside) 1 10.1.1.0 255.255.255.0 &lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;global (outside) 1 interface &lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;same-security-traffic permit intra-interface&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The above configuration will send all traffic through the tunnel and will be NATed and routed out to the Internet by the ASA out the same outside interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To restrict outbound traffic, you could apply an ACL in the outbound direction on the outside interface allowing only the IPs for the websites you need.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope it helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Federico.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 21 Sep 2010 05:25:23 GMT</pubDate>
    <dc:creator>Federico Coto Fajardo</dc:creator>
    <dc:date>2010-09-21T05:25:23Z</dc:date>
    <item>
      <title>web access on vpn</title>
      <link>https://community.cisco.com/t5/network-security/web-access-on-vpn/m-p/1576471#M695689</link>
      <description>&lt;P&gt;Any possible method to permit only one of many vpn groups to access internet when connected to ssl vpn.&lt;/P&gt;&lt;P&gt;and is it possible to permit only few internet web sites, with specific ip address , to be allowed for particular vpn group.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks in advance.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 18:42:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/web-access-on-vpn/m-p/1576471#M695689</guid>
      <dc:creator>suthomas1</dc:creator>
      <dc:date>2019-03-11T18:42:50Z</dc:date>
    </item>
    <item>
      <title>Re: web access on vpn</title>
      <link>https://community.cisco.com/t5/network-security/web-access-on-vpn/m-p/1576472#M695697</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If you're referring to the ASA (as the firewall terminating the VPN) then...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can have a single group with a split-tunneling policy where you tunnel all traffic and provide Internet to this specific group.&lt;/P&gt;&lt;P&gt;If you have the IP addresses of the websites, you can create ACL to permit only access to those sites.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Other method will be to use the MPF to permit certain websites only.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Federico.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 21 Sep 2010 05:03:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/web-access-on-vpn/m-p/1576472#M695697</guid>
      <dc:creator>Federico Coto Fajardo</dc:creator>
      <dc:date>2010-09-21T05:03:18Z</dc:date>
    </item>
    <item>
      <title>Re: web access on vpn</title>
      <link>https://community.cisco.com/t5/network-security/web-access-on-vpn/m-p/1576473#M695704</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;apologies, it is an ASA 5540.&lt;/P&gt;&lt;P&gt;precisely, thats what is being asked for by our business. a certain group has to have internet while connected to vpn for only this one specific internet website.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;please elaborate a little on how this can be achieved.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 21 Sep 2010 05:11:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/web-access-on-vpn/m-p/1576473#M695704</guid>
      <dc:creator>suthomas1</dc:creator>
      <dc:date>2010-09-21T05:11:21Z</dc:date>
    </item>
    <item>
      <title>Re: web access on vpn</title>
      <link>https://community.cisco.com/t5/network-security/web-access-on-vpn/m-p/1576474#M695713</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;i.e&lt;/P&gt;&lt;P&gt;You know how you can have multiple VPN groups (IPsec or SSL), each one has its own tunnel-group configuration.&lt;/P&gt;&lt;P&gt;Then, you can call a different group-policy for each tunnel-group that you have configured.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So, a particular tunnel-group that needs to have split-tunneling, could have a configuration like:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;group-policy vpnclient internal&lt;BR /&gt;group-policy vpnclient attributes&lt;BR /&gt; split-tunnel-policy tunnelspecified&lt;BR /&gt; split-tunnel-network-list value 102&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Where ACL 102 dictates the traffic to be encrypted.&lt;/P&gt;&lt;P&gt;If ACL 102 is something like:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;access-list 102 permit ip any 10.1.1.0 255.255.255.0&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;where 10.1.1.0/24 is the VPN pool of addresses, you're effectively sending all traffic through the tunnel.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then, if you configure regular NAT:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;nat (outside) 1 10.1.1.0 255.255.255.0 &lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;global (outside) 1 interface &lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;same-security-traffic permit intra-interface&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The above configuration will send all traffic through the tunnel and will be NATed and routed out to the Internet by the ASA out the same outside interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To restrict outbound traffic, you could apply an ACL in the outbound direction on the outside interface allowing only the IPs for the websites you need.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope it helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Federico.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 21 Sep 2010 05:25:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/web-access-on-vpn/m-p/1576474#M695713</guid>
      <dc:creator>Federico Coto Fajardo</dc:creator>
      <dc:date>2010-09-21T05:25:23Z</dc:date>
    </item>
    <item>
      <title>Re: web access on vpn</title>
      <link>https://community.cisco.com/t5/network-security/web-access-on-vpn/m-p/1576475#M695722</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;used this configuration to try over.but had few thoughts on this:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is acl 102 ip pool for this set of users ? this acl didnt show any hits on it when internet was tested.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;removing of &lt;STRONG&gt;split-tunnel-policy tunnelspecified&lt;BR /&gt; split-tunnel-network-list value 102 , &lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;these two lines from current group-policy doesnt stop user groups to browse, browsing stops only after same interface security is removed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i was thinking on how control would work if applied over selected multiple groups , since same-interface is a global command.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;to try out, i used acl on nat statements to define user pool and destination ip &amp;amp; it did work fine. after i remove the nat acl it stops working.&lt;/P&gt;&lt;P&gt;which is a good control looking for.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Appreciate all advises in advance.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 21 Sep 2010 09:02:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/web-access-on-vpn/m-p/1576475#M695722</guid>
      <dc:creator>suthomas1</dc:creator>
      <dc:date>2010-09-21T09:02:42Z</dc:date>
    </item>
  </channel>
</rss>

