<?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 ISE and GDPR in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-and-gdpr/m-p/3507931#M510636</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Folks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With GDPR in the EU now, what impact does this have on ISE deployments doing AAA?&amp;nbsp; Anything that must be changed? configured differently?&amp;nbsp; Question is coming from a large multinational Insurance company.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 18 Apr 2018 19:27:56 GMT</pubDate>
    <dc:creator>kkaminsk</dc:creator>
    <dc:date>2018-04-18T19:27:56Z</dc:date>
    <item>
      <title>ISE and GDPR</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-and-gdpr/m-p/3507931#M510636</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Folks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With GDPR in the EU now, what impact does this have on ISE deployments doing AAA?&amp;nbsp; Anything that must be changed? configured differently?&amp;nbsp; Question is coming from a large multinational Insurance company.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 18 Apr 2018 19:27:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-and-gdpr/m-p/3507931#M510636</guid>
      <dc:creator>kkaminsk</dc:creator>
      <dc:date>2018-04-18T19:27:56Z</dc:date>
    </item>
    <item>
      <title>Re: ISE and GDPR</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-and-gdpr/m-p/3507932#M510637</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Atad is researching on this topic so I would suggest you to contact him in our PM team.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 18 Apr 2018 19:54:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-and-gdpr/m-p/3507932#M510637</guid>
      <dc:creator>hslai</dc:creator>
      <dc:date>2018-04-18T19:54:04Z</dc:date>
    </item>
    <item>
      <title>Re: ISE and GDPR</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-and-gdpr/m-p/3507933#M510638</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello, &lt;/P&gt;&lt;P&gt;Thank you for asking this question.&lt;/P&gt;&lt;P&gt;There are no changes required in the way we set up ISE in order to support&lt;SPAN style="font-size: 13.3333px;"&gt; the new GDPR regulations that would be enforced starting May 25th&lt;/SPAN&gt;. ISE enables our clients to configure their deployment to meet their business and regulatory needs. For example, using TrustSec for segmentation, customers have control over who get's access to what data. ISE also offers flexibility on what data should the system collect on connected end-points; this should be determined by the network admins to support their needs. Moreover, customers can configure when to delete collected data from the system, which is an imperative capability for complying with GDPR.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In summary, ISE is equipped to support new GDPR and there is no impact on existing ISE deployments.&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 23 Apr 2018 19:02:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-and-gdpr/m-p/3507933#M510638</guid>
      <dc:creator>atpeled</dc:creator>
      <dc:date>2018-04-23T19:02:49Z</dc:date>
    </item>
  </channel>
</rss>

