<?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: Firepower - Allow based on AD Computer Object in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/firepower-allow-based-on-ad-computer-object/m-p/4166938#M1074769</link>
    <description>&lt;P&gt;Interestingly I had tried that a few weeks ago and could not make it working in any way. Although I could see the computer object in the ACP users tab and add it to the selected "users", the FMC could not treat it as a user, hence no traffic was matching. When I ran some identity debug, I kept seeing that object coming as unknown with all 9s. Then I thought it might have been caused by the $ sign appended to the computer name, I went to change that on the AD, but that did not help.&amp;nbsp;Also, although I could see the computer name correctly in the active sessions page, but never showed up in the connections event. My conclusion on this is that FMC can't treat the computers as users due to the object class "computer" associated to them.&lt;/P&gt;</description>
    <pubDate>Wed, 14 Oct 2020 17:54:30 GMT</pubDate>
    <dc:creator>Aref Alsouqi</dc:creator>
    <dc:date>2020-10-14T17:54:30Z</dc:date>
    <item>
      <title>Firepower - Allow based on AD Computer Object</title>
      <link>https://community.cisco.com/t5/network-security/firepower-allow-based-on-ad-computer-object/m-p/4166875#M1074757</link>
      <description>&lt;P&gt;If we are using pxGrid as our identity service, can we allow computers based on their computer object in AD? Ex. If we want to block an AD group of computers from accessing a resource?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 14 Oct 2020 16:31:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-allow-based-on-ad-computer-object/m-p/4166875#M1074757</guid>
      <dc:creator>Scott_22</dc:creator>
      <dc:date>2020-10-14T16:31:53Z</dc:date>
    </item>
    <item>
      <title>Re: Firepower - Allow based on AD Computer Object</title>
      <link>https://community.cisco.com/t5/network-security/firepower-allow-based-on-ad-computer-object/m-p/4166893#M1074760</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/753785"&gt;@Scott_22&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You could, but the only way the FMC/FTD would have a computer binding would be if the computer has been authenticated and is at the login prompt without a user logged in, otherwise that binding is replaced with a user/ip binding.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;HTH&lt;/P&gt;</description>
      <pubDate>Wed, 14 Oct 2020 16:56:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-allow-based-on-ad-computer-object/m-p/4166893#M1074760</guid>
      <dc:creator>Rob Ingram</dc:creator>
      <dc:date>2020-10-14T16:56:53Z</dc:date>
    </item>
    <item>
      <title>Re: Firepower - Allow based on AD Computer Object</title>
      <link>https://community.cisco.com/t5/network-security/firepower-allow-based-on-ad-computer-object/m-p/4166920#M1074765</link>
      <description>&lt;P&gt;Okay, so with that being said, there's not really a way to do this if a user is logged into the machine?&lt;/P&gt;</description>
      <pubDate>Wed, 14 Oct 2020 17:32:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-allow-based-on-ad-computer-object/m-p/4166920#M1074765</guid>
      <dc:creator>Scott_22</dc:creator>
      <dc:date>2020-10-14T17:32:55Z</dc:date>
    </item>
    <item>
      <title>Re: Firepower - Allow based on AD Computer Object</title>
      <link>https://community.cisco.com/t5/network-security/firepower-allow-based-on-ad-computer-object/m-p/4166924#M1074767</link>
      <description>&lt;P&gt;Correct.&lt;/P&gt;
&lt;P&gt;You'd need to block traffic based on the logged in user or group.&lt;/P&gt;</description>
      <pubDate>Wed, 14 Oct 2020 17:36:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-allow-based-on-ad-computer-object/m-p/4166924#M1074767</guid>
      <dc:creator>Rob Ingram</dc:creator>
      <dc:date>2020-10-14T17:36:39Z</dc:date>
    </item>
    <item>
      <title>Re: Firepower - Allow based on AD Computer Object</title>
      <link>https://community.cisco.com/t5/network-security/firepower-allow-based-on-ad-computer-object/m-p/4166938#M1074769</link>
      <description>&lt;P&gt;Interestingly I had tried that a few weeks ago and could not make it working in any way. Although I could see the computer object in the ACP users tab and add it to the selected "users", the FMC could not treat it as a user, hence no traffic was matching. When I ran some identity debug, I kept seeing that object coming as unknown with all 9s. Then I thought it might have been caused by the $ sign appended to the computer name, I went to change that on the AD, but that did not help.&amp;nbsp;Also, although I could see the computer name correctly in the active sessions page, but never showed up in the connections event. My conclusion on this is that FMC can't treat the computers as users due to the object class "computer" associated to them.&lt;/P&gt;</description>
      <pubDate>Wed, 14 Oct 2020 17:54:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-allow-based-on-ad-computer-object/m-p/4166938#M1074769</guid>
      <dc:creator>Aref Alsouqi</dc:creator>
      <dc:date>2020-10-14T17:54:30Z</dc:date>
    </item>
  </channel>
</rss>

