<?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 Client Access Rule in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/csa-client-access-rule/m-p/615035#M87329</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Finally I went and created a CSA Client Admin list and its opposite which I called CSA Users and then made 2 UI rules. One that allows full access and another that does not allow any user interaction. Seemed to work for me.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 21 Mar 2007 21:13:43 GMT</pubDate>
    <dc:creator>shank15217</dc:creator>
    <dc:date>2007-03-21T21:13:43Z</dc:date>
    <item>
      <title>CSA Client Access Rule</title>
      <link>https://community.cisco.com/t5/network-security/csa-client-access-rule/m-p/615031#M87320</link>
      <description>&lt;P&gt;I am running CSA on a number of workstations in live mode but I wanted to give certain users (techs) privileged access so i created a user state group with those users and when those users log into a machine with csa they are able to see the UI and disable/enable csa to install applications. For other users the UI rule is not enabled so not its viewable on their desktop. It seems to be working however the UI frequently disappears if I make a rule change or create a new rule. Is this a good way or am I hacking it in a way it shouldn't be used. Right now the techs have to reboot the machine and relog into their accounts to see the CSA client icon. Seems to me there should be a better way.&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 10:30:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/csa-client-access-rule/m-p/615031#M87320</guid>
      <dc:creator>shank15217</dc:creator>
      <dc:date>2019-03-10T10:30:06Z</dc:date>
    </item>
    <item>
      <title>Re: CSA Client Access Rule</title>
      <link>https://community.cisco.com/t5/network-security/csa-client-access-rule/m-p/615032#M87323</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Sounds like a good way.  Be sure there are no other Agent UI Control rules that might be stepping on the one you created.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also, the Agent UI will disappear if there are no Agent UI Control rules applied to the host.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Tom&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 07 Mar 2007 18:46:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/csa-client-access-rule/m-p/615032#M87323</guid>
      <dc:creator>tsteger1</dc:creator>
      <dc:date>2007-03-07T18:46:03Z</dc:date>
    </item>
    <item>
      <title>Re: CSA Client Access Rule</title>
      <link>https://community.cisco.com/t5/network-security/csa-client-access-rule/m-p/615033#M87325</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;ah ok that helps a lot. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Mar 2007 19:05:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/csa-client-access-rule/m-p/615033#M87325</guid>
      <dc:creator>shank15217</dc:creator>
      <dc:date>2007-03-08T19:05:17Z</dc:date>
    </item>
    <item>
      <title>Re: CSA Client Access Rule</title>
      <link>https://community.cisco.com/t5/network-security/csa-client-access-rule/m-p/615034#M87327</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Also keep in mind you can turn off CSA via command line and by disabling the service.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I don't know if you want your tec to know this or not.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Mar 2007 20:32:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/csa-client-access-rule/m-p/615034#M87327</guid>
      <dc:creator>TradeSecrets</dc:creator>
      <dc:date>2007-03-08T20:32:13Z</dc:date>
    </item>
    <item>
      <title>Re: CSA Client Access Rule</title>
      <link>https://community.cisco.com/t5/network-security/csa-client-access-rule/m-p/615035#M87329</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Finally I went and created a CSA Client Admin list and its opposite which I called CSA Users and then made 2 UI rules. One that allows full access and another that does not allow any user interaction. Seemed to work for me.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 21 Mar 2007 21:13:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/csa-client-access-rule/m-p/615035#M87329</guid>
      <dc:creator>shank15217</dc:creator>
      <dc:date>2007-03-21T21:13:43Z</dc:date>
    </item>
    <item>
      <title>Re: CSA Client Access Rule</title>
      <link>https://community.cisco.com/t5/network-security/csa-client-access-rule/m-p/615036#M87334</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Cool, glad to hear it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Tom&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 21 Mar 2007 22:21:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/csa-client-access-rule/m-p/615036#M87334</guid>
      <dc:creator>tsteger1</dc:creator>
      <dc:date>2007-03-21T22:21:28Z</dc:date>
    </item>
  </channel>
</rss>

