[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Detection of Rogue Access Points
- Subject: Detection of Rogue Access Points
- From: Valdis.Kletnieks at vt.edu (Valdis.Kletnieks at vt.edu)
- Date: Mon, 15 Oct 2012 11:05:44 -0400
- In-reply-to: Your message of "Mon, 15 Oct 2012 13:11:00 +1100." <1350267060.2856.133.camel@karl>
- References: <CAC47Z9mEDndWoNUsXjUNgawifNtv4RXztLZgLZ2SLc4JTe0AGA@mail.gmail.com> <1350267060.2856.133.camel@karl>
On Mon, 15 Oct 2012 13:11:00 +1100, Karl Auer said:
> No-one has said this yet, so I will - why are people working around your
> normal network policies? This is often a sign of something lacking that
> people need in their daily work. You can often reduce this sort of
> "innocent thievery" down to a manageable minimum simply by making sure
> that people have the tools they need to work.
>
> Sometimes it's cheaper to give people what they want than to prevent
> them taking it. Maybe at least consider that as an option.
Amen to that - detecting rogue access points is one thing, but in order
to make the users stop doing it, you're going to need either a sufficiently
large carrot or a sufficiently large stick. If you don't deploy at least one,
the problem *will* keep recurring.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 865 bytes
Desc: not available
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20121015/d90b2067/attachment.bin>