<?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: ATM Machine profiling in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/atm-machine-profiling/m-p/5037803#M588015</link>
    <description>&lt;P&gt;As&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/158532"&gt;@Arne Bier&lt;/a&gt;&amp;nbsp;inferred in his previous response, you are not likely to get much detail from Profiling of an ATM endpoint. From my experience, most ATMs are built on generic platforms (like old Windows OS), so they would not provide any unique attributes.&lt;/P&gt;
&lt;P&gt;If you intend to pursue the Profiling route, you would need to determine what the network can glean from one of the ATM endpoints and build custom Profiling conditions/polices based on the &lt;A href="https://community.cisco.com/t5/security-knowledge-base/ise-profiling-design-guide/ta-p/3739456" target="_blank" rel="noopener"&gt;ISE Profiling Design Guide&lt;/A&gt;.&lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2024 23:17:57 GMT</pubDate>
    <dc:creator>Greg Gibbs</dc:creator>
    <dc:date>2024-03-11T23:17:57Z</dc:date>
    <item>
      <title>ATM Machine profiling</title>
      <link>https://community.cisco.com/t5/network-access-control/atm-machine-profiling/m-p/3755136#M487645</link>
      <description>&lt;P&gt;All,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I am looking for ISE profiling attributes for ATMs for a banking customer. These devices are non-Dot1x capable and have a static IP address assigned.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Has anyone done something similar before?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Manasi Jain&lt;/P&gt;</description>
      <pubDate>Thu, 29 Nov 2018 13:55:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/atm-machine-profiling/m-p/3755136#M487645</guid>
      <dc:creator>manasjai</dc:creator>
      <dc:date>2018-11-29T13:55:33Z</dc:date>
    </item>
    <item>
      <title>Re: ATM Machine profiling</title>
      <link>https://community.cisco.com/t5/network-access-control/atm-machine-profiling/m-p/3755728#M487646</link>
      <description>&lt;P&gt;It's one thing to rely on ISE to profile an IOT device (like a light bulb) and work with a "certainty factor" percentage accuracy.&amp;nbsp; But I would be worried if my bank used profiling to assign its ATMs to the correct VLAN or assign ACLs etc.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;What is the reason for using Radius here?&amp;nbsp; if they don't do 802.1X to gain network access then could you not do MAB auth instead?&amp;nbsp; That would mean putting all the ATM's MAC addresses into an Identity Group.&amp;nbsp; But MAB auth for an ATM sounds dodgy too.&amp;nbsp; I don't see what they use case is here.&lt;/P&gt;</description>
      <pubDate>Fri, 30 Nov 2018 11:00:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/atm-machine-profiling/m-p/3755728#M487646</guid>
      <dc:creator>Arne Bier</dc:creator>
      <dc:date>2018-11-30T11:00:12Z</dc:date>
    </item>
    <item>
      <title>Re: ATM Machine profiling</title>
      <link>https://community.cisco.com/t5/network-access-control/atm-machine-profiling/m-p/5037786#M588010</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;I am looking for the same. Kindly advise&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2024 22:40:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/atm-machine-profiling/m-p/5037786#M588010</guid>
      <dc:creator>SHABEEB KUNHIPOCKER</dc:creator>
      <dc:date>2024-03-11T22:40:15Z</dc:date>
    </item>
    <item>
      <title>Re: ATM Machine profiling</title>
      <link>https://community.cisco.com/t5/network-access-control/atm-machine-profiling/m-p/5037799#M588013</link>
      <description>&lt;P&gt;Hi Manasi,&lt;/P&gt;&lt;P&gt;The best way to handle non dot1x devices is to create a custom identity group for all atm machines. These devices do not need to be connected to be added to the group, they can be imported.&amp;nbsp;&lt;/P&gt;&lt;P&gt;This solution has been explained in detail &lt;A href="https://community.cisco.com/t5/network-access-control/handling-non-dot1x-devices/td-p/3586400" target="_self"&gt;here&lt;/A&gt; from Timothy Abbott. I believe its applicable in this case for you.&lt;/P&gt;&lt;P&gt;&lt;FONT face="times new roman,times" size="2"&gt;&lt;EM&gt;&lt;STRONG&gt;If you find this useful, please mark it helpful and Accept the Solution.&lt;/STRONG&gt;&lt;/EM&gt;&lt;/FONT&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2024 23:14:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/atm-machine-profiling/m-p/5037799#M588013</guid>
      <dc:creator>Pulkit Mittal</dc:creator>
      <dc:date>2024-03-11T23:14:49Z</dc:date>
    </item>
    <item>
      <title>Re: ATM Machine profiling</title>
      <link>https://community.cisco.com/t5/network-access-control/atm-machine-profiling/m-p/5037800#M588014</link>
      <description>&lt;P&gt;Hi Shabeeb,&lt;/P&gt;&lt;P&gt;It's answered, follow the same approach.&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Pulkit&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2024 23:18:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/atm-machine-profiling/m-p/5037800#M588014</guid>
      <dc:creator>Pulkit Mittal</dc:creator>
      <dc:date>2024-03-11T23:18:58Z</dc:date>
    </item>
    <item>
      <title>Re: ATM Machine profiling</title>
      <link>https://community.cisco.com/t5/network-access-control/atm-machine-profiling/m-p/5037803#M588015</link>
      <description>&lt;P&gt;As&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/158532"&gt;@Arne Bier&lt;/a&gt;&amp;nbsp;inferred in his previous response, you are not likely to get much detail from Profiling of an ATM endpoint. From my experience, most ATMs are built on generic platforms (like old Windows OS), so they would not provide any unique attributes.&lt;/P&gt;
&lt;P&gt;If you intend to pursue the Profiling route, you would need to determine what the network can glean from one of the ATM endpoints and build custom Profiling conditions/polices based on the &lt;A href="https://community.cisco.com/t5/security-knowledge-base/ise-profiling-design-guide/ta-p/3739456" target="_blank" rel="noopener"&gt;ISE Profiling Design Guide&lt;/A&gt;.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2024 23:17:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/atm-machine-profiling/m-p/5037803#M588015</guid>
      <dc:creator>Greg Gibbs</dc:creator>
      <dc:date>2024-03-11T23:17:57Z</dc:date>
    </item>
  </channel>
</rss>

