Re: VLAN on Cisco Catalyst
- From: roberson@xxxxxxxxxxxx (Walter Roberson)
- Date: Mon, 11 Sep 2006 00:49:59 GMT
In article <45048148$1@xxxxxxxxxxxxxxxxx>,
Keme <KEMEsixtwonullsix@xxxxxxxx> wrote:
I am getting conflicting advice from various sources concerning VLAN
security. I have several Catalyst 2950 switches in my network
I will now set up a network
commanding higher security in the same physical space
I get some warnings about the possibility of fixing a packet header to
make traffic cross over between VLANs. Is that possible if all
switchports have the communication explicitly set? (i.e.: ports
connected to other Catalysts are set to Trunk mode, and ports towards
the client side are set to access mode.) With no ports in auto mode, I'd
think that such "trunk spoofing" would fail.
Historically, there have been attacks (on some devices) in which
a packet that unexpectedly had an 802.1Q header was allowed to hop
to the target VLAN. Most of the obvious vlan hopping attacks were
repaired by (reputable) vendors (on their managed switches) quite
a few years ago. It might, however, still be possible on some switches
by flooding the ARP table: in case of switch overload, some switches
(especially lower-end ones) might flood to *all* ports, not just to
the ports that are part of the same VLAN.
I seem to recall there was an attack demonstrated (and fixed since)
against some of the more advanced layer 2 capabilities such as
packet-in-packet encapsulation, used for "private VLAN" functions
(in which there might be multiple layers of 802.1Q tags.)
The high security nodes are mostly self sufficient (only occasional need
for network) so DoS is probably not an issue. Eavesdropping and
intrusion could be critical, though.
If the work has anything to do with the military, or anything
to do with information that has legally been classified beyond
certain levels, then there are military or legal requirements on the
security mechanisms that must be put in place, and those may
require "air gaps" or other fairly strict interconnection restrictions.
Thus, why you are doing this might make an important difference.
A lot of personnel issues (e.g., not allowing people to see other's
salary) are *not* legally considered to require that level of security,
as is also the case for a lot of standard "keep our competitors
from finding out what we are doing" commercial security. But
EU customer privacy regulations are fairly strict, so ensure that
your choices are consistant with whatever level of customer information
you are holding internally.
.
- Follow-Ups:
- Re: VLAN on Cisco Catalyst
- From: Keme
- Re: VLAN on Cisco Catalyst
- References:
- VLAN on Cisco Catalyst
- From: Keme
- VLAN on Cisco Catalyst
- Prev by Date: VLAN on Cisco Catalyst
- Next by Date: Re: VLAN on Cisco Catalyst
- Previous by thread: VLAN on Cisco Catalyst
- Next by thread: Re: VLAN on Cisco Catalyst
- Index(es):
Relevant Pages
|
|