11.2.4.6 Lab - Securing Network Devices
11.2.4.6 Lab - Securing Network Devices
11.2.4.6 Lab - Securing Network Devices
Lab – Securing Network Devices
Topology
Addressing Table
Objectives
Part 1: Configure Basic Device Settings
Part 2: Configure Basic Security Measures on the Router
Part 3: Configure Basic Security Measures on the Switch
Background / Scenario
It is recommended that all network devices be configured with, at least, a minimum set of best practice
security commands. This includes end user devices, servers, and network devices, such as routers and
switches.
In this lab, you will configure the network devices in the topology to accept SSH sessions for remote
management. You will also use the IOS CLI to configure common, basic best practice security measures. You
will then test the security measures to verify that they are properly implemented and working correctly.
Note: The routers used with CCNA handson labs are Cisco 1941 Integrated Services Routers (ISRs) with
Cisco IOS Release 15.2(4)M3 (universalk9 image). The switches used are Cisco Catalyst 2960s with Cisco
IOS Release 15.0(2) (lanbasek9 image). Other routers, switches, and Cisco IOS versions can be used.
Depending on the model and Cisco IOS version, the commands available and output produced might vary
from what is shown in the labs. Refer to the Router Interface Summary Table at the end of this lab for the
correct interface identifiers.
Note: Make sure that the routers and switches have been erased and have no startup configurations. If you
are unsure, contact your instructor.
Required Resources
• 1 Router (Cisco 1941 with Cisco IOS Release 15.2(4)M3 universal image or comparable)
• 1 Switch (Cisco 2960 with Cisco IOS Release 15.0(2) lanbasek9 image or comparable)
• 1 PC (Windows 7, Vista, or XP with terminal emulation program, such as Tera Term)
• Console cables to configure the Cisco IOS devices via the console ports
• Ethernet cables as shown in the topology
© 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 1 of 8
Lab – Securing Network Devices
Part 1: Configure Basic Device Settings
In Part 1, you will set up the network topology and configure basic settings, such as the interface IP
addresses, device access, and passwords on the router.
Step 1: Cable the network as shown in the topology.
Attach the devices as shown in the topology and cable as necessary.
Step 2: Initialize and reload the router and switch.
Step 3: Configure the router.
Please refer to the previous lab for help with the commands needed for SSH.
a. Console into the router and enable privileged EXEC mode.
b. Enter configuration mode.
c. Assign the name of the router as R1.
d. Disable DNS lookup.
e. Assign class as the privileged EXEC encrypted password.
f. Assign cisco as the console password and enable login.
g. Assign cisco as the vty password and enable login.
h. Encrypt the plain text passwords.
i. Create a banner that warns anyone accessing the device that unauthorized access is prohibited.
j. Configure and activate the G0/1 interface on the router using the information contained in the Addressing
Table.
k. Save the running configuration to the startup configuration file.
Step 4: Configure the switch.
a. Console into the switch and enable privileged EXEC mode.
b. Enter configuration mode.
c. Assign the name of the switch as S1.
d. Disable DNS lookup to prevent the router from attempting to translate incorrectly entered commands as
though they were hostnames.
e. Assign class as the privileged EXEC encrypted password.
f. Assign cisco as the console password and enable login.
g. Assign cisco as the vty password and enable login.
h. Encrypt the plain text passwords.
i. Create a banner that warns anyone accessing the device that unauthorized access is prohibited.
j. Configure the default SVI with the IP address information contained in the Addressing Table.
k. Save the running configuration to the startup configuration file.
Part 2: Configure Basic Security Measures on the Router
© 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 2 of 8
Lab – Securing Network Devices
Step 1: Strengthen passwords.
An administrator should ensure that passwords meet the standard guidelines for strong passwords. These
guidelines could include mixing letters, numbers, and special characters in the password and setting a
minimum length.
Note: Best practice guidelines require the use of strong passwords, such as those shown here, in a
production environment. However, the other labs in this course use the cisco and class passwords for ease in
performing the labs.
a. Change the privileged EXEC encrypted password to meet guidelines.
R1(config)# enable secret Enablep@55
b. Require that a minimum of 10 characters be used for all passwords.
R1(config)# security passwords min-length 10
Step 2: Enable SSH connections.
a. Assign the domain name as CCNAlab.com.
R1(config)# ip domain-name CCNA-lab.com
b. Create a local user database entry to use when connecting to the router via SSH. The password should
meet strong password standards, and the user should have administratorlevel access.
R1(config)# username admin privilege 15 secret Admin15p@55
c. Configure the transport input for the vty lines so that they accept SSH connections, but do not allow
Telnet connections.
R1(config)# line vty 0 4
R1(config-line)# transport input ssh
d. The vty lines should use the local user database for authentication.
R1(config-line)# login local
R1(config-line)# exit
e. Generate a RSA crypto key using a modulus of 1024 bits.
R1(config)# crypto key generate rsa modulus 1024
The name for the keys will be: R1.CCNA-lab.com
R1(config)#
*Jan 31 17:54:16.127: %SSH-5-ENABLED: SSH 1.99 has been enabled
Step 3: Secure the console and VTY lines.
a. You can set the router to log out of a connection that has been idle for a specified time. If a network
administrator was logged into a networking device and was suddenly called away, this command
automatically logs the user out after the specified time. The following commands cause the line to log out
after five minutes of inactivity.
R1(config)# line console 0
R1(config-line)# exec-timeout 5 0
© 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 3 of 8
Lab – Securing Network Devices
Step 4: Verify that all unused ports are disabled.
Router ports are disabled, by default, but it is always prudent to verify that all unused ports are in an
administratively down state. This can be quickly checked by issuing the show ip interface brief command.
Any unused ports that are not in an administratively down state should be disabled using the shutdown
command in interface configuration mode.
R1# show ip interface brief
Interface IP-Address OK? Method Status Protocol
Embedded-Service-Engine0/0 unassigned YES NVRAM administratively down down
GigabitEthernet0/0 unassigned YES NVRAM administratively down down
GigabitEthernet0/1 192.168.1.1 YES manual up up
Serial0/0/0 unassigned YES NVRAM administratively down down
Serial0/0/1 unassigned YES NVRAM administratively down down
R1#
Step 5: Verify that your security measures have been implemented correctly.
a. Use Tera Term to telnet to R1.
No
Does R1 accept the Telnet connection? ___________________________
Why or why not?
Telnet was disabled with the transport input ssh command.
____________________________________________________________________________________
b. Use Tera Term to SSH to R1.
Yes
Does R1 accept the SSH connection? __________
c. Intentionally mistype the user and password information to see if login access is blocked after two
attempts.
What happened after you failed to login the second time?
The connection to R1 was disconnected. If you attempt to reconnect within 30 seconds,
____________________________________________________________________________________
the connection will be refused.
____________________________________________________________________________________
d. From your console session on the router, issue the show login command to view the login status. In the
example below, the show login command was issued within the 30 second login blocking period and
shows that the router is in QuietMode. The router will not accept any login attempts for 14 more seconds.
R1# show login
© 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 4 of 8
Lab – Securing Network Devices
e. After the 30 seconds has expired, SSH to R1 again and login using the admin username and Admin15p
@55 for the password.
The R1 login banner.
After you successfully logged in, what was displayed? ________________________
f. Enter privileged EXEC mode and use Enablep@55 for the password.
If you mistype this password, are you disconnected from your SSH session after two failed attempts
The login block-for 30 attempts 2 within 120 command only monitors
within 120 seconds? ______________ session
Why or why not? login attempts.
____________________________________________________________________________________
g. Issue the show runningconfig command at the privileged EXEC prompt to view the security settings
you have applied.
Part 3: Configure Basic Security Measures on the Switch
Step 1: Strengthen Passwords on the switch.
Change the privileged EXEC encrypted password to meet strong password guidelines.
S1(config)# enable secret Enablep@55
Note: The security password minlength command is not available on the 2960 switch.
Step 2: Enable SSH Connections.
a. Assign the domainname as CCNAlab.com
S1(config)# ip domain-name CCNA-lab.com
b. Create a local user database entry for use when connecting to the router via SSH. The password should
meet strong password standards, and the user should have administrative level access.
S1(config)# username admin privilege 15 secret Admin15p@55
c. Configure the transport input for the vty lines to allow SSH connections but not allow Telnet connections.
S1(config)# line vty 0 15
S1(config-line)# transport input ssh
d. The vty lines should use the local user database for authentication.
S1(config-line)# login local
S1(config-line)# exit
e. Generate a RSA crypto key using a modulus of 1024 bits.
© 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 5 of 8
Lab – Securing Network Devices
Step 3: Secure the console and VTY lines.
a. Have the switch log out a line that has been idle for 10 minutes.
S1(config)# line console 0
S1(config-line)# exec-timeout 10 0
S1(config-line)# line vty 0 15
S1(config-line)# exec-timeout 10 0
S1(config-line)# exit
S1(config)#
b. To impede brute force login attempts, configure the switch to block login access for 30 seconds if there
are 2 failed attempts within 120 seconds. This timer is set especially low for the purpose of this lab.
S1(config)# login block-for 30 attempts 2 within 120
S1(config)# end
Step 4: Verify that all unused ports are disabled.
Switch ports are enabled, by default. Shut down all ports that are not in use on the switch.
a. You can verify the switch port status using the show ip interface brief command.
S1# show ip interface brief
Interface IP-Address OK? Method Status Protocol
Vlan1 192.168.1.11 YES manual up up
FastEthernet0/1 unassigned YES unset down down
FastEthernet0/2 unassigned YES unset down down
FastEthernet0/3 unassigned YES unset down down
FastEthernet0/4 unassigned YES unset down down
FastEthernet0/5 unassigned YES unset up up
FastEthernet0/6 unassigned YES unset up up
FastEthernet0/7 unassigned YES unset down down
FastEthernet0/8 unassigned YES unset down down
FastEthernet0/9 unassigned YES unset down down
FastEthernet0/10 unassigned YES unset down down
FastEthernet0/11 unassigned YES unset down down
FastEthernet0/12 unassigned YES unset down down
FastEthernet0/13 unassigned YES unset down down
FastEthernet0/14 unassigned YES unset down down
FastEthernet0/15 unassigned YES unset down down
FastEthernet0/16 unassigned YES unset down down
FastEthernet0/17 unassigned YES unset down down
FastEthernet0/18 unassigned YES unset down down
FastEthernet0/19 unassigned YES unset down down
FastEthernet0/20 unassigned YES unset down down
FastEthernet0/21 unassigned YES unset down down
FastEthernet0/22 unassigned YES unset down down
FastEthernet0/23 unassigned YES unset down down
FastEthernet0/24 unassigned YES unset down down
GigabitEthernet0/1 unassigned YES unset down down
© 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 6 of 8
Lab – Securing Network Devices
b. Use the interface range command to shut down multiple interfaces at a time.
S1(config)# interface range f0/1–4 , f0/7-24 , g0/1-2
S1(config-if-range)# shutdown
S1(config-if-range)# end
S1#
c. Verify that all inactive interfaces have been administratively shut down.
S1# show ip interface brief
Interface IP-Address OK? Method Status Protocol
Vlan1 192.168.1.11 YES manual up up
FastEthernet0/1 unassigned YES unset administratively down down
FastEthernet0/2 unassigned YES unset administratively down down
FastEthernet0/3 unassigned YES unset administratively down down
FastEthernet0/4 unassigned YES unset administratively down down
FastEthernet0/5 unassigned YES unset up up
FastEthernet0/6 unassigned YES unset up up
FastEthernet0/7 unassigned YES unset administratively down down
FastEthernet0/8 unassigned YES unset administratively down down
FastEthernet0/9 unassigned YES unset administratively down down
FastEthernet0/10 unassigned YES unset administratively down down
FastEthernet0/11 unassigned YES unset administratively down down
FastEthernet0/12 unassigned YES unset administratively down down
FastEthernet0/13 unassigned YES unset administratively down down
FastEthernet0/14 unassigned YES unset administratively down down
FastEthernet0/15 unassigned YES unset administratively down down
FastEthernet0/16 unassigned YES unset administratively down down
FastEthernet0/17 unassigned YES unset administratively down down
FastEthernet0/18 unassigned YES unset administratively down down
FastEthernet0/19 unassigned YES unset administratively down down
FastEthernet0/20 unassigned YES unset administratively down down
FastEthernet0/21 unassigned YES unset administratively down down
FastEthernet0/22 unassigned YES unset administratively down down
FastEthernet0/23 unassigned YES unset administratively down down
FastEthernet0/24 unassigned YES unset administratively down down
GigabitEthernet0/1 unassigned YES unset administratively down down
GigabitEthernet0/2 unassigned YES unset administratively down down
S1#
Step 5: Verify that your security measures have been implemented correctly.
a. Verify that Telnet has been disabled on the switch.
b. SSH to the switch and intentionally mistype the user and password information to see if login access is
blocked.
c. After the 30 seconds has expired, SSH to S1 again and log in using the admin username and Admin15p
@55 for the password.
Yes
Did the banner appear after you successfully logged in? __________
© 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 7 of 8
Lab – Securing Network Devices
d. Enter privileged EXEC mode using Enablep@55 as the password.
e. Issue the show runningconfig command at the privileged EXEC prompt to view the security settings
you have applied.
Reflection
1. The password cisco command was entered for the console and vty lines in your basic configuration in Part 1
. When is this password used after the best practice security measures have been applied?
This password will not be used any longer. Even though the password command stil appears
_______________________________________________________________________________________
in the lin sections of the running-config, this command was disabled as soon as the login local
_______________________________________________________________________________________
command was entered for those lines.
_______________________________________________________________________________________
2. Are preconfigured passwords, shorter than 10 characters, affected by the security passwords minlength
10 command?
No. The security passwords min-length command only affects passwords that are entered
_______________________________________________________________________________________
after this command is issued. Any pre-existing passwords remain in effect. If they are changed,
_______________________________________________________________________________________
they will need to be at least 10 characters long.
_______________________________________________________________________________________
Router Interface Summary Table
Router Interface Summary
© 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 8 of 8