<?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: ISE 3.1 linux application posture policy in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-3-1-linux-application-posture-policy/m-p/4678638#M577009</link>
    <description>&lt;P&gt;Yes we are running anyconnect.&amp;nbsp; 4.10.3104&lt;/P&gt;&lt;P&gt;compliance module 4.3.1968.0&lt;/P&gt;</description>
    <pubDate>Tue, 30 Aug 2022 12:01:11 GMT</pubDate>
    <dc:creator>Joseph.F</dc:creator>
    <dc:date>2022-08-30T12:01:11Z</dc:date>
    <item>
      <title>ISE 3.1 linux application posture policy</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-3-1-linux-application-posture-policy/m-p/4678623#M577007</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I'm trying to create a posture application condition for a Red Hat linux policy that looks for the puppet process to be running.&amp;nbsp;&lt;/P&gt;&lt;P&gt;a ps -aux | grep puppet shows:&amp;nbsp; path/puppet agent --no-daemonize&lt;/P&gt;&lt;P&gt;I've tried every variation of that process that i can think of but this compliance check fails on systems that are running this process.&amp;nbsp; I have other application conditions that work as expected for Linux however those conditions don't have a space in the process name i.e. puppet agent.&amp;nbsp; Anyone else have similar experiences?&amp;nbsp; I would like to get this check working so it is consistent with the other operating systems posture policies.&lt;/P&gt;</description>
      <pubDate>Tue, 30 Aug 2022 11:42:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-3-1-linux-application-posture-policy/m-p/4678623#M577007</guid>
      <dc:creator>Joseph.F</dc:creator>
      <dc:date>2022-08-30T11:42:31Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 3.1 linux application posture policy</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-3-1-linux-application-posture-policy/m-p/4678634#M577008</link>
      <description>&lt;P&gt;is the Linux running any connect client, what is the version of anyconnect client.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 30 Aug 2022 11:54:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-3-1-linux-application-posture-policy/m-p/4678634#M577008</guid>
      <dc:creator>balaji.bandi</dc:creator>
      <dc:date>2022-08-30T11:54:21Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 3.1 linux application posture policy</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-3-1-linux-application-posture-policy/m-p/4678638#M577009</link>
      <description>&lt;P&gt;Yes we are running anyconnect.&amp;nbsp; 4.10.3104&lt;/P&gt;&lt;P&gt;compliance module 4.3.1968.0&lt;/P&gt;</description>
      <pubDate>Tue, 30 Aug 2022 12:01:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-3-1-linux-application-posture-policy/m-p/4678638#M577009</guid>
      <dc:creator>Joseph.F</dc:creator>
      <dc:date>2022-08-30T12:01:11Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 3.1 linux application posture policy</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-3-1-linux-application-posture-policy/m-p/4680498#M577094</link>
      <description>&lt;P&gt;related question for the posture ise experts.&amp;nbsp; What command does the compliance module run on the back end of the linux machine to determine running processes?&lt;/P&gt;</description>
      <pubDate>Fri, 02 Sep 2022 16:52:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-3-1-linux-application-posture-policy/m-p/4680498#M577094</guid>
      <dc:creator>Joseph.F</dc:creator>
      <dc:date>2022-09-02T16:52:43Z</dc:date>
    </item>
  </channel>
</rss>

