<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Security on mattdrew.net - Matt&#39;s network blog</title>
		<link>https://mattdrew.net/tags/security/</link>
		<description>Recent content in Security on mattdrew.net - Matt&#39;s network blog</description>
		<generator>Hugo</generator>
		<language>en-US</language>
		
		
		
		
			<lastBuildDate>Wed, 03 Sep 2014 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://mattdrew.net/tags/security/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Cisco Port-Security</title>
				<link>https://mattdrew.net/posts/port-sec/</link>
				<pubDate>Wed, 03 Sep 2014 00:00:00 +0000</pubDate>
				<guid>https://mattdrew.net/posts/port-sec/</guid>
				<description>&lt;p&gt;Objective: Prevent users in sensitive environment from using switches or hubs to connect more than 2 devices to their switchport.&lt;/p&gt;&#xA;&lt;p&gt;In this example we will implement port-security and limit learned MACs on each switchport to a maximum of 2. To prevent administrative work by the network team, we will implement &amp;lsquo;inactivity aging&amp;rsquo;. In port-security, &amp;lsquo;inactivity aging&amp;rsquo; is a setting that will clear the sticky MAC after a period of time if there is no activity from that MAC address. This allows users to connect and be mobile within the office while still protecting the port and limiting numbers of devices. Here I choose to keep the port in restrict mode to prevent the port from being put in err-disable. I also want to receive log messages while limiting additional device activity.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
