<?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 Posture to check DNS and proxy settings in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/posture-to-check-dns-and-proxy-settings/m-p/3458265#M518722</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Can we check client's DNS and proxy settings with NAC agent or Anyconnect, and decide to allow the client if these settings are configured as compliant to corporate policy? If not, redirect to a page which says uncompliant DNS and proxy settings are being used.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 10 Jan 2018 06:05:00 GMT</pubDate>
    <dc:creator>ozgguler</dc:creator>
    <dc:date>2018-01-10T06:05:00Z</dc:date>
    <item>
      <title>Posture to check DNS and proxy settings</title>
      <link>https://community.cisco.com/t5/network-access-control/posture-to-check-dns-and-proxy-settings/m-p/3458265#M518722</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Can we check client's DNS and proxy settings with NAC agent or Anyconnect, and decide to allow the client if these settings are configured as compliant to corporate policy? If not, redirect to a page which says uncompliant DNS and proxy settings are being used.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 10 Jan 2018 06:05:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/posture-to-check-dns-and-proxy-settings/m-p/3458265#M518722</guid>
      <dc:creator>ozgguler</dc:creator>
      <dc:date>2018-01-10T06:05:00Z</dc:date>
    </item>
    <item>
      <title>Re: Posture to check DNS and proxy settings</title>
      <link>https://community.cisco.com/t5/network-access-control/posture-to-check-dns-and-proxy-settings/m-p/3458266#M518723</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You might be able to do this with a registry check, you would have to validate this in a lab setup&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Upon failure you could then throw up a remediation message with AnyConnect telling them they are blocked because of this&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can redirect them on non compliance to an manual noted html page in ISE 2.2 and higher stating they are non compliant however there is no way in authorization rules to say if you fail posture rule x then redirect to html page x for message x&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 10 Jan 2018 12:16:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/posture-to-check-dns-and-proxy-settings/m-p/3458266#M518723</guid>
      <dc:creator>Jason Kunst</dc:creator>
      <dc:date>2018-01-10T12:16:45Z</dc:date>
    </item>
  </channel>
</rss>

