Re: Wireless Guest Access

[Steve Lovaas <steven.lovaas () COLOSTATE EDU>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

We solve this in two ways:

1) If the parent/potential student is visiting as part of an established
program (like orientation), then the sponsoring organization can include
a guest login as part of the materials they get at check-in.

2) For individual visitors with no sponsor ("just looking, thanks")
there are web-only kiosks in the student center that require no login,
as well as terminals in the library. No wireless, but at least they can
check their web mail.

As for the risks, we feel that we need at least some level of
accountability. If a non-login kiosk misbehaves, we can re-evaluate
offering such services. Other than that, whether it's an automated
process or a manual tracking (like a sign-in sheet at the library or a
sponsor's list of conference attendees), we need to be able to get to
the source PC/user in the case of legal entanglements.

Steve Lovaas
Colorado State

Matt Arthur wrote:
<snip>
> It sounds like most of you are doing some kind of 'sponsored' guest
> access (which is what we do for our current system), but how do parents
> and prospective students find someone to 'sponsor' them?
>
> And, do you think (assuming the technical security problems are taken
> care of) there is large political (or legal) risk in simply allowing
> folks to come in and use a non-login guest account?
>
> Thanks,
> Matt
>
> Matthew K Arthur, CISSP
> Director, NTS-Enterprise Networks
> Washington University in St. Louis
> W: 314.935.7388, F:314.935.7142


- --
==============================================================
Steven Lovaas, MSIA, CISSP
Network & Security Resource Manager
Academic Computing & Network Services
Colorado State University
970-297-3707
Steven.Lovaas () ColoState EDU
==============================================================
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFHCup2E9pSXAHWcsRAlddAJ9hS671n1W/DmhOLFDR3Mc2H3e9bACfQciR
vPJUYwdizPbvNq6FzLCaFP4=
=qRIe
-----END PGP SIGNATURE-----