<?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: Secure Endpoint, allow internet access while computer is isolated? in Endpoint Security</title>
    <link>https://community.cisco.com/t5/endpoint-security/secure-endpoint-allow-internet-access-while-computer-is-isolated/m-p/5199331#M8540</link>
    <description>&lt;P&gt;You couldn't achieve this with endpoint isolation since it is meant to stop the endpoint from communicating with anything other than the Secure Endpoint servers. What you can do is move them to a policy with the IP Blacklist in place rather than isolating them if you see an issue where they would normally be isolated. I would caution against this approach since it would allow any malicious code to reach out to additional resources.&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;Matt&lt;/P&gt;</description>
    <pubDate>Thu, 26 Sep 2024 11:18:17 GMT</pubDate>
    <dc:creator>Matthew Franks</dc:creator>
    <dc:date>2024-09-26T11:18:17Z</dc:date>
    <item>
      <title>Secure Endpoint, allow internet access while computer is isolated?</title>
      <link>https://community.cisco.com/t5/endpoint-security/secure-endpoint-allow-internet-access-while-computer-is-isolated/m-p/5199074#M8537</link>
      <description>&lt;P&gt;Is it possible to put a machine in isolation, to keep it off our internal network, but still allow the machine to access the internet? I have built an IP Block List with our internal IPs, but we would want our end users to be able to access the internet if moved to this policy. Long story short, it is a policy to put traveling staff into, should their machine become compromised, as a temp fix until we are able to address the issue.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Wed, 25 Sep 2024 23:58:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/endpoint-security/secure-endpoint-allow-internet-access-while-computer-is-isolated/m-p/5199074#M8537</guid>
      <dc:creator>hank hale</dc:creator>
      <dc:date>2024-09-25T23:58:50Z</dc:date>
    </item>
    <item>
      <title>Re: Secure Endpoint, allow internet access while computer is isolated?</title>
      <link>https://community.cisco.com/t5/endpoint-security/secure-endpoint-allow-internet-access-while-computer-is-isolated/m-p/5199331#M8540</link>
      <description>&lt;P&gt;You couldn't achieve this with endpoint isolation since it is meant to stop the endpoint from communicating with anything other than the Secure Endpoint servers. What you can do is move them to a policy with the IP Blacklist in place rather than isolating them if you see an issue where they would normally be isolated. I would caution against this approach since it would allow any malicious code to reach out to additional resources.&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;Matt&lt;/P&gt;</description>
      <pubDate>Thu, 26 Sep 2024 11:18:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/endpoint-security/secure-endpoint-allow-internet-access-while-computer-is-isolated/m-p/5199331#M8540</guid>
      <dc:creator>Matthew Franks</dc:creator>
      <dc:date>2024-09-26T11:18:17Z</dc:date>
    </item>
    <item>
      <title>Re: Secure Endpoint, allow internet access while computer is isolated?</title>
      <link>https://community.cisco.com/t5/endpoint-security/secure-endpoint-allow-internet-access-while-computer-is-isolated/m-p/5199357#M8541</link>
      <description>&lt;P&gt;Thanks Matt!&lt;/P&gt;</description>
      <pubDate>Thu, 26 Sep 2024 12:08:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/endpoint-security/secure-endpoint-allow-internet-access-while-computer-is-isolated/m-p/5199357#M8541</guid>
      <dc:creator>hank hale</dc:creator>
      <dc:date>2024-09-26T12:08:33Z</dc:date>
    </item>
  </channel>
</rss>

