<?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: CSA Poison Pill  in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/csa-poison-pill/m-p/974045#M79870</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I guess you should determine why you are doing this before you choose a what and how.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you simply want to disable a system to protect other systems, the network quarantine feature should work.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you want to make it so a system that triggers certain rules should be disabled so that no changes can be made to it, there are ways to do that too.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You would still be able to return system to a functioning state from the MC without reimaging it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CSA needs the system functioning in order to be effective at enforcing rules.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Booting into safe mode will bypass CSA but there are ways to disable that as well.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Tom&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 05 Jun 2008 17:25:55 GMT</pubDate>
    <dc:creator>tsteger1</dc:creator>
    <dc:date>2008-06-05T17:25:55Z</dc:date>
    <item>
      <title>CSA Poison Pill</title>
      <link>https://community.cisco.com/t5/network-security/csa-poison-pill/m-p/974042#M79867</link>
      <description>&lt;P&gt;I have to create a Poison Pill where CSA can essentially disable a system to the point that it is unusable and not recoverable. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I know there are several rules that can possibly do this by themselves, but I was wondering what would be the most effective where the system would have to be re-imaged in order to make it useable again. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am running V5.0.0.229 agent on XP images. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I was thinking of not allowing services.exe to run anything.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What would you recommend? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 11:08:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/csa-poison-pill/m-p/974042#M79867</guid>
      <dc:creator>dkthomas</dc:creator>
      <dc:date>2019-03-10T11:08:05Z</dc:date>
    </item>
    <item>
      <title>Re: CSA Poison Pill</title>
      <link>https://community.cisco.com/t5/network-security/csa-poison-pill/m-p/974043#M79868</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There may be a way to do this with less drastic measures but first, a couple of questions:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How would CSA enforce security if CSA was unable to run?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Do you prevent booting into safe mode?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Tom&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 03 Jun 2008 16:57:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/csa-poison-pill/m-p/974043#M79868</guid>
      <dc:creator>tsteger1</dc:creator>
      <dc:date>2008-06-03T16:57:51Z</dc:date>
    </item>
    <item>
      <title>Re: CSA Poison Pill</title>
      <link>https://community.cisco.com/t5/network-security/csa-poison-pill/m-p/974044#M79869</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Well... that is a good question... &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I was about to try that on a laptop just to see what happens... But as you pointed out, if the service can't start CSA... then CSA couldn't apply the rules...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But then again... would the system start CSA but stop everything else from starting after CSA started once the rules are applied? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Anyway, the answer to your second question: Booting into safe mode has not been disabled.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Which brings me back to my question: What would be the most effect method to disable a system? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Or is booting into SafeMode allows the bypassing all of the CSA rules?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 Jun 2008 22:03:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/csa-poison-pill/m-p/974044#M79869</guid>
      <dc:creator>dkthomas</dc:creator>
      <dc:date>2008-06-04T22:03:29Z</dc:date>
    </item>
    <item>
      <title>Re: CSA Poison Pill</title>
      <link>https://community.cisco.com/t5/network-security/csa-poison-pill/m-p/974045#M79870</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I guess you should determine why you are doing this before you choose a what and how.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you simply want to disable a system to protect other systems, the network quarantine feature should work.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you want to make it so a system that triggers certain rules should be disabled so that no changes can be made to it, there are ways to do that too.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You would still be able to return system to a functioning state from the MC without reimaging it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CSA needs the system functioning in order to be effective at enforcing rules.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Booting into safe mode will bypass CSA but there are ways to disable that as well.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Tom&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2008 17:25:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/csa-poison-pill/m-p/974045#M79870</guid>
      <dc:creator>tsteger1</dc:creator>
      <dc:date>2008-06-05T17:25:55Z</dc:date>
    </item>
    <item>
      <title>Re: CSA Poison Pill</title>
      <link>https://community.cisco.com/t5/network-security/csa-poison-pill/m-p/974046#M79871</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Dk,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Create a group that doesn't let any communication. CSA has a firewall built in.&lt;/P&gt;&lt;P&gt;Have the group priority deny any connection. Also play with the priority terminate.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What is the reason for this group ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Jun 2008 18:51:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/csa-poison-pill/m-p/974046#M79871</guid>
      <dc:creator>TradeSecrets</dc:creator>
      <dc:date>2008-06-26T18:51:06Z</dc:date>
    </item>
  </channel>
</rss>

