<?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: Non-working rules in Cisco ISE for posturing services on MacOS in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/non-working-rules-in-cisco-ise-for-posturing-services-on-macos/m-p/4777692#M579894</link>
    <description>&lt;P&gt;hello&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1432646"&gt;@Aleksandr Pashko&lt;/a&gt;, are you using the latest compliance ? if you don't please make sure you are using it in the machines affected , ensure also that the posture feed is also updated within ISE .&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Let me know if that helped .&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 17 Feb 2023 20:54:41 GMT</pubDate>
    <dc:creator>Rodrigo Diaz</dc:creator>
    <dc:date>2023-02-17T20:54:41Z</dc:date>
    <item>
      <title>Non-working rules in Cisco ISE for posturing services on MacOS</title>
      <link>https://community.cisco.com/t5/network-access-control/non-working-rules-in-cisco-ise-for-posturing-services-on-macos/m-p/4777446#M579885</link>
      <description>&lt;P&gt;Hello everyone!&lt;/P&gt;&lt;P&gt;We need to understand why ISE posture fails on process checks on MacOS.&lt;/P&gt;&lt;P&gt;For example, we need to check that the datalossd or datalosste processes are running. Here is an example of output from one device, where you can see that the processes are running:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="AleksandrPashko_0-1676639038724.png" style="width: 400px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/176717iB73F19C7611ED745/image-size/medium?v=v2&amp;amp;px=400" role="button" title="AleksandrPashko_0-1676639038724.png" alt="AleksandrPashko_0-1676639038724.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;This is what the enabled checks look like:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="AleksandrPashko_1-1676639142409.png" style="width: 400px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/176718iC2104BBDB9C5F86E/image-size/medium?v=v2&amp;amp;px=400" role="button" title="AleksandrPashko_1-1676639142409.png" alt="AleksandrPashko_1-1676639142409.png" /&gt;&lt;/span&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="AleksandrPashko_2-1676639170204.png" style="width: 400px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/176719i7C585EF1F7040289/image-size/medium?v=v2&amp;amp;px=400" role="button" title="AleksandrPashko_2-1676639170204.png" alt="AleksandrPashko_2-1676639170204.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;As far as I understand, by design it should not give any error. It's just that the system scan does not consider the process running. He simply does not see him, hence he believes that the condition fails. I attached screenshots of the troubleshoot, but in fact they just say that the air conditioner has failed.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="AleksandrPashko_4-1676640138202.png" style="width: 400px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/176721i858BDB3BE1AA0B04/image-size/medium?v=v2&amp;amp;px=400" role="button" title="AleksandrPashko_4-1676640138202.png" alt="AleksandrPashko_4-1676640138202.png" /&gt;&lt;/span&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="AleksandrPashko_5-1676640226424.png" style="width: 400px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/176722iC37D3E4C9573BDFC/image-size/medium?v=v2&amp;amp;px=400" role="button" title="AleksandrPashko_5-1676640226424.png" alt="AleksandrPashko_5-1676640226424.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Moreover, each of these checks fails and it is not very clear why.&lt;BR /&gt;Perhaps you need to specify the process name in some other way or take it in some other place or with some kind of prefix.&lt;BR /&gt;Please help/suggest what we are doing wrong and how to make it work correctly?&amp;nbsp;For example, for windows, if you specify the name of the process, as it is visible in system monitor, then such a check passes successfully.&lt;/P&gt;</description>
      <pubDate>Fri, 17 Feb 2023 13:24:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/non-working-rules-in-cisco-ise-for-posturing-services-on-macos/m-p/4777446#M579885</guid>
      <dc:creator>Aleksandr Pashko</dc:creator>
      <dc:date>2023-02-17T13:24:26Z</dc:date>
    </item>
    <item>
      <title>Re: Non-working rules in Cisco ISE for posturing services on MacOS</title>
      <link>https://community.cisco.com/t5/network-access-control/non-working-rules-in-cisco-ise-for-posturing-services-on-macos/m-p/4777692#M579894</link>
      <description>&lt;P&gt;hello&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1432646"&gt;@Aleksandr Pashko&lt;/a&gt;, are you using the latest compliance ? if you don't please make sure you are using it in the machines affected , ensure also that the posture feed is also updated within ISE .&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Let me know if that helped .&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 17 Feb 2023 20:54:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/non-working-rules-in-cisco-ise-for-posturing-services-on-macos/m-p/4777692#M579894</guid>
      <dc:creator>Rodrigo Diaz</dc:creator>
      <dc:date>2023-02-17T20:54:41Z</dc:date>
    </item>
    <item>
      <title>Re: Non-working rules in Cisco ISE for posturing services on MacOS</title>
      <link>https://community.cisco.com/t5/network-access-control/non-working-rules-in-cisco-ise-for-posturing-services-on-macos/m-p/4777693#M579895</link>
      <description>&lt;P&gt;I was referring to the latest ISE compliance module in my latest post.&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 17 Feb 2023 20:55:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/non-working-rules-in-cisco-ise-for-posturing-services-on-macos/m-p/4777693#M579895</guid>
      <dc:creator>Rodrigo Diaz</dc:creator>
      <dc:date>2023-02-17T20:55:30Z</dc:date>
    </item>
    <item>
      <title>Re: Non-working rules in Cisco ISE for posturing services on MacOS</title>
      <link>https://community.cisco.com/t5/network-access-control/non-working-rules-in-cisco-ise-for-posturing-services-on-macos/m-p/4778497#M579923</link>
      <description>&lt;P&gt;Hello&lt;/P&gt;&lt;P&gt;thank you for the answer&amp;nbsp;&lt;/P&gt;&lt;P&gt;You mean the compliance module in the AnyConnect for MacOS?&lt;/P&gt;</description>
      <pubDate>Mon, 20 Feb 2023 11:19:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/non-working-rules-in-cisco-ise-for-posturing-services-on-macos/m-p/4778497#M579923</guid>
      <dc:creator>Aleksandr Pashko</dc:creator>
      <dc:date>2023-02-20T11:19:12Z</dc:date>
    </item>
    <item>
      <title>Re: Non-working rules in Cisco ISE for posturing services on MacOS</title>
      <link>https://community.cisco.com/t5/network-access-control/non-working-rules-in-cisco-ise-for-posturing-services-on-macos/m-p/4778509#M579926</link>
      <description>&lt;P&gt;The OPSWAT module version is 4.3.2661.4353&lt;/P&gt;</description>
      <pubDate>Mon, 20 Feb 2023 11:34:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/non-working-rules-in-cisco-ise-for-posturing-services-on-macos/m-p/4778509#M579926</guid>
      <dc:creator>Aleksandr Pashko</dc:creator>
      <dc:date>2023-02-20T11:34:06Z</dc:date>
    </item>
    <item>
      <title>Re: Non-working rules in Cisco ISE for posturing services on MacOS</title>
      <link>https://community.cisco.com/t5/network-access-control/non-working-rules-in-cisco-ise-for-posturing-services-on-macos/m-p/4778663#M579930</link>
      <description>&lt;P&gt;yes I meant that module .&lt;/P&gt;</description>
      <pubDate>Mon, 20 Feb 2023 16:28:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/non-working-rules-in-cisco-ise-for-posturing-services-on-macos/m-p/4778663#M579930</guid>
      <dc:creator>Rodrigo Diaz</dc:creator>
      <dc:date>2023-02-20T16:28:40Z</dc:date>
    </item>
    <item>
      <title>Re: Non-working rules in Cisco ISE for posturing services on MacOS</title>
      <link>https://community.cisco.com/t5/network-access-control/non-working-rules-in-cisco-ise-for-posturing-services-on-macos/m-p/4779846#M579990</link>
      <description>&lt;P&gt;&lt;SPAN&gt;The OPSWAT module version is 4.3.2661.4353&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 21 Feb 2023 19:29:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/non-working-rules-in-cisco-ise-for-posturing-services-on-macos/m-p/4779846#M579990</guid>
      <dc:creator>Aleksandr Pashko</dc:creator>
      <dc:date>2023-02-21T19:29:47Z</dc:date>
    </item>
  </channel>
</rss>

