<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Analysis and Review &#187; Cisco Clean Access</title>
	<atom:link href="http://analysisandreview.com/category/cisco/cisco-clean-access/feed/" rel="self" type="application/rss+xml" />
	<link>http://analysisandreview.com</link>
	<description>Unbiased research, analysis and review...</description>
	<lastBuildDate>Fri, 13 Aug 2010 13:29:42 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Cisco Clean Access Review</title>
		<link>http://analysisandreview.com/cisco/cisco-clean-access/cisco-clean-access-review/</link>
		<comments>http://analysisandreview.com/cisco/cisco-clean-access/cisco-clean-access-review/#comments</comments>
		<pubDate>Tue, 02 Jun 2009 13:45:13 +0000</pubDate>
		<dc:creator>Kurt</dc:creator>
				<category><![CDATA[Cisco Clean Access]]></category>

		<guid isPermaLink="false">http://analysisandreview.com/?p=388</guid>
		<description><![CDATA[How it all works 30,000 foot view Cisco Clean Access checks our users computers for Anti-Virus (Trend Micro) and Windows Patches (also check for many as well as forces sign on before access to the network can begin. Cisco Clean Access uses several applications and devices to make this all work: • Clean Access Manager ]]></description>
		<wfw:commentRss>http://analysisandreview.com/cisco/cisco-clean-access/cisco-clean-access-review/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>NAC Registry modification required</title>
		<link>http://analysisandreview.com/cisco/cisco-clean-access/nac-registry-modification-required/</link>
		<comments>http://analysisandreview.com/cisco/cisco-clean-access/nac-registry-modification-required/#comments</comments>
		<pubDate>Tue, 24 Mar 2009 19:20:00 +0000</pubDate>
		<dc:creator>Kurt</dc:creator>
				<category><![CDATA[Cisco Clean Access]]></category>

		<guid isPermaLink="false">http://analysisandreview.com/?p=356</guid>
		<description><![CDATA[In order to configure a client machine to detect when the vlan changes you must define the appropriate registry keys on the client. The following required DWORD registry keys are all located in the same HKEY_LOCAL_MACHINE\Software\Cisco\Clean Access Agent\ registry location. RetryDetection 5 PingArp 0 VlanDetectInterval 5 You&#8217;ll need to make these changes is you&#8217;re in ]]></description>
		<wfw:commentRss>http://analysisandreview.com/cisco/cisco-clean-access/nac-registry-modification-required/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Stop attacker IP at border router without an ACL</title>
		<link>http://analysisandreview.com/cisco/cisco-clean-access/stop-attacker-ip-at-border-router-without-an-acl/</link>
		<comments>http://analysisandreview.com/cisco/cisco-clean-access/stop-attacker-ip-at-border-router-without-an-acl/#comments</comments>
		<pubDate>Sun, 15 Feb 2009 04:13:27 +0000</pubDate>
		<dc:creator>Kurt</dc:creator>
				<category><![CDATA[Cisco Clean Access]]></category>

		<guid isPermaLink="false">http://analysisandreview.com/?p=305</guid>
		<description><![CDATA[ip route (attacker ip) 255.255.255.255 null0 wow was that hard? You just denied the attacker with a route statement. And to make things even better you use less processing power on your router versus using an ACL to stop the attacking IP address. example command router(config)#ip route 14.2.3.198 255.255.255.255 null0 Why does this work? You&#8217;ll ]]></description>
		<wfw:commentRss>http://analysisandreview.com/cisco/cisco-clean-access/stop-attacker-ip-at-border-router-without-an-acl/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Enable debug Cisco Clean Access Agent</title>
		<link>http://analysisandreview.com/cisco/cisco-clean-access/enable-debug-cisco-clean-access-agent/</link>
		<comments>http://analysisandreview.com/cisco/cisco-clean-access/enable-debug-cisco-clean-access-agent/#comments</comments>
		<pubDate>Wed, 07 Jan 2009 17:53:04 +0000</pubDate>
		<dc:creator>Kurt</dc:creator>
				<category><![CDATA[Cisco Clean Access]]></category>

		<guid isPermaLink="false">http://analysisandreview.com/?p=239</guid>
		<description><![CDATA[Step 1 Exit the Clean Access Agent on the client by right-clicking the taskbar icon and selecting Exit. Step 2 Edit the registry of the client by going to Start &#62; Run and typing regedit in the Open: field of the Run dialog. The Registry Editor opens. Step 3 In the Registry Editor, navigate to HKEY_CURRENT_USER\Software\Cisco\Clean Access Agent\ ]]></description>
		<wfw:commentRss>http://analysisandreview.com/cisco/cisco-clean-access/enable-debug-cisco-clean-access-agent/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Where to find your Cisco Clean Access logs</title>
		<link>http://analysisandreview.com/cisco/cisco-clean-access/cisco-clean-access-logs/</link>
		<comments>http://analysisandreview.com/cisco/cisco-clean-access/cisco-clean-access-logs/#comments</comments>
		<pubDate>Fri, 03 Oct 2008 20:12:47 +0000</pubDate>
		<dc:creator>Kurt</dc:creator>
				<category><![CDATA[Cisco Clean Access]]></category>

		<guid isPermaLink="false">http://analysisandreview.com/?p=203</guid>
		<description><![CDATA[Log into the clean access server and cd to /perfigo/logs/perfigo-redirect-log0.log.0 This is where you will find CAS logs to display recent events on your clean access deployment. There are three levels of logging ALL &#8211; all logging INFO &#8211; informational messages only SEVERE &#8211; only severe messages (default) To change the log level drive down ]]></description>
		<wfw:commentRss>http://analysisandreview.com/cisco/cisco-clean-access/cisco-clean-access-logs/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to modify the Cisco Clean Access web login page</title>
		<link>http://analysisandreview.com/cisco/cisco-clean-access/how-to-modify-the-cisco-clean-access-web-login-page/</link>
		<comments>http://analysisandreview.com/cisco/cisco-clean-access/how-to-modify-the-cisco-clean-access-web-login-page/#comments</comments>
		<pubDate>Tue, 16 Sep 2008 14:55:21 +0000</pubDate>
		<dc:creator>Kurt</dc:creator>
				<category><![CDATA[Cisco Clean Access]]></category>

		<guid isPermaLink="false">http://analysisandreview.com/?p=167</guid>
		<description><![CDATA[Cisco clean access web login page can be modified via html editing. I only want to do this to remove the Cisco Clean Access branding from the login page on the bottom left hand corner. If a Black Hat plugged into our network they would get the web auth (authentication) page from Cisco Clean Access. ]]></description>
		<wfw:commentRss>http://analysisandreview.com/cisco/cisco-clean-access/how-to-modify-the-cisco-clean-access-web-login-page/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
