3 replies
Firstly hello, welcome, thanks tech republic.
Now onto the topic at hand: Where to next?
And we're not talking at the NOS / DESKTOP level we're talking at the network infrastructure level...
Sure you don't want your users to do things they're not supposed to do
on the network and of course you put in measures to prevent / minimise
interaction in ways that are not in your acceptable use policy, (we all
have these for our networks don't we??) but at what point do you have
to say enough is enough.. if I secure this any more - it will no longer
be usable in the manner it was intended, and then once it is that
secure, what is the next thing to do?
The reason I ask this - I work in education I'm currently involved in a project that part of the outcome will be:
- Dynamic VLAN / SSID allocation via 802.1x authentication and secure token authentication (RSA KEY)
- Securing the core application/s via an encrypted Citrix session
- Moving core applications from local sites to one central access point
- Virtual Routing between VLANS --> while maintaining integrity on secure vlan section
- Intrusion detection / prevention being installed at the network edge (and in the core)
On the wireless side: users will be asigned a SSID based on the
credentials they have provided, depending upon those credentials the
SSID will apply different encryption methods and access levels....
eg. a teacher authenticates with their rsa token, 802.1x credentials
and domain credentials and are allocated to the hidden SSID 'teacher'
which uses dynamic rotating keys (changing every 2 minutes) and has
full access through the edge to the core ... with the ability to access
all VLAN's ('Teaching' 'Curriculum' 'DMZ')
while a student authenticates and receives access to the local file /
print server and access to the secure proxy server to access the
internet...and access to only the 'Curriculum' Vlan.
Now....
Given that all of the above are steps to secure the actual 'network'
itself and provides what I believe to be OVERKILL for security at least
in the education environment, there would obviously be environment's
where these levels of security are the bare minimum .... what would the
next step be?
- RSA tokens / 802.1x authentication for all students?
- Dynamic 802.1x allocation for anywhere
(eg teachers / students from ANY site can authenticate through the core and have their access available at ANY other site...) - Dynamic distributed applications based on credentials through out the entire education network?
from core to edge?
*sigh* - I just realised I've spent half an hour getting this how I
want it to read, while I should have been configuring switches and IAS
boxes to do all the things I was writing about...
back to slave pit for me.
But before I do - I would welcome comments / responses to the above.
Cheers.
EducationEmployee
Satisfaction plus today ladies and gentlemen.
I got it working and figured out something else too....
After spending 3 days trying to troubleshoot why I couldn't get a 3com
5500-EI to pass authentication requests from a windows 2000 sp4
workstation to an IAS server on windows 2003.....
Elimination and packet analysis is the key.
- eliminate the switch configuration --> it's all correct move on.
- eliminate the IAS server --> it's all correct move on.
- That leaves workstation.......
I went through every setting on the workstation that I could think of -
that and more, I tried different clients without any luck, I tried
different types of encryption still no luck, packet analysis is the
next key step. - Packet analysis....thank god for ethereal.
Well it's at the packet analysis stage that I found the answer to my
problem...after watching the packets pass from the workstation to the
switch but not hit the server, I was a little concerned - thinking the
problem must be with the switch...back to checking switch config - no
that's all fine - problem MUST be at the workstation end...-nope that's
all correct as well - .....begin frustration.
at this point in time - I start pulling apart all of the EAP packets
being sent / received by the workstation... everything seems to look ok
... except one small tiny detail....
the way windows by default sends username / domain is in this format
(using the standard windows 2000 802.1x supplicant) is like this:
Username:
Password:
Domain:
which translates to "domain/username"
all seems fine...except... both the 3com device and the IAS server want the format to be:
username@domain
so instead of entering the details as windows requests them I entered them like this:
username: username@domain
password: password
domain:
and guess what - almost like magic - authentication happens, I see
packets pass from workstation to switch to server and back again - what
a miracle...I don't know why Windows doesn't pass the information in
the way I expect it too, I don't really care - I'm happy that I now
know enough about it to make it work....
*hurrah*
Hi again all,
Just grappling with a few things today (Now that I've got the hard part
working - I have to figure out some logical / illogical way to get the
actual usable features of this setup working):
- Imaging workstations
- How do I network image a workstation across a network that
requires each port to be authenticated before I am allocated a VLAN
membership (IE - Before I can see any servers...unless I put the
imaging server on a default VLAN and have the switch drop back to
default VLAN if the port is unauthenticated) - Domain membership
- I have seperate domains that need to remain seperate and have
specific policies / user rights associated with each domain, but have
workstations that will need to logon to either domain depending on the
user.I toyed with the idea of creating a dual boot system - but I would hate
it if I was a user, student a logs on, logs off, teacher a has to reset
the machine, logon, then reset the machine before a student can use it.I'm also toying with the idea of distributing a single logon
workstation with two VMWARE sessions. One for Admin the other for
Curriculum - so rather than reboot - they just run the application....Really not sure the best way to approach this one.
- User experience
- Obviously I want this to be as easy and rewarding as possible
for the end user, since the entire network revolves around their use,
if I make it too complex the user will not enjoy or appreciate the
experience.Given that I want to make this experience as unchallenging as possible
for the end user, I'm also toying with the idea of moving all of the
'secure' data out of the current setup, securing it via an encrypted
Citrix session requiring dual factor authentication and having a single
domain at the local level with seperate OU's for the 'Admin' and
'Curriculum' segments along with dynamic VLAN's for bandwidth
management only rather than security. - Too many variables
- The more I look at all of the options - I just keep wondering what the actual outcome is going to be...
From what I've seen so far there are far more plausible ways of doing
what this project is setting out to achieve, with less effort from a
network admin, less confusion for the end user, and at the end of the
day - a much more streamlined solution.I think I need to sit down with the project team and give them some real world uses / solutions and possible outcomes....
As I said grappling with a few things --> the majority of these all
come from actual in school experience as an Admin and a User..... and I
just keep thinking - how is this all going to work.......
This discussion is closed to new replies.
Trending After Hours posts
Sort by Trending