CCNA Security Skills Based Challenge Lab
CCNA Security Skills Based Challenge Lab
Collin College
Lab Overview
This Skills Based Challenge Lab (SBCL) is divided into 7 parts. The parts should be completed
sequentially. In Part 1 you verify that the basic device settings have been preconfigured by the instructor.
In Part 2, you secure a network router using the CLI to configure various IOS features including AAA and
SSH. In Part 3 you configure a site-to-site VPN between R1 and R3 through the ISP router (R2). In Part 4
you configure a ZPF firewall and IPS on an ISR. Part 5 configures network switches using the CLI. In
Parts 6 and 7 you configure the ASA firewall functionality and clientless SSL VPN remote access.
Required Resources: 3 routers, 3 switches,1 ASA 5505, 3 PCs, and Serial and Ethernet cables
as shown in the topology
PC-A: Windows XP, Vista, or Windows 7 with CCP, PuTTy SSH client (Web and FTP server optional)
(flash drive optional)
PC-B: Windows XP, Vista, or Windows 7 with PuTTy SSH client and Java version 6.x or higher (ASDM
loaded on the PC is optional)
PC-C: Windows XP, Vista, or Windows 7 with CCP, PuTTy SSH client, TFTP server and IPS files. (flash
drive optional)
Collin College
IP Addressing Table
Device
R1
R2
R3
S1
S2
ASA
ASA
PC-A
PC-B
PC-C
Interface
FA0/0
S0/0/0 (DCE)
Loopback 1
S0/0/0
S0/0/1 (DCE)
Loopback 1
FA0/1
S0/0/1
VLAN 1
VLAN 1
VLAN 1 (E0/1)
VLAN 2 (E0/0)
NIC
NIC
NIC
IP Address
69.15.20.33
10.100.1.1
172.21.10.1
10.100.1.2
10.200.2.2
192.168.200.2
172.31.30.1
10.200.2.1
192.168.100.11
192.168.100.12
192.168.100.1
69.15.20.34
192.168.100.2
192.168.100.3
172.31.30.3
Subnet Mask
255.255.255.248
255.255.255.252
255.255.255.0
255.255.255.252
255.255.255.252
255.255.255.252
255.255.255.0
255.255.255.252
255.255.255.0
255.255.255.0
255.255.255.0
255.255.255.248
255.255.255.0
255.255.255.0
255.255.255.0
Default
Gateway
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
192.168.100.1
192.168.100.1
NA
NA
192.168.100.1
192.168.100.1
172.31.30.1
Objectives:
Part 1: Verify Basic Device Settings
Part 2: Configure Secure Router Administrative Access
Switch Port
ASA E0/0
N/A
N/.A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
S2 FA0/24
R1 FA0/0
S1 FA0/6
S2 FA0/18
S3 FA0/18
Collin College
Collin College
a.
b.
Collin College
Configure an ACL (ACL 120) on the R1 router to identify the interesting traffic. The
interesting traffic is all IP traffic between the two LANs (172.21.10.0/24 and 172.31.30.0/24).
Configure the ISAKMP Phase 1 properties on the R1 router. The crypto ISAKMP policy is 10.
Refer to the ISAKMP Phase 1 Policy Parameters Table for the specific details needed.
Configure the ISAKMP Phase 2 properties on the R1 router. Refer to the ISAKMP Phase 2
Policy Parameters Table for the specific details needed.
Bind the VPN-MAP crypto map to the outgoing interface.
Configure IPsec parameters on the R3 router using the same parameters as on the R1
router. Note that interesting traffic is defined as the IP traffic from the two LANs.
Save the running-config, then reload both R1 and R3 routers.
Verify the VPN configuration by conducting an FTP session with the username cisco and the
password cisco from the PC-C to the DMZ Web Svr. On the R3 router, check that the
packets are encrypted. To exit the FTP session, type quit.
Collin College
a.
Configure a Basic firewall with Fa0/1 interface as the Inside interface and S0/0/1
as the Outside interface.
b.
Use the Low Security setting, and complete the Firewall wizard.
Step 2: Verify Firewall functionality.
a.
From PC-C, ping external router R2. The pings should be successful.
b.
From external router R2, ping PC-C. The pings should NOT be successful.
If using CLI:
Step 1: Configure a ZPF Firewall on R3 using CLI.
a. Access the R3 router with username R1ADMIN, password ciscoccnas and the
enable secret password of ciscoclass.
b. On the R3 router, create the firewall zones.
Create an internal zone named BR-IN-ZONE.
Create an external zone named BR-OUT-ZONE.
c. Define a traffic class and access list.
Create an ACL (ACL 110) to permit all protocols from the 172.31.30.0/24 network to
any destination.
Create a class map using the option of class map type inspect with the match-all
keyword. Match the ACL 110 and name the class map BR-IN-CLASS-MAP.
d. Specify firewall policies.
Create a policy map named BR-IN-OUT-PMAP.
Use the BR-IN-CLASS-MAP class map.
Specify the action of inspect for this policy map.
e. Apply the firewall.
Create a pair of zones named IN-OUT-ZPAIR with the source as BR-IN-ZONE and
destination as BR-OUT-ZONE.
Specify the policy map BR-IN-OUT-PMAP for handling the traffic between the two
zones.
Assign interfaces to the appropriate security zones.
f. Verify the ZPF configuration.
The PC-C in the R3 office can ping the R2 Lo1 (192.168.200.2).
R2 Lo1 cannot ping the PC-C in the R3 office (172.31.30.3).
The PC-C in R3 office can establish an SSH connection to the R1 router with the
username SSHAccess and password ciscosshaccess. If you get the R1> prompt,
then your configuration is correct.
Task 2: Configure IPS on R3 Using CCP or CLI.
Step 1: Prepare router R3 and the TFTP server.
To configure Cisco IOS IPS 5.x, the IOS IPS signature package file and public crypto key files
must be available on the PC with the TFTP server installed. R3 uses PC-C as the TFTP server.
Check with your instructor if these files are not on the PC.
a.Verify that the IOS-Sxxx-CLI.pkg signature package file is in the default TFTP folder.
The xxx is the version number and varies depending on which file was downloaded from
Cisco.com.
b.Verify that the realm-cisco.pub.key.txt file is available and note its location on PC-C.
c.Verify or create the IPS directory, ipsdir, in router flash on R3.
Note: For router R3, the IPS signature (.xml) files in the flash:/ipsdir/ directory should have been deleted
and the directory removed prior to starting the SBCL. The files must be deleted from the directory in order
to remove it.
Note: If the ipsdir directory is listed and there are files in it, contact your instructor. This directory must be
empty before configuring IPS. If there are no files in it you may proceed to configure IPS.
Collin College
If using CCP:
Step 2: Access CCP and discover R3 (if required).
Specify Admin01 as the username and Admin01pa55 as the password.
Step 3: Use the CCP IPS wizard to configure IPS.
a.
Launch the IPS wizard and apply the IPS rule in the inbound direction for
Serial0/0/1.
b.
Specify the signature file with a URL and use TFTP to retrieve the file from PC-C.
c.
Name the public key file realm-cisco.pub.
d.
Copy the text from the public key file to the CCP IPS wizard.
e.
Specify the flash:/ipsdir/ directory name as the location to store the signature
information.
f.
Choose the basic category.
g.
Complete the wizard.
If using CLI:
Step 2: Configure an IOS IPS on the R3 Router.
a. On the R3 router, create a directory in flash named ipsdir.
b. Configure the IPS signature storage location to be flash:ipsdir.
c. Create an IPS rule named R3ips.
d. Configure the IOS IPS to use the signature categories. Retire the all signature
category and unretire the ios_ips basic category.
e. Apply the IPS rule in the inbound direction for Serial0/0/1.
f. Modify the ios_ips basic category. Unretire the echo request signature (signature
2004, subsig 0); enable the signature; modify the signature event-action to produce an
alert and to deny packets that match the signature.
g. Verify that IPS is working properly. PC-C in the internal network can R2 Lo1.
However, R2 Lo1 can not ping PC-C.
Part 5: Secure Network Switches
Task 1: Configure Passwords and a Login Banner on S1.
Step 1: Configure the enable secret password of ciscoenapa55.
Step 2: Encrypt plaintext passwords.
Step 3: Configure the console and VTY lines.
a.
Configure a console password of ciscoconpa55 and set the exec-timeout to log
out after 5 minutes of inactivity. Prevent console messages from interrupting
command entry.
b.
Configure a vty lines password of ciscovtypa55 and set the exec-timeout to log
out after 5 minutes of inactivity.
Step 4: Configure a login warning banner.
Configure a warning to unauthorized users with a message-of-the-day (MOTD)
banner that says Unauthorized access strictly prohibited and prosecuted to the
full extent of the law!.
Step 5: Disable HTTP access.
Task 2: Secure Trunk and Access Ports on S1 and S2.
Step 1: Configure trunk ports on S1 and S2.
Step 2: Change the native VLAN to 99 for the trunk ports on S1 and S2.
Step 3: Prevent the use of DTP on S1 and S2 trunk ports.
Step 4: Verify the trunking configuration on S1 and S2.
Step 5: Enable storm control for broadcasts on S1 and S2 trunk ports.
Step 6: Disable trunking on S1 access ports that are in use.
Step 7: Enable PortFast on S1 access ports that are in use.
Step 8: Enable BPDU guard on S1 access ports that are in use.
Collin College
Collin College
previously enabled so you should be prompted with a user authentication login dialog box
from the R2 GUI device manger. Exit the browser.
Step 4: Configure AAA for SSH client access.
a.
Create a new user named admin with a password of cisco123. Allow this user
Full access (ASDM, SSH, Telnet, and console) and set the privilege level to 15.
b.
Require authentication for HTTP/ASDM, SSH and Telnet connections and specify
the LOCAL server group for each connection type.
c.
From PC-C, open an SSH client such as PuTTY and attempt to access the ASA
outside interface at 69.15.20.34. You should be able to establish the connection.
Part 7: Configure ASA Clientless SSL VPN Remote Access
Step 1: Configure the SSL VPN user interface.
Configure VPN-Con-Prof as the Connection Profile Name, and specify outside as the
interface to which outside users will connect.
Step 2: Configure AAA user authentication.
Use the local user database to authenticate remote access users and create a new user
named VPNuser with a password of remote.
Step 3: Configure the VPN group policy.
Create a new group policy named VPN-Grp-Pol.
Step 4: Configure the bookmark list.
a.
Add a bookmark list and name it WebServer-XX (where XX is your initials).
b.
Add a new Bookmark with Web Mail as the Bookmark Title. Specify the server
destination IP address of PC-B 192.168.100.3 (simulating a web server).
Step 5: Verify VPN access from the remote host.
Open the browser on PC-C and enter the login URL for the SSL VPN into the address
field (https://69.15.20.34). The Logon window should appear. Enter the previously
configured user name VPNuser and password remote and click Logon to continue. The
Web Portal window should display.