<?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: ISE for Printer Security in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-for-printer-security/m-p/3933247#M456745</link>
    <description>&lt;P&gt;Every environment is different and there is no one size fits all.&amp;nbsp; Here are some general thoughts:&lt;/P&gt;&lt;P&gt;- First thing is to try to do 802.1x if at all possible with your printers and if there is a centralized management system to push the configurations for them. You don't want to have to visit each printer to configure them manually.&lt;/P&gt;&lt;P&gt;- If you have to use MAB, you can use a static identity group for your printers called something like "Corporate_Printers".&amp;nbsp; When you find printers on the network using dynamic profiling and the printers logical profile, have someone verify it is a corporate-approved printer, and then statically assign it to the "Corporate_Printers" identity group.&amp;nbsp; Use that group in your authorization profile.&amp;nbsp; It is a little more secure than just allowing any device that is profiled as a printer.&lt;/P&gt;&lt;P&gt;- dACL will depend on your environment, what you are using for printer management, and how the users add printers on their machines.&amp;nbsp; Recommendation would be to SPAN a printer port for a while and capture the traffic.&amp;nbsp; Build your dACL from there.&amp;nbsp; And you will likely have to adjust over time based on feedback.&lt;/P&gt;</description>
    <pubDate>Tue, 01 Oct 2019 16:25:22 GMT</pubDate>
    <dc:creator>Colby LeMaire</dc:creator>
    <dc:date>2019-10-01T16:25:22Z</dc:date>
    <item>
      <title>ISE for Printer Security</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-for-printer-security/m-p/3933216#M456743</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;does anyone have any suggested configurations, ACLs, etc for securing printers, especially HP and giving network access to just their essential functions only?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;All replies rated,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks in advance!&lt;/P&gt;</description>
      <pubDate>Tue, 01 Oct 2019 15:29:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-for-printer-security/m-p/3933216#M456743</guid>
      <dc:creator>angel-moon</dc:creator>
      <dc:date>2019-10-01T15:29:02Z</dc:date>
    </item>
    <item>
      <title>Re: ISE for Printer Security</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-for-printer-security/m-p/3933221#M456744</link>
      <description>&lt;P&gt;We use MAB for printers, I send a DACL down so they can't talk on their vlan, then the firewall does the rest of the upstream access.&lt;/P&gt;</description>
      <pubDate>Tue, 01 Oct 2019 15:41:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-for-printer-security/m-p/3933221#M456744</guid>
      <dc:creator>Dustin Anderson</dc:creator>
      <dc:date>2019-10-01T15:41:00Z</dc:date>
    </item>
    <item>
      <title>Re: ISE for Printer Security</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-for-printer-security/m-p/3933247#M456745</link>
      <description>&lt;P&gt;Every environment is different and there is no one size fits all.&amp;nbsp; Here are some general thoughts:&lt;/P&gt;&lt;P&gt;- First thing is to try to do 802.1x if at all possible with your printers and if there is a centralized management system to push the configurations for them. You don't want to have to visit each printer to configure them manually.&lt;/P&gt;&lt;P&gt;- If you have to use MAB, you can use a static identity group for your printers called something like "Corporate_Printers".&amp;nbsp; When you find printers on the network using dynamic profiling and the printers logical profile, have someone verify it is a corporate-approved printer, and then statically assign it to the "Corporate_Printers" identity group.&amp;nbsp; Use that group in your authorization profile.&amp;nbsp; It is a little more secure than just allowing any device that is profiled as a printer.&lt;/P&gt;&lt;P&gt;- dACL will depend on your environment, what you are using for printer management, and how the users add printers on their machines.&amp;nbsp; Recommendation would be to SPAN a printer port for a while and capture the traffic.&amp;nbsp; Build your dACL from there.&amp;nbsp; And you will likely have to adjust over time based on feedback.&lt;/P&gt;</description>
      <pubDate>Tue, 01 Oct 2019 16:25:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-for-printer-security/m-p/3933247#M456745</guid>
      <dc:creator>Colby LeMaire</dc:creator>
      <dc:date>2019-10-01T16:25:22Z</dc:date>
    </item>
  </channel>
</rss>

