1 w. owen – isecon 2003 – san diego designing labs for network courses william owen michael...

15
1 W. Owen – ISECON 2003 – San Diego Designing Labs for Network Courses William Owen Michael Black School of Computer & Information Sciences University of South Alabama

Upload: avice-stewart

Post on 29-Dec-2015

214 views

Category:

Documents


0 download

TRANSCRIPT

1W. Owen – ISECON 2003 – San Diego

Designing Labs for Network Courses

William OwenMichael Black

School of Computer & Information SciencesUniversity of South Alabama

2W. Owen – ISECON 2003 – San Diego

Background

•Complex topic

•“Hands-on” experience necessary

•More depth needed

•Curriculum standards requirements

3W. Owen – ISECON 2003 – San Diego

Design Objectives

Lab facilities must be:

• Affordable

• Maintainable

• Flexible

• Accessible

1. Affordable2. M

aintainable

3. Flexib

le

4W. Owen – ISECON 2003 – San Diego

Our Course Sequence

1. Network AdministrationHardware/software installation – Normal operations

2. Advanced Network AdministrationTrouble shooting, diagnosis, and repair

3. Network Infrastructure SystemsNetwork technologies (media, routers, switches, etc.)

4. Network Security ManagementSecure network facilities and assets

5W. Owen – ISECON 2003 – San Diego

Administration Lab Design

Requirements:

• ~ 25 students per offering

• 2 students per workstation

• Limited floor space

• Systems easily accessible to students

• Use existing equipment, if possible

6W. Owen – ISECON 2003 – San Diego

Network Cluster

• Vertical design

• Shared I/O devices

• Network switch

• Cable & cord management

Network Cluster Design Diagram

7W. Owen – ISECON 2003 – San Diego

Lab Configuration

• Lab switch for interconnectivity labs

• Rack mounted equipment

• 2 high capacity servers

• 100 Mbps minimum capability (gigabit preferred)

Admin. Lab Block Diagram

Tab

le

(30

”x7

2”)

NetworkInfrastructure

27’

18’

8W. Owen – ISECON 2003 – San Diego

Infrastructure Lab

• Rack mounted equipment

• Minimum space needed

• Wiring systems

• Limited student access

• Remote management

Infrastructure Lab Block Diagram

9W. Owen – ISECON 2003 – San Diego

Network Security Lab

• Isolated from the World

• Network equipment

• Two sets – two functions

• Protected assets

Tab

le

(30

”x7

2”)

NetworkInfrastructure

24’

18’

Attack Equipment

Atta

ck E

qu

ipm

ent

SecuredLANs

SecuredLANs

SecuredLANs

SecuredLANs

SecuredLANs

SecuredLANs

Security Lab Block Diagram

10W. Owen – ISECON 2003 – San Diego

Lab Scheduling Options

Fixed SchedulingMore potential students

Open SchedulingMatches student’s schedules

11W. Owen – ISECON 2003 – San Diego

Sample Lab Assignments

Network Administration Course•Install & Configure Hardware & Software•Monitor Operations•Inter-connectivity•Device Connectivity

Advanced Network Administration Course•Trouble shooting & debugging•Reports/Debriefs Required•Timed Labs

12W. Owen – ISECON 2003 – San Diego

Network Security Labs

• 3 Teams: Attackers, Defenders, Monitors

• 2 Weeks to build defenses

• 2 Weeks to attack the system

• Switch Roles and Repeat

• Ethics Discussions

• Isolated Environment

Capture the Flag

13W. Owen – ISECON 2003 – San Diego

Infrastructure Lab

• Installation & configuration

• Cabling & Signaling Systems (coax, cat5e, fiber, T1/T3)

• Normal Operations / Monitoring

• Trouble Shooting / Debugging

14W. Owen – ISECON 2003 – San Diego

Our Current State

15W. Owen – ISECON 2003 – San Diego

Future Work

• Complete Lab Development

• Develop Network Traffic Systems

• Develop Teaching Handouts

• Monitor Changing Network Technology