192.268 0.10

iLab 2 of 7: Security Demands

Submit your assignment to the Dropbox located on the silver tab at the top of this page.

(See the Syllabus section "Due Dates for Assignments & Exams" for due date information.)

iLAB OVERVIEW

Scenario and Summary

Below is the topology that you will be using for the Security Demands iLab.

SEC450_Topology

Image Description

iLab Configuration Image Description

The network configuration encompasses the Dallas, Chicago, Attack PC, and Public Server connecting through the same ISP router as follows:

The Dallas network is comprised of a switch connected to the Dallas perimeter router via Dallas LAN 192.168.100.0/24. The switch also creates an intranet for a Dallas client host IP address 192.168.100.10 and a Dallas Server IP address 192.168.100.11.

The Chicago network is comprised of a switch connected to the Chicago perimeter router via Chicago LAN 192.168.200.0/24. The switch also creates an intranet for a Chicago client host IP address 192.168.200.10 and a Chicago Server IP address 192.268.200.11.

The ISP Router uses RIP protocol to route the packets to the Dallas destination network 192.168.100.0/24 using serial 0/0 outbound interface. The ISP Router uses RIP protocol to route packets to the Chicago destination network 192.168.200.0/24 using serial 0/1 outbound interface.

The Dallas Router uses the IP address 200.100.10.0/24 to connect through the ISP while the Chicago Router uses the IP address 200.100.20.0/24 to connect through the ISP. The ISP Router is directly connected to Public LAN 200.100.0.0/24 via Fast Ethernet F0/0. The ISP Router is directly connected to the Attack LAN 200.100.40.0/24, using Fast Ethernet F1/0. The Public Server IP Address 200.100.0.10 is attached to the Public LAN via the ISP Switch, and the Attack PC IP address 200.100.40.99 is attached to the Attack LAN via the Attack Switch.

Press the ESC key to close the image description and return to lecture.

A small company is using the topology shown below. Minimal security measures have been implemented. Assume that the 200.100.0.0/16 network represents the Internet. The Dallas and Chicago hosts need to be protected from specific types of malicious traffic from the Internet.

In this lab, the students will examine the following objectives.

· Create ACL to meet the requirements of the security demands

· Modify existing ACL to meet additional security requirements

When you are ready to begin the iLab, open to the SEC450_W2_SecurityDemands_iLab.docx document.

Deliverables

Students will complete all tasks specified in the iLab Instructions document. As the iLab tasks are completed, students will enter CLI commands, and answer questions in the iLab Report document. This iLab Report document will be submitted to the iLab Dropbox for Week 2.

Required Dcumentation

· SEC450_ACL_Tutorial.docx from Week 1 iLab.

· Textbook (Chapter 3)

· Webliography links on Access Control List

iLAB STEP

Complete the Lab Assignment and Submit the Lab Document

Back to Top

Download and print the Week 2 iLab instructions: SEC450_W2_SecurityDemands_iLab.docx. You will also need to download, but not print, the Week 2 iLab Report document: SEC450_W2_SecurityDemands_Report.docx. Complete the iLab assignment referring to your printed Lab Assignment document. The report document file will be completed and submitted for your iLab grade. It must contain all required commands, and answered questions referenced in your Lab Instructions document. You will be submitting it to the Week 2 iLab Dropbox.

Back to Top