<?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 or ISE that block access? in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/firepower-or-ise-that-block-access/m-p/4700630#M1094101</link>
    <description>&lt;P&gt;Is the identity source ISE, then ISE will have blocked user for this case i guess.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 10 Oct 2022 10:35:59 GMT</pubDate>
    <dc:creator>balaji.bandi</dc:creator>
    <dc:date>2022-10-10T10:35:59Z</dc:date>
    <item>
      <title>Firepower or ISE that block access?</title>
      <link>https://community.cisco.com/t5/network-security/firepower-or-ise-that-block-access/m-p/4700622#M1094098</link>
      <description>&lt;P&gt;hi, so i'm integrated my firepower with ISE, and i have a rule that will quarantine user that try to access something dangerous. The quarantine option come from ISE, but Firepower is the one that trigger the action.&lt;/P&gt;&lt;P&gt;I want to ask, if user get block into quarantine. Which technology responsible for it? Firepower or ISE?&lt;/P&gt;</description>
      <pubDate>Mon, 10 Oct 2022 10:12:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-or-ise-that-block-access/m-p/4700622#M1094098</guid>
      <dc:creator>raymondluis13</dc:creator>
      <dc:date>2022-10-10T10:12:39Z</dc:date>
    </item>
    <item>
      <title>Re: Firepower or ISE that block access?</title>
      <link>https://community.cisco.com/t5/network-security/firepower-or-ise-that-block-access/m-p/4700626#M1094100</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1412833"&gt;@raymondluis13&lt;/a&gt; ISE is the brains, when you quarantine it sends a CoA to reauthorise the session and can assign a different TrustSec SGT. The firepower device or switches, routers, WSA etc can all block traffic based on the SGT.&lt;/P&gt;</description>
      <pubDate>Mon, 10 Oct 2022 10:28:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-or-ise-that-block-access/m-p/4700626#M1094100</guid>
      <dc:creator>Rob Ingram</dc:creator>
      <dc:date>2022-10-10T10:28:53Z</dc:date>
    </item>
    <item>
      <title>Re: Firepower or ISE that block access?</title>
      <link>https://community.cisco.com/t5/network-security/firepower-or-ise-that-block-access/m-p/4700630#M1094101</link>
      <description>&lt;P&gt;Is the identity source ISE, then ISE will have blocked user for this case i guess.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 10 Oct 2022 10:35:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-or-ise-that-block-access/m-p/4700630#M1094101</guid>
      <dc:creator>balaji.bandi</dc:creator>
      <dc:date>2022-10-10T10:35:59Z</dc:date>
    </item>
    <item>
      <title>Re: Firepower or ISE that block access?</title>
      <link>https://community.cisco.com/t5/network-security/firepower-or-ise-that-block-access/m-p/4700683#M1094105</link>
      <description>&lt;P&gt;As&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/97036"&gt;@Rob Ingram&lt;/a&gt;&amp;nbsp;mentioned, ISE is the brain. It is essentially going to instruct the network device(s) with what action should be applied to the endpoint session that triggered the violation, the network device itself won't be able to do that, this is why we need the integration with ISE. For example, with Secure Network Analytics (Stealthwatch) you can configure the violation rules, then when and endpoint triggers a rule, Secure Network Analytics will share that with ISE, ISE will then trigger the reauthentication of that session and will instruct the switch (where the endpoint is connected) to reject the traffic from that endpoint.&lt;/P&gt;</description>
      <pubDate>Mon, 10 Oct 2022 12:42:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-or-ise-that-block-access/m-p/4700683#M1094105</guid>
      <dc:creator>Aref Alsouqi</dc:creator>
      <dc:date>2022-10-10T12:42:28Z</dc:date>
    </item>
  </channel>
</rss>

