<?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: FTD via FDM in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/ftd-via-fdm/m-p/5035356#M1109694</link>
    <description>&lt;P&gt;That is correct&lt;/P&gt;</description>
    <pubDate>Wed, 06 Mar 2024 20:32:54 GMT</pubDate>
    <dc:creator>jebankshrcu</dc:creator>
    <dc:date>2024-03-06T20:32:54Z</dc:date>
    <item>
      <title>FTD via FDM</title>
      <link>https://community.cisco.com/t5/network-security/ftd-via-fdm/m-p/5035339#M1109689</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;I have been having a hard time to integrate ISE with my Cisco FTD since most of the articles covers using the FMC. For my FTD device I am using FDM not FMC. What I am trying to accomplish is to block web whatsapps by user usage. I have been able to integrate AD to my FTD but after a debug done with cisco tac they said I need ISE for the mapping of IP to user since the below log is showing the highlighted error.&lt;/P&gt;&lt;P&gt;&amp;gt; 157.240.14.52 443 6 AS=0 ID=1 GR=1-1 no match rule order 1, 'WhatsAppBlocking',&lt;STRONG&gt; user 9999999, realm 0&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;I have integrated ISE in my environment already but am stuck in the certification part. From what i understand I should enable pxgrid which i have already in ISE and generated the necessary certs for it but now on my FTD device side am only able to upload my CA certificate but am not able to generate my own cert in my FTD device.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 06 Mar 2024 20:06:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-via-fdm/m-p/5035339#M1109689</guid>
      <dc:creator>jebankshrcu</dc:creator>
      <dc:date>2024-03-06T20:06:51Z</dc:date>
    </item>
    <item>
      <title>Re: FTD via FDM</title>
      <link>https://community.cisco.com/t5/network-security/ftd-via-fdm/m-p/5035341#M1109690</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1509715"&gt;@jebankshrcu&lt;/a&gt; use openssl from the CLI of the FTD to generate the CSR, as per this guide:-&lt;/P&gt;
&lt;P&gt;&lt;A href="https://integratingit.wordpress.com/2021/11/06/fdm-pxgrid-integration-with-ise/" target="_blank"&gt;https://integratingit.wordpress.com/2021/11/06/fdm-pxgrid-integration-with-ise/&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 06 Mar 2024 20:09:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-via-fdm/m-p/5035341#M1109690</guid>
      <dc:creator>Rob Ingram</dc:creator>
      <dc:date>2024-03-06T20:09:34Z</dc:date>
    </item>
    <item>
      <title>Re: FTD via FDM</title>
      <link>https://community.cisco.com/t5/network-security/ftd-via-fdm/m-p/5035348#M1109691</link>
      <description>&lt;P&gt;Hi Rob:&lt;/P&gt;&lt;P&gt;Forgive my ignorance here. So for ISE to have this information for the IP mapping. I would need to have the end-user devices authenticate from the access switch to ISE via 802.1x which then that info there is what will be used to send to my FTD? Does my end-user devices (meaning laptops, desktop etc) have that connectivity to ISE for this to work?&lt;/P&gt;</description>
      <pubDate>Wed, 06 Mar 2024 20:24:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-via-fdm/m-p/5035348#M1109691</guid>
      <dc:creator>jebankshrcu</dc:creator>
      <dc:date>2024-03-06T20:24:46Z</dc:date>
    </item>
    <item>
      <title>Re: FTD via FDM</title>
      <link>https://community.cisco.com/t5/network-security/ftd-via-fdm/m-p/5035350#M1109692</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1509715"&gt;@jebankshrcu&lt;/a&gt; yes, the users authenticate via wired or wireless using ISE as the RADIUS server, which then sends the IP/user bindings to the FMC, and in turn sends these bindings to the FTD. If you add an AD realm you can use AD groups (which the users are a memver of) in the FTD ACP rules. &lt;A href="https://integratingit.wordpress.com/2021/11/07/fdm-identity-policy-and-ad-realm/" target="_blank"&gt;https://integratingit.wordpress.com/2021/11/07/fdm-identity-policy-and-ad-realm/&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;If using 802.1X authentication, its the switches that need to communicate with ISE.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 06 Mar 2024 20:30:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-via-fdm/m-p/5035350#M1109692</guid>
      <dc:creator>Rob Ingram</dc:creator>
      <dc:date>2024-03-06T20:30:12Z</dc:date>
    </item>
    <item>
      <title>Re: FTD via FDM</title>
      <link>https://community.cisco.com/t5/network-security/ftd-via-fdm/m-p/5035351#M1109693</link>
      <description>&lt;P&gt;What i get from your request is you need ACL apply to specific user' so you need way to make FTD recognize the user?&lt;/P&gt;
&lt;P&gt;MHM&lt;/P&gt;</description>
      <pubDate>Wed, 06 Mar 2024 20:30:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-via-fdm/m-p/5035351#M1109693</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2024-03-06T20:30:13Z</dc:date>
    </item>
    <item>
      <title>Re: FTD via FDM</title>
      <link>https://community.cisco.com/t5/network-security/ftd-via-fdm/m-p/5035356#M1109694</link>
      <description>&lt;P&gt;That is correct&lt;/P&gt;</description>
      <pubDate>Wed, 06 Mar 2024 20:32:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-via-fdm/m-p/5035356#M1109694</guid>
      <dc:creator>jebankshrcu</dc:creator>
      <dc:date>2024-03-06T20:32:54Z</dc:date>
    </item>
    <item>
      <title>Re: FTD via FDM</title>
      <link>https://community.cisco.com/t5/network-security/ftd-via-fdm/m-p/5035361#M1109695</link>
      <description>&lt;P&gt;That is what i have done on the FTD device. I have added AD realm and got the AD groups and have tried to match it via my ACL but the log error was the below:&lt;/P&gt;&lt;P&gt;157.240.14.52 443 6 AS=0 ID=1 GR=1-1 no match rule order 1, 'WhatsAppBlocking',&lt;STRONG&gt; user 9999999, realm 0&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;I will look over the second link you sent me. That on looks like what am trying to do&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 06 Mar 2024 20:35:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-via-fdm/m-p/5035361#M1109695</guid>
      <dc:creator>jebankshrcu</dc:creator>
      <dc:date>2024-03-06T20:35:30Z</dc:date>
    </item>
    <item>
      <title>Re: FTD via FDM</title>
      <link>https://community.cisco.com/t5/network-security/ftd-via-fdm/m-p/5035365#M1109696</link>
      <description>&lt;P&gt;check active auth by ftd for identity&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/support/docs/security/firepower-ngfw/217231-configure-fdm-active-authentication-cap.html" target="_blank"&gt;https://www.cisco.com/c/en/us/support/docs/security/firepower-ngfw/217231-configure-fdm-active-authentication-cap.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Check this&amp;nbsp;&lt;/P&gt;
&lt;P&gt;MHM&lt;/P&gt;</description>
      <pubDate>Wed, 06 Mar 2024 21:25:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-via-fdm/m-p/5035365#M1109696</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2024-03-06T21:25:32Z</dc:date>
    </item>
    <item>
      <title>Re: FTD via FDM</title>
      <link>https://community.cisco.com/t5/network-security/ftd-via-fdm/m-p/5035367#M1109697</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1509715"&gt;@jebankshrcu&lt;/a&gt; from your first post it sounds like you had not configured the certificate on the FMC, so you are unlikely to have an IP/user bindings learnt from ISE until you configure the integration correctly. The first link provided has the commands to use to troubleshoot and determine whether you have these bindings.&lt;/P&gt;</description>
      <pubDate>Wed, 06 Mar 2024 20:39:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-via-fdm/m-p/5035367#M1109697</guid>
      <dc:creator>Rob Ingram</dc:creator>
      <dc:date>2024-03-06T20:39:04Z</dc:date>
    </item>
    <item>
      <title>Re: FTD via FDM</title>
      <link>https://community.cisco.com/t5/network-security/ftd-via-fdm/m-p/5035369#M1109698</link>
      <description>&lt;P&gt;ok So from looking over the links. I need to make sure my access switches are integrated too. I was thinking that just getting AD realm integrated to my FTD via FDM was all i needed since i was able to pull my AD data from the configuration that was done for AD realm&lt;/P&gt;</description>
      <pubDate>Wed, 06 Mar 2024 20:40:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-via-fdm/m-p/5035369#M1109698</guid>
      <dc:creator>jebankshrcu</dc:creator>
      <dc:date>2024-03-06T20:40:53Z</dc:date>
    </item>
    <item>
      <title>Re: FTD via FDM</title>
      <link>https://community.cisco.com/t5/network-security/ftd-via-fdm/m-p/5035374#M1109699</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1509715"&gt;@jebankshrcu&lt;/a&gt; correct, without those IP/User bindings the FTD is not going to know which user the IP address is associated with. Both those links I provided include enough to get the bindings and AD realm integrated into FDM.&lt;/P&gt;</description>
      <pubDate>Wed, 06 Mar 2024 20:44:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-via-fdm/m-p/5035374#M1109699</guid>
      <dc:creator>Rob Ingram</dc:creator>
      <dc:date>2024-03-06T20:44:08Z</dc:date>
    </item>
    <item>
      <title>Re: FTD via FDM</title>
      <link>https://community.cisco.com/t5/network-security/ftd-via-fdm/m-p/5035377#M1109700</link>
      <description>&lt;P&gt;ok thanks for that clarity. Now I may have some issues then because my access switches are &lt;SPAN&gt;CBS350-48P-4X&lt;/SPAN&gt; models and I dont think it fully compatible with cisco ise. It does have some 802.1x functions but not compare to a 3750-x switch model etc.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 06 Mar 2024 20:50:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-via-fdm/m-p/5035377#M1109700</guid>
      <dc:creator>jebankshrcu</dc:creator>
      <dc:date>2024-03-06T20:50:15Z</dc:date>
    </item>
    <item>
      <title>Re: FTD via FDM</title>
      <link>https://community.cisco.com/t5/network-security/ftd-via-fdm/m-p/5035380#M1109701</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1509715"&gt;@jebankshrcu&lt;/a&gt; if the switch supports 802.1X, then it can authenticate against ISE, which can send those bindings to the FMC.&lt;/P&gt;</description>
      <pubDate>Wed, 06 Mar 2024 20:54:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-via-fdm/m-p/5035380#M1109701</guid>
      <dc:creator>Rob Ingram</dc:creator>
      <dc:date>2024-03-06T20:54:17Z</dc:date>
    </item>
    <item>
      <title>Re: FTD via FDM</title>
      <link>https://community.cisco.com/t5/network-security/ftd-via-fdm/m-p/5035384#M1109702</link>
      <description>&lt;P&gt;Hi Rob:&lt;/P&gt;&lt;P&gt;Thanks for the input. Let me try and see what I can do. I'll update you&lt;/P&gt;</description>
      <pubDate>Wed, 06 Mar 2024 20:59:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-via-fdm/m-p/5035384#M1109702</guid>
      <dc:creator>jebankshrcu</dc:creator>
      <dc:date>2024-03-06T20:59:11Z</dc:date>
    </item>
  </channel>
</rss>

