1 / 49

Introduction To The Course Network Architecture

Introduction To The Course Network Architecture. Hervey Allen Chris Evans Phil Regnauld. September 3 - 4, 2009 Santiago, Chile. Overview. Course Architecture Diagram Introducing Your “ccTLD” How to Connect to Your Network Practice Exercises. Course Architecture.

lela
Télécharger la présentation

Introduction To The Course Network Architecture

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Introduction ToThe Course Network Architecture Hervey Allen Chris Evans Phil Regnauld September 3 - 4, 2009 Santiago, Chile

  2. Overview Course Architecture Diagram Introducing Your “ccTLD” How to Connect to Your Network Practice Exercises

  3. Course Architecture This architecture was designed to give each group of students a sample “registry” to secure, operate, and defend Each group of two students will be assigned one registry network. Each group will have a separate registry consisting of a Cisco Router, Name Server, and Network Operations Center server at a minimum Other servers and routers exist on the network to simulate an “Internet connected” registry and support course delivery All student “servers” are virtualized!

  4. Course Architecture • Connectivity • Each “ccTLD” is separated from the network by a gateway router – which is under YOUR control • Each “ccTLD” connects to the same “ISP” router which provides live Internet access (except during attack scenarios) and inter-connectivity • The ISP router also connects the instructor management servers and attack boxes • The Core Router provides Internet access and connects you to the ISP and your “ccTLD”

  5. Course Architecture Root (.) .MGMT .TLD1 .TLD2 … .TLD8 • DNS Architecture • A “Root” name server is setup on 192.168.128.20 which provides delegations to the ccTLD networks and to regular TLDs when connected live. • A “ISP” name server provides recursive services for _everyone_ on the network • Each “ccTLD” has an authoritative name server for their own networks (e.g. .TLD1)

  6. Course Architecture • Core Services • Course Support Server: 192.168.75.20 • NTP: 192.168.128.5

  7. Course Architecture

  8. Course Architecture YOU ARE HERE!

  9. Course Architecture A “ccTLD” Network

  10. Course Architecture The Core Router

  11. Course Architecture The “ISP” Router

  12. Course Architecture The Management Network

  13. Course Architecture Your Laptop Internet Access

  14. Course Architecture ccTLD Internet Connectivity

  15. Course Architecture ISP Router Backchannel Connection to ccTLD

  16. Course Architecture “External Monitoring”

  17. Course Architecture “Attack” Path

  18. Course Architecture Here’s YOUR ccTLD Network

  19. Introducing Your “ccTLD” Recursive NameServer A “Cheat Sheet” is Available on the Wiki

  20. Introducing Your “ccTLD” Root NameServer A “Cheat Sheet” is Available on the Wiki

  21. Introducing Your “ccTLD” ISP Router A “Cheat Sheet” is Available on the Wiki

  22. Introducing Your “ccTLD” Your Router A “Cheat Sheet” is Available on the Wiki

  23. Introducing Your “ccTLD” Your Auth NameServer A “Cheat Sheet” is Available on the Wiki

  24. Introducing Your “ccTLD” Your NOC A “Cheat Sheet” is Available on the Wiki

  25. Introducing Your “ccTLD” Your “Office” Workstation A “Cheat Sheet” is Available on the Wiki

  26. Connecting to Your “ccTLD” This is Great But, How Do I Use It?!

  27. Connecting to Your “ccTLD” • A Word on Programs • SSH (Secure Shell) is the primary connection protocol used in this network. You must provide a username AND a identity key to login • You can use any ssh client you are familiar with, but we have Putty available for Windows users • To view web pages on your network (e.g. network monitoring from your NOC), use any browser you are comfortable with • To view GUI programs on your network (e.g. wireshark, a packet capture program), you must redirect X11 output via a SSH connection • On Windows, this requires a X11 server; we suggest Xming • On Linux, its easy, use the –X option with ssh • Download links for Putty, XMing, and identity keys are available on the wiki…

  28. Connecting to Your “ccTLD” X – your group number, 1-8 Remember - A “Cheat Sheet” is Available on the Wiki • Connecting to Your Router • SSH as ‘tldadmin’ user to 192.168.10X.1 • Password: tldadmin! • Enable Password: tldadmin! • Example: ssh tldadmin@192.168.101.1

  29. Connecting to Your “ccTLD” X – your group number, 1-8 • Connecting to Your Router with Putty • IP Address: 192.168.101.1 • Click “Open”

  30. Connecting to Your “ccTLD” X – your group number, 1-8 • Connecting to Your Router with Putty • You will be doing this a lot! • Save connection information as a Session! • IP Address: 192.168.101.1 • Session Name: TLD-Router • Click “Save”

  31. Connecting to Your “ccTLD” X – your group number, 1-8 Remember - A “Cheat Sheet” is Available on the Wiki • Connecting to Your Nameserver • SSH as ‘tldadmin’, with tldadmin identity key to 192.168.10X.10 • Password: tldadmin! • Example: ssh –i tldadmin tldadmin@192.168.101.10

  32. Connecting to Your “ccTLD” X – your group number, 1-8 • Connecting to Your Nameserver with Putty • IP Address: 192.168.10X.10 • Enter “TLD-NS1” in Saved Sessions Box

  33. Connecting to Your “ccTLD” • Connecting to Your Nameserver with Putty • Click Connection -> SSH -> Auth • Identity File: Path to tldadmin.ppk

  34. Connecting to Your “ccTLD” • Connecting to Your Nameserver with Putty • Click Connection -> SSH -> X11 • Check “Enable X11 Forwarding” • Put Your Laptop IP Address Here • e.g. 192.168.75.101

  35. Connecting to Your “ccTLD” • Connecting to Your Nameserver with Putty • Click Connection -> Data • Enter ‘tldadmin’ for Auto-login username

  36. Connecting to Your “ccTLD” • Connecting to Your Nameserver with Putty • Click Session • Click “Save”

  37. Connecting to Your “ccTLD” • Connecting to Your Nameserver with Putty • Double Click the Session Name to Connect!

  38. Connecting to Your “ccTLD” X – your group number, 1-8 Remember - A “Cheat Sheet” is Available on the Wiki • Connecting to Your NOC • SSH as ‘tldadmin’, with tldadmin identity key to 192.168.10X.30 • Password: tldadmin! • Example: ssh –i tldadmin tldadmin@192.168.101.30

  39. Connecting to Your “ccTLD” X – your group number, 1-8 • Connecting to Your NOC with Putty • IP Address: 192.168.10X.30 • Enter “TLD-NOC” in Saved Sessions Box

  40. Connecting to Your “ccTLD” • Connecting to Your NOC with Putty • Click Connection -> SSH -> Auth • Identity File: Path to tldadmin.ppk

  41. Connecting to Your “ccTLD” • Connecting to Your NOC with Putty • Click Connection -> SSH -> X11 • Check “Enable X11 Forwarding” • Put Your Laptop IP Address Here • e.g. 192.168.75.101

  42. Connecting to Your “ccTLD” • Connecting to Your NOC with Putty • Click Connection -> Data • Enter ‘tldadmin’ for Auto-login username

  43. Connecting to Your “ccTLD” • Connecting to Your NOC with Putty • Click Session • Click “Save”

  44. Connecting to Your “ccTLD” • Connecting to Your NOC with Putty • Double Click the Session Name to Connect!

  45. Your “ccTLD” Cheat Sheet View Your Copy on the Course Wiki Usernames, Passwords, Keys, IPS, and sample command line instructions included

  46. Your “ccTLD” Configuration • Your Router Has Very Minor Security Precautions, No ACLs, and only allows SSH • Your NOC is a base installation of Ubuntu 8.10 Desktop with OpenSSH server • We’ll be adding to this as we move through the course • Your NS is a base installation of Ubuntu 8.10 Server with OpenSSH and BIND • We may make BIND configuration changes as we go

  47. Ground Rules Please respect other student’s registries – while you have the power to do so, do not change them! Please respect the underlying servers running VMWare! Please don’t make any configuration changes except those presented in class – they may break attack scenarios! Please respect the course management servers, wiki and attack boxes – they are there to assist in course delivery! Do not conduct cyber attacks on others students or the instructors!

  48. Practice Exercises EX: Intro to Course Architecture View Exercises on Wiki Login to your Nameserver by SSH Login to your NOC by SSH Run wireshark on your NOC with X11 Forwarding ** Be sure to save your SSH profiles to make connections easier – you’ll be doing a lot of this!

  49. ? questions On YOUR “ccTLD”?

More Related