<?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: New PC Imagining in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/new-pc-imagining/m-p/5035353#M587938</link>
    <description>&lt;P&gt;I know of a customer who gives their IT folks limited access to ISE to add Ethernet MAC addresses to an ISE PXEBoot Endpoint Identity Group. The access is so limited that all they see is the Context Visibility, and they only have write permission to the PXEBoot Endpoint Identity Group.&amp;nbsp; That's as close to a portal as you'll get.&lt;/P&gt;
&lt;P&gt;An ISE AuthZ rule then applies a dACL to permit any any when it sees that MAC address. You can try to make the dACL more watertight but then you must study the traffic flows carefully (DHCP/BOOTP, DNS, TFTP, etc.)&lt;/P&gt;
&lt;P&gt;That Identity Group gets purged every 24 hours. Enough time to allow someone to re-image a PC. If you got really smart about it, you could integrate your ticketing system (e.g. Service Now) to poke the MAC address into ISE via REST API.&lt;/P&gt;</description>
    <pubDate>Wed, 06 Mar 2024 20:30:23 GMT</pubDate>
    <dc:creator>Arne Bier</dc:creator>
    <dc:date>2024-03-06T20:30:23Z</dc:date>
    <item>
      <title>New PC Imagining</title>
      <link>https://community.cisco.com/t5/network-access-control/new-pc-imagining/m-p/5035286#M587936</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I have been tasked to secure the ports our helpdesk uses to imagine new machines.&amp;nbsp; They used to use a secured room to do this but they have since changed to imagine laptops at their work stations.&amp;nbsp; My first thought was to use an ACL to limit what the switchport had access to talk with.&amp;nbsp; We use ISE with MAB and after looking into this some more, could I use ISE to create a splash screen where the help desk person would have to enter their login cred's after connecting the laptop?&amp;nbsp; Or has someone found a better solution for this?&lt;/P&gt;&lt;P&gt;Thanks!!!&lt;/P&gt;</description>
      <pubDate>Wed, 06 Mar 2024 18:45:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/new-pc-imagining/m-p/5035286#M587936</guid>
      <dc:creator>Jerry10</dc:creator>
      <dc:date>2024-03-06T18:45:38Z</dc:date>
    </item>
    <item>
      <title>Re: New PC Imagining</title>
      <link>https://community.cisco.com/t5/network-access-control/new-pc-imagining/m-p/5035287#M587937</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1695630"&gt;@Jerry10&lt;/a&gt; yes, you could use Central Web Authentication (CWA) portal which uses AD for authentication.&amp;nbsp;&lt;A href="https://www.cisco.com/c/en/us/support/docs/security/identity-services-engine/113362-config-web-auth-ise-00.html" target="_blank"&gt;https://www.cisco.com/c/en/us/support/docs/security/identity-services-engine/113362-config-web-auth-ise-00.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;You could also push down a DACL to the authenticated users (post CWA) to allow the devices only enough access to image the devices.&lt;/P&gt;</description>
      <pubDate>Wed, 06 Mar 2024 18:49:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/new-pc-imagining/m-p/5035287#M587937</guid>
      <dc:creator>Rob Ingram</dc:creator>
      <dc:date>2024-03-06T18:49:55Z</dc:date>
    </item>
    <item>
      <title>Re: New PC Imagining</title>
      <link>https://community.cisco.com/t5/network-access-control/new-pc-imagining/m-p/5035353#M587938</link>
      <description>&lt;P&gt;I know of a customer who gives their IT folks limited access to ISE to add Ethernet MAC addresses to an ISE PXEBoot Endpoint Identity Group. The access is so limited that all they see is the Context Visibility, and they only have write permission to the PXEBoot Endpoint Identity Group.&amp;nbsp; That's as close to a portal as you'll get.&lt;/P&gt;
&lt;P&gt;An ISE AuthZ rule then applies a dACL to permit any any when it sees that MAC address. You can try to make the dACL more watertight but then you must study the traffic flows carefully (DHCP/BOOTP, DNS, TFTP, etc.)&lt;/P&gt;
&lt;P&gt;That Identity Group gets purged every 24 hours. Enough time to allow someone to re-image a PC. If you got really smart about it, you could integrate your ticketing system (e.g. Service Now) to poke the MAC address into ISE via REST API.&lt;/P&gt;</description>
      <pubDate>Wed, 06 Mar 2024 20:30:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/new-pc-imagining/m-p/5035353#M587938</guid>
      <dc:creator>Arne Bier</dc:creator>
      <dc:date>2024-03-06T20:30:23Z</dc:date>
    </item>
    <item>
      <title>Re: New PC Imagining</title>
      <link>https://community.cisco.com/t5/network-access-control/new-pc-imagining/m-p/5035394#M587941</link>
      <description>&lt;P&gt;See a similar discussion in the following post. It's an old discussion, but still relevant. Other options you could consider are inserting API calls into build process tree.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.cisco.com/t5/network-access-control/pc-imaging-on-nac-secured-ports/td-p/3486098" target="_blank" rel="noopener"&gt;PC Imaging on NAC secured ports&lt;/A&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 06 Mar 2024 21:37:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/new-pc-imagining/m-p/5035394#M587941</guid>
      <dc:creator>Greg Gibbs</dc:creator>
      <dc:date>2024-03-06T21:37:57Z</dc:date>
    </item>
  </channel>
</rss>

