Devoir À Rendre 08 06 2023

CCNA Security
Lab - CCNA Security Comprehensive Lab

Topology
© 2023 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 1 of 18
IP Addressing Table
Device Interface IP Address Subnet Mask Default Gateway Switch Port
Fa0/0 209.165.200.9 255.255.255.248 N/A ASA E0/0

R1 S0/0/0 (DCE) 10.10.10.1 255.255.255.252 N/A N/A
Loopback 1 172.20.1.1 255.255.255.0 N/A N/A
S0/0/0 10.10.10.2 255.255.255.252 N/A N/A
R2
S0/0/1 (DCE) 10.20.20.2 255.255.255.252 N/A N/A
Fa0/1 172.16.1.1 255.255.255.0 N/A S3 Fa0/5
R3
S0/0/1 10.20.20.1 255.255.255.252 N/A N/A
S1 VLAN 1 192.168.2.11 255.255.255.0 192.168.2.1 N/A
S2 VLAN 1 192.168.1.11 255.255.255.0 192.168.1.1 N/A
S3 VLAN 1 172.16.1.11 255.255.255.0 172.30.3.1 N/A
VLAN 1 (E0/1) 192.168.1.1 255.255.255.0 N/A S2 Fa0/24
ASA VLAN 2 (E0/0) 209.165.200.10 255.255.255.248 N/A R1 Fa0/0
VLAN 2 (E0/2) 192.168.2.1 255.255.255.0 N/A S1 Fa0/24
PC-A NIC 192.168.2.3 255.255.255.0 192.168.2.1 S1 Fa0/6
PC-B NIC 192.168.1.3 255.255.255.0 192.168.1.1 S2 Fa0/18
PC-C NIC 172.16.1.3 255.255.255.0 172.16.1.1 S3 Fa0/18
Objectives
Part 1: Create a Basic Technical Security Policy
Part 2: Configure Basic Device Settings
Part 3: Configure Secure Router Administrative Access
 Configure encrypted passwords and a login banner.
 Configure the EXEC timeout value on console and vty lines.
 Configure login failure rates and vty login enhancements.
 Configure Secure Shell (SSH) access and disable Telnet.
 Configure local authentication, authorization, and accounting (AAA) user authentication.
 Secure the router against login attacks, and secure the IOS image, and configuration file.
 Configure a router NTP server and router NTP clients.
 Configure router syslog reporting and a syslog server on a local host.
Part 4: Configure a Site-to-Site VPN between ISRs
 Configure an IPsec site-to-site VPN between R1 and R3 using the Cisco Configuration Professional
(CCP).
Part 5: Configure a Zone-Based Policy Firewall and Intrusion Prevention System
 Configure a Zone-Based Policy Firewall (ZBF) on an ISR using CCP.
 Configure an intrusion prevention system (IPS) on an ISR using CCP.

Part 6: Secure Network Switches
 Configure passwords and a login banner.
 Configure management VLAN access.
 Secure access ports.
 Protect against Spanning Tree Protocol (STP) attacks.
 Configure port security and disable unused ports.
Part 7: Configure ASA Basic Settings and Firewall
 Configure basic settings, passwords, date, and time.
 Configure the inside and outside VLAN interfaces.
 Configure port address translation (PAT) for the inside network.
 Configure a Dynamic Host Configuration Protocol (DHCP) server for the inside network.
 Configure administrative access via Telnet and SSH.
 Configure a static default route for the Adaptive Security Appliance (ASA).
 Configure Local AAA user authentication.
 Configure a DMZ with a static NAT and ACL.
 Verify address translation and firewall functionality.
Part 8 Configure a DMZ, Static NAT, and ACLs
Part 9: Configure ASA Clientless SSL VPN Remote Access
 Configure a remote access SSL VPN using the Cisco Adaptive Security Device Manager (ASDM).
 Verify SSL VPN access to the portal.
Background / Scenario
This comprehensive lab is divided into nine parts. The parts should be completed sequentially. In Part 1, you
will create a basic technical security policy. In Part 2, you configure the basic device settings. In Part 3, you
will secure a network router using the command-line interface (CLI) to configure various IOS features,
including AAA and SSH. In Part 4, you will configure a site-to-site VPN between R1 and R3 through the ISP
router (R2). In Part 5, you will configure a ZBF and IPS on an ISR. In Part 6, you will configure a network
switch using the CLI. In Parts 7 to 9, you will configure the ASA firewall functionality and clientless SSL VPN
remote access.
Note: The router commands and output in this lab are from a Cisco 1841 router using Cisco IOS software,
release 15.1(4)M8 (Advanced IP Services image). The switch commands and output are from Cisco WS-
C2960-24TT-L switches with Cisco IOS Release 15.0(2)SE4 (C2960-LANBASEK9-M image). Other routers,
switches, and Cisco IOS versions can be used. See the Router Interface Summary Table at the end of the lab
to determine which interface identifiers to use based on the equipment in the lab. Depending on the router, or
switch model and Cisco IOS version, the commands available and output produced might vary from what is
shown in this lab.
The ASA used with this lab is a Cisco model 5505 with an 8-port integrated switch, running OS version 8.4(2)
and the Adaptive Security Device Manager (ASDM) version 7.2(1) and comes with a Base license that allows
a maximum of three VLANs.
Note: Ensure that the routers and switches have been erased and have no startup configurations.
Required Resources
 3 Routers (Cisco 1841 with Cisco IOS Release 15.1(4)M8 Advanced IP Services image or comparable)
 3 Switches (Cisco 2960 with cryptography IOS image for SSH support – Release 15.0(2)SE4 or
comparable)
 1 ASA 5505 (OS version 8.4(2) and ASDM version 7.2(1) and Base license or comparable)
 3 PCs (Windows Vista or Windows 7 with CCP 2.5, Cisco VPN Client, latest version of Java, Internet
Explorer, and Flash Player)
 Serial and Ethernet cables as shown in the topology
 Console cables to configure Cisco networking devices
CCP Notes:
 If the PC on which CCP is installed is running Windows Vista or Windows 7, it may be necessary to right-
click on the CCP icon or menu item, and choose Run as administrator.
 In order to run CCP, it may be necessary to temporarily disable antivirus programs and O/S firewalls.
Make sure that all pop-up blockers are turned off in the browser.
Part 1: Create a Basic Technical Security Policy

In Part 1, you will create a Network Device Security Guidelines document that can serve as part of a
comprehensive network security policy. This document addresses specific router and switch security
measures and describes the security requirements to be implemented on the infrastructure equipment.
Task 1: Identify Potential Sections of a Basic Network Security Policy.

A network security policy should include several key sections that can address potential issues for users,
network access, device access, and other areas. List some key sections you think could be part of good basic
security policy.
__ Stratégie de pare-
feu ____________________________________________________________________________________
_
___ Politique de sécurité des données
__ Stratégie d’accès à
distance _______________________________________________________________________________
______
_______Sécurité des
ports________________________________________________________________________________
_______________________________________________________________________________________
Task 2: Create a “Network Equipment Security Guidelines” Document As a Supplement

to a Basic Security Policy
Step 1: Review the objectives from previous CCNA Security labs.

a. Open each of the previous labs completed from chapters 1 to 9, and review the objectives listed for each
one.
b. Copy the objectives to a separate document for use as a starting point. Focus mainly on those objectives
that involve security practices and device configuration.
Step 2: Create a “Network Device Security Guidelines” document for router and switch security.
Create a high-level list of tasks to include for network access and device security. This document should
reinforce and supplement the information presented in a basic Security Policy. It is based on the content of
previous CCNA Security labs and on the networking devices present in the course lab topology.
Note: The “Network Device Security Guidelines” document should be no more than two pages, and is the
basis for the equipment configuration in the remaining parts of the lab.
Step 3: Submit the Network Device Security Guidelines to your instructor.

Provide the “Network Device Security Guidelines” documents to your instructor for review before starting Part
2 of this lab. You can send them as e-mail attachments or put them on removable storage media, such as a
flash drive.
Part 2: Configure Basic Device Settings

Step 1: Cable the network as shown in the topology.
Attach the devices as shown in the topology diagram, and cable as necessary.
Step 2: Configure basic settings for all routers.

a. Configure hostnames as shown in the topology.
b. Configure the interface IP addresses as shown in the IP addressing table.
c. Configure a serial interface DCE clock rate of 128000 for the routers, if using routers other than those
specified with this lab.
d. Disable DNS lookup on each router.
Step 3: Configure static default routes on routers R1 and R3.

a. Configure a static default route from R1 to R2 and from R3 to R2.
b. Configure static routes from R2 to the R1 simulated LAN (Loopback 1), the R1 Fa0/0-to-ASA subnet, and
the R3 LAN.
Step 4: Configure basic settings for each switch.

a. Configure hostnames, as shown in the topology.
b. Configure the VLAN 1 management address on each switch, as shown in the IP Addressing table.
c. Configure the IP default gateway for each of the three switches.
d. Disable DNS lookup on each switch.
Step 5: Configure PC host IP settings.

Configure a static IP address, subnet mask, and default gateway for each PC, as shown in the IP Addressing
table.
Step 6: Verify connectivity between PC-C and R1 Lo1 and Fa0/0.
Step 7: Save the basic running configuration for each router and switch.
Part 3: Configure Secure Router Administrative Access

You use the CLI to configure passwords and device access restrictions.
Task 1: Configure Access Passwords on All the Routers
Step 1: Configure the enable secret password.

Use ciscoenapa55 as the enable secret password.
Step 2: Configure the console line.

Configure a console password of ciscoconpa55 and enable login. Set the exec-timeout value to log out after
15 minutes of inactivity. Prevent console messages from interrupting command entry.
Step 3: Configure the vty lines.

Configure the password for vty lines to be ciscovtypa55 and enable login. Set the exec-timeout value to log
out a session after 15 minutes of inactivity.
Task 2: Configure Settings for R1 and R3
Step 1: Configure a minimum password length of 10 characters.
Step 2: Encrypt plaintext passwords.
Step 3: 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 4: Configure the router to log login activity.

a. Configure the router to generate system logging messages for both successful and failed login attempts.
Configure the router to log every successful login and log failed login attempts after every second failed
login.
b. Issue the show login command. What additional information is displayed?
____________________________________________________________________________________
____________________________________________________________________________________
Step 5: Enable HTTP access. #####################

a. Enable the HTTP server on R1 to simulate an Internet target for later testing.
b. Enable secure HTTP server on R3 for a secure CCP access.
Step 6: Configure the local user database.

Create a local user account of Admin01 with a secret password of Admin01pa55 and a privilege level of 15,
and configure the local database to authenticate and access the HTTP sessions. ####################”
Task 3: Configure Local Authentication with AAA on R1 and R3
Step 1: Configure the local user database.

Create a local user account of Admin01 with a secret password of Admin01pa55 and a privilege level of 15.
Step 2: Enable AAA services.
Step 3: Implement AAA services using the local database.

Create the default login authentication method list using case-sensitive local authentication as the first option,
and the enable password as the backup option to use if an error occurs in relation to local authentication.
Task 4: Configure the SSH Server on R1 and R3
Step 1: Configure the domain name.

Configure a domain name of ccnasecurity.com.
Step 2: Change the vty lines to accept SSH connections only.

Specify that the router vty lines will accept only SSH connections and only using the local database.
Step 3: Generate the RSA encryption key pair.

Configure the RSA keys with 1024 as the number of modulus bits.
Step 4: Configure the SSH version.

Specify that the router accept only SSH version 2 connections.
Step 5: Configure SSH timeouts and authentication parameters.

The default SSH timeouts and authentication parameters can be altered to be more restrictive. Configure
SSH timeout to 90 seconds and the number of authentication attempts to 2.
Step 6: Verify SSH connectivity to R1 from PC-C.

Launch the SSH client on PC-C, enter the R1 S0/0/0 IP address (10.10.10.1) and log in as Admin01 with the
password Admin01pa55. If prompted by the SSH client with a security alert regarding the server’s host key,
click Yes.
Task 5: Secure against Login Attacks and Secure the IOS and Configuration File on R1
and R3
Step 1: Configure enhanced login security.

If a user fails to log in twice within a 30-second time span, then disable logins for 1 minute. Log all failed login
attempts.
Step 2: Secure the Cisco IOS image and archive a copy of the running configuration.
a. The secure boot-image command enables Cisco IOS image resilience, which hides the file from the dir
and show commands. The file cannot be viewed, copied, modified, or removed using EXEC mode
commands. (It can be viewed in ROMMON mode.)
b. The secure boot-config command takes a snapshot of the router running configuration and securely
archives it in persistent storage (flash).
Step 3: Verify that your image and configuration are secured.

a. You can use only the show secure bootset command to display the archived filename. Display the
status of configuration resilience and the primary bootset filename.
What is the name of the archived running config file and on what is the name based?
____________________________________________________________________________________
____________________________________________________________________________________
b. Save the running configuration to the startup configuration from the privileged EXEC mode prompt.
Task 6: Configure a Synchronized Time Source Using NTP

R2 will be the master NTP clock source for R1 and R3.
Step 1: Set up the NTP master using Cisco IOS commands.

R2 is the master NTP server in this lab. All other routers and switches learn the time from it, either directly or
indirectly. For this reason, you must ensure that R2 has the correct Coordinated Universal Time (UTC) set.
a. Use the show clock command to display the current time set on the router.
b. Use the clock set time command to set the time on the router.
c. Configure R2 as the NTP master using the ntp master stratum-number command in global configuration
mode. The stratum number indicates the distance from the original source. For this lab, use a stratum
number of 3 on R2. When a device learns the time from an NTP source, its stratum number becomes one
greater than the stratum number of its source.
Step 2: Configure R1 and R3 as NTP clients using the CLI.

a. R1 and R3 will become NTP clients of R2. To configure R1, use the ntp server hostname global
configuration mode command. The hostname can also be an IP address. The ntp update-calendar
command periodically updates the calendar with the NTP time.
b. Verify that R1 has made an association with R2 with the show ntp associations command. You can also
use the more verbose version of the command by adding the detail argument. It might take some time for
the NTP association to form.
c. Verify the time on R1 and R3 after they have made NTP associations with R2.
Task 7: Configure Syslog Support on R3 and PC-C
Step 1: Install the syslog server on PC-C.

a. The Tftpd32 software from jounin.net is free to download and install, and it includes a TFTP server, TFTP
client, and a syslog server and viewer. If not already installed, download Tftpd32 at
http://tftpd32.jounin.net and install it on PC-C.
b. Run the Tftpd32.exe file, click Settings, and ensure that the syslog server check box is checked. In the
SYSLOG tab, you can configure a file for saving syslog messages. Close the settings and in the main
Tftpd32 interface window, note the server interface IP address, and select the Syslog server tab to bring
it to the foreground.
Step 2: Configure R3 to log messages to the syslog server using the CLI.
a. Verify that you have connectivity between R3 and PC-C by pinging the R1 Fa0/1 interface IP address
172.16.1.3. If it is unsuccessful, troubleshoot as necessary before continuing.
b. NTP was configured in Task 2 to synchronize the time on the network. Displaying the correct time and
date in syslog messages is vital when using syslog to monitor a network. If the correct time and date of a
message is not known, it can be difficult to determine what network event caused the message.
Verify that the timestamp service for logging is enabled on the router using the show run command. Use
the service timestamps log datetime msec command if the timestamp service is not enabled.
c. Configure the syslog service on the router to send syslog messages to the syslog server.
Step 3: Configure the logging severity level on R3.

Logging traps can be set to support the logging function. A trap is a threshold that when reached, triggers a
log message. The level of logging messages can be adjusted to allow the administrator to determine what
kinds of messages are sent to the syslog server. Routers support different levels of logging. The eight levels
range from 0 (emergencies), indicating that the system is unstable, to 7 (debugging), which sends messages
that include router information.
Note: The default level for syslog is 6, informational logging. The default for console and monitor logging is 7,
debugging.
a. Use the logging trap command to set the severity level for R3 to level 4, warnings.
b. Use the show logging command to see the type and level of logging enabled.
Part 4: Configure a Zone-Based Policy Firewall and Intrusion Prevention

System
In Part 4, you will configure a ZBF and IPS on R3 using CCP. ###############################”
Task 1: Configure a ZBF on R3 Using CCP
Step 1: Access CCP and discover R3.

a. Start CCP on PC-C. In the Manage Devices window, add R3 IP address (172.16.1.1) in the first IP
address field. In the Username field, enter Admin01, and in the Password field, Admin01pa55. Ensure
that the Connect Securely check box is selected.
b. At the CCP Dashboard, click Discover to discover and connect to R3.
Step 2: Use the CCP Firewall wizard to configure ZBF.

a. On the CCP menu bar, click Configure > Security > Firewall > Firewall.
b. Select Basic Firewall and click Launch the selected task.
c. Specify Fa0/1 interface as the Inside (trusted) interface and S0/0/1 as the Outside (untrusted)
interface.
d. Click OK when the warning displays, informing you that you cannot launch CCP from the S0/0/1 interface
after the Firewall wizard completes.
e. Select Low Security, and complete the Firewall wizard.
f. Deliver the configuration to the router.
Step 3: Verify firewall functionality.

a. From PC-C, ping external router R2 interface S0/0/1 at IP address 10.20.20.2. The pings should be
successful.
b. From external router R2, ping PC-C at IP address 172.16.1.3. The pings should NOT be successful.
c. From PC-C on the R3 internal LAN, Telnet to R2 at IP address 10.20.20.2 and use password
ciscovtypa55.
d. With the Telnet session open from PC-C to R2, issue the show policy-map type inspect zone-pair
sessions command on R3 from the privileged EXEC mode prompt. Continue pressing Enter until you
see an Established Sessions section toward the end.
Task 2: Configure IPS on R3 Using CCP
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. This is the public
crypto key used by Cisco IOS IPS.
c. Verify or create the IPS directory (ipsdir) in router flash on R3. From the R3 CLI, display the content of
flash memory and check to see if the ipsdir directory exists.
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 SBA. The files must be deleted from the directory to
remove it.
d. If the ipsdir directory is not listed, create it in privileged EXEC mode, using the mkdir command.
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.
Step 2: Verify the IOS IPS signature package location and TFTP server setup.
a. Verify connectivity between R3 and PC-C, the TFTP server, using the ping command.
b. Start Tftpd32 (or other TFTP server) and set the default directory to the one with the IPS signature
package in it. Note the filename for use in the next step.
Step 3: Access CCP and discover R3 (if required).

a. Start CCP on PC-C. In the Manage Devices window, add R3 IP address (172.16.1.1) in the first IP
address field.
b. In the Username field, enter Admin01, and in the Password field, Admin01pa55. Ensure that the
Connect Securely check box is selected. Enter the same username and password for subsequent login
dialog boxes, if prompted. Click OK > Discover (on the next screen).
Step 4: Use the CCP IPS wizard to configure IPS.

NETLAB+ Users: It may be necessary to copy the text from the public key file before starting the IPS
configuration process with CCP. If you are not using NETLAB+ to perform the SBA go to Step 4a.
a. On the CCP menu bar, click Configure > Security > Intrusion Prevention > Create IPS.
b. Click Launch IPS Rule Wizard to open the Welcome to the IPS Policies Wizard window.
c. Apply the IPS rule in the inbound direction for Serial0/0/1.
d. In the Signature File and Public Key window, specify the signature file with a URL and use TFTP to
retrieve the file from PC-C. Enter the IP address of the PC-C TFTP server and the filename.
e. In the Signature File and Public Key window, enter the name of the public key file, realm-cisco.pub.
f. On PC-C, open the public key file and copy the text that is between the phrase “key-string” and the word
“quit”. In the Configure Public Key section, paste the text into the Key field.
g. In the Config Location and Category window, specify the flash:/ipsdir/ directory name as the location to
store the signature information.
h. In the Config Location and Category window > Choose Category field, select basic.
i. Click Next to display the Summary window, and click Finish.
j. On the Deliver Configuration to Device screen, click Deliver to deliver the commands to the router.
Note: Allow the signature configuration process to complete. This can take several minutes.
##################”
Part 5: Configure a Site-to-Site IPsec VPN between ISRs

In Part 5, you will use CCP to configure an IPsec VPN tunnel between R1 and R3 that passes through R2.
Task 1: Configure the Site-to-Site VPN between R1 and R3
Step 1: Use the CCP VPN wizard to configure R3.

a. On the CCP menu bar, click Configure > Security > VPN > Site-to-Site VPN.
b. Select the Create a Site to Site VPN option to configure the R3 side of the site-to-site VPN. Click
Launch the selected task.
c. Verify that Quick setup option is selected, and click Next.
Step 2: Configure basic VPN connection information settings.

a. On the VPN Connection Information screen, select R3 S0/0/1 as the interface for the connection.
b. In the Peer Identity section, specify R1 interface S0/0/0 (10.10.10.1) as the remote peer static IP
address.
c. In the Authentication section, specify the pre-shared VPN key cisco12345.
d. In the Traffic to encrypt section, specify the R1 source interface FastEthernet0/1 and the destination IP
address of the R1 Loopback 1 network (172.20.1.0/24). Click Next.
e. Click Finish on the Summary of the Configuration screen.
Step 3: Generate a mirror configuration from R3 and apply it to R1.

a. When returned to the CCP VPN Edit Site-to-Site VPN screen on R3, click Generate mirror to create the
IOS commands for application to router R1.
b. Click Save and save the generated configuration CLI commands to a text file on the desktop or flash drive
on PC-C.
c. Edit the file as necessary to remove notes and non-essential components.
d. From PC-C, SSH to R1 using SSH client. Log in to R1 using Admin01 and Admin01pa55 for the
password. The enable password on R1 is ciscoenapa55.
e. Copy the mirrored commands from the text file that you saved on PC-C to the R1 command prompt in
global configuration mode.
f. Apply the crypto map named in the configuration to the R1 S0/0/0 interface.
Task 2: Test the Site-to-Site IPsec VPN Using CCP
Step 1: On R3 (PC-C), use CCP to test the IPsec VPN tunnel between the two routers.
a. On the CCP menu bar, click Configure > Security > VPN > Site-to-Site VPN and select the Edit Site-
to-Site VPN tab.
b. In the Edit Site to Site VPN tab, select the VPN you just configured, and click Test Tunnel.
c. When the VPN Troubleshooting window displays, click Start to have CCP troubleshoot the tunnel.
d. When the CCP Warning window displays, indicating that CCP will enable router debugs and generate
some tunnel traffic, click Yes to continue.
e. In the next VPN Troubleshooting window, the IP address of the R3 Fa0/1 interface in the source network
is displayed by default (172.16.1.1). Enter the IP address of the R1 Loopback 1 interface in the
Destination Network field (172.20.1.1), and click Continue to begin the debugging process.
If the debug is successful, you should see an Information window indicating that troubleshooting was
successful and the tunnel is up.
Step 2: Ping from PC-C to the R1 Lo1 interface at 172.20.1.1 to generate some interesting traffic.
Step 3: Issue the show crypto isakmp sa command on R3 to view the security association
created.
Step 4: Issue the show crypto ipsec sa command on R1 to see how many packets have been
received from R3 and decrypted by R1.
Part 6: Secure Network Switches

Note: Not all security features in this part of the lab will be configured on all switches, although they normally
would be in a production network.
Task 1: Configure Passwords and a Login Banner on S1
Step 1: Configure the enable secret password.

Use an 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 enable login. Set the exec-timeout value to log out
after five (5) minutes of inactivity. Prevent console messages from interrupting command entry.
b. Configure a vty lines password of ciscovtypa55 and enable login. Set the exec-timeout value to log out
after five (5) minutes of inactivity.
Step 4: Configure a login warning banner.

Configure a warning to unauthorized users with a MOTD banner that says “Unauthorized access strictly
prohibited!”.
Step 5: Disable HTTP access.

HTTP access to the switch is enabled by default. To prevent HTTP access, disable the HTTP server and
HTTP secure server.
Task 2: Secure Access Ports on S1
Step 1: Disable trunking access ports that are in use.

On S1, configure port F0/6 as access mode only.
Step 2: Enable PortFast access ports that are in use.

PortFast is configured on access ports that connect to a workstation or server to enable the port to forward
traffic more quickly.
Enable PortFast on the S1 Fa0/6 access port.
Step 3: Enable BPDU guard access ports that are in use.

Enable BPDU guard on the F0/6 access port.
Task 3: Configure Port Security and Disable Unused Ports
Step 1: Configure basic port security for the S1 access port.

Shut down user access ports that are in use on S1 and enable basic default port security. This sets the
maximum MAC addresses to 1 and the violation action to shut down. Use the sticky option to allow the
secure MAC address that is dynamically learned on a port to the switch running configuration. Re-enable the
access port to which port security was applied.
Step 2: Disable unused ports on S1.

As a further security measure, disable any ports not being used on each switch.
Ports Fa0/1 and Fa0/6 are used on switch S1. Shut down the remaining Fast Ethernet ports and the two
Gigabit Ethernet ports.
Step 3: Save the running configuration to the startup configuration for each switch.
Part 7: Configure ASA Basic Settings and Firewall

Task 1: Prepare the ASA for ASDM Access
Step 1: Clear the previous ASA configuration settings.

a. Use the write erase command to remove the startup-config file from flash memory.
b. Use the reload command to restart the ASA.
Step 2: Bypass Setup Mode and configure the ASDM VLAN interfaces using the CLI.
a. When prompted to preconfigure the firewall through interactive prompts (Setup mode), respond with no.
b. Enter privileged EXEC mode. The password should be blank (no password) at this point.
c. Enter global configuration mode. Respond with no to the prompt to enable anonymous reporting.
d. The VLAN 1 logical interface will be used by PC-B to access ASDM on ASA physical interface E0/1.
Configure interface VLAN 1 and name it inside. The Security Level should be automatically set to the
highest level of 100. Specify IP address 192.168.10.1 and subnet mask 255.255.255.0.
e. Enable physical interface E0/1 and verify the E0/1 and VLAN 1 interface status. The status and protocol
for interface E0/1 and VLAN 1 should be up/up.
f. Preconfigure interface VLAN 2 and name it outside, add physical interface E0/0 to VLAN 2, and bring up
the E0/0 interface. You will assign the IP address using ASDM.
g. Test connectivity to the ASA by pinging from PC-B to ASA interface VLAN 1 IP address 192.168.1.1. The
pings should be successful.
Step 3: Configure and verify access to the ASA from the inside network. |||||||||||||||||||||||||||
a. Use the http command to configure the ASA to accept HTTPS connections and to allow access to ASDM
from any host on the inside network 192.168.10.0/24.
b. Open a browser on PC-B and test the HTTPS access to the ASA by entering https://192.168.1.1.
c. From the ASDM Welcome page, click Run ASDM. When prompted for a username and password, leave
them blank and click OK.
Task 2: Configure Basic ASA Settings Using the ASDM Startup Wizard
Step 1: Access the Configuration menu and launch the Startup wizard.
At the top left of the screen, click Configuration > Launch Startup wizard.
Step 2: Configure the hostname, domain name, and the enable password.
a. On the first Startup wizard screen, select the Modify Existing Configuration option.
b. On the Startup Wizard Step 2 screen, configure the ASA hostname CCNAS-ASA and domain name
ccnasecurity.com. Change the enable mode password from blank (no password) to ciscoenapa55.
Step 3: Configure the outside VLAN interfaces.

a. On the Startup Wizard Step 3 screen – Interface Selection, do not change the current settings; these
were previously defined using the CLI.
b. On the Startup Wizard Step 4 screen – Switch Port Allocation, verify that port Ethernet1 is in Inside VLAN
1 and that port Ethernet0 is in Outside VLAN 2.
c. On the Startup Wizard Step 5 screen – Interface IP Address Configuration, enter an Outside IP address
of 209.165.200.10 and Mask 255.255.255.248.
Step 4: Configure DHCP, address translation, and administrative access.

a. On the Startup Wizard Step 6 screen – DHCP Server, select Enable DHCP server on the Inside
Interface and specify a starting IP address of 192.168.1.5 and ending IP address of 192.168.1.30. Enter
the DNS Server 1 address of 10.3.3.3 and ccnasecurity.com for the domain name. Do NOT check the
box to enable Autoconfiguration from Interface.
b. On the Startup Wizard Step 7 screen – Address Translation (NAT/PAT), configure the ASA to Use Port
Address Translation (PAT) and select the Use the IP address of the outside interface option.
c. On the Startup Wizard Step 8 screen – Administrative Access, HTTPS/ASDM access is currently
configured for hosts on inside network 192.168.10.0/24. Add Telnet access to the ASA for the inside
network 192.168.1.0 with a subnet mask of 255.255.255.0. Add SSH access to the ASA from host
172.16.1.3 on the outside network.
d. Finish the wizard and deliver the commands to the ASA.
Note: ASDM may hang after delivering the configuration changes to the ASA. If this happens, close
ASDM and, on the PC Desktop, double-click the ASDM on 192.168.1.1 icon to restart ASDM. When
prompted, leave Username blank and enter ciscoenapa55 as the password.
Step 5: Test Telnet access to the ASA.

a. From a command prompt or GUI Telnet client on PC-B, Telnet to the ASA inside interface at IP address
192.168.1.1.
b. Log in to the ASA using the default login password of cisco. Enter privileged EXEC mode and provide the
password ciscoenapa55. Exit the Telnet session by using the quit command.
Task 3: Configuring ASA Settings From the ASDM Configuration Menu
Step 1: Set the ASA date and time.

At the Configuration > Device Setup screen, click System Time > Clock, set the time zone, current date
and time, and apply the commands to the ASA.
Step 2: Configure a static default route for the ASA.

a. At the Configuration > Device Setup screen, click Routing > Static Routes. Add a static route for the
outside interface, specify Any for the network object and a Gateway IP of 209.165.200.9 (R1 Fa0/0).
Apply the commands to the ASA.
b. On the ASDM Tools menu, select Ping, and enter the IP address of router R1 S0/0/0 (10.10.10.1). The
ping should succeed.
Step 3: Test access to an external website from PC-B.

Open a browser on PC-B and enter the IP address of the R1 S0/0/0 interface (10.10.10.1) to simulate access
to an external website. The R1 HTTP server was enabled in Part 2. You should be prompted with a user
authentication login dialog box from the R1 GUI device manger. Exit the browser.
Note: You will be unable to ping from PC-B to R1 S0/0/0, because the default ASA application inspection policy
does not permit ICMP from the internal network.
Step 4: Configure AAA for SSH client access.

a. At the Configuration > Device Management screen, click Users/AAA > User Accounts > Add. 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. Apply the command to the ASA.
b. At the Configuration > Device Management screen, click Users/AAA > AAA Access. On the
Authentication tab, require authentication for HTTP/ASDM, SSH, and Telnet connections, and specify the
LOCAL server group for each connection type. Click Apply to send the commands to the ASA.
Note: The next action you attempt within ASDM will require you to log in as admin with password
cisco123.
c. From PC-C, open an SSH client and attempt to access the ASA outside interface at 209.165.200.10. You
should be able to establish the connection. When prompted to log in, enter username admin and
password cisco123.
d. After logging in to the ASA using SSH, enter the enable command and provide the password
ciscoenapa55. Issue the show run command to display the current configuration you have created using
ASDM.
e. Connect to the ASA inside interface from a PC-B via Telnet using IP address 192.168.1.1.
Part 8: Configuring a DMZ, Static NAT, and ACLs

In Part 7, you configured address translation using PAT for the inside network. In this part, you will create a
DMZ on the ASA, configure static NAT to a DMZ server, and apply ACLs to control access to the server.
To accommodate the addition of a DMZ and a web server, you will use another address from the ISP range
assigned, 209.165.200.8/29 (.8-.15). Router R1 Fa0/0 and the ASA outside interface already use
209.165.200.9 and .10, respectively. You will use public address 209.165.200.11 and static NAT to provide
address translation access to the server.
Step 1: Configure the DMZ interface VLAN 3 on the ASA.

a. Configure DMZ VLAN 3, which is where the public access web server will reside. Assign it IP address
192.168.2.1/24, name it dmz, and assign it a security level of 70.
Note: If you are working with the ASA 5505 base license, you will see the error message shown in the
output below. The ASA 5505 Base license allows for the creation of up to three named VLAN interfaces.
However, you must disable communication between the third interface and one of the other interfaces
using the no forward command. This is not an issue if the ASA has a Security Plus license, which allows
20 named VLANs.
Because the server does not need to initiate communication with the inside users, disable forwarding to
interface VLAN 1.
b. Assign ASA physical interface E0/2 to DMZ VLAN 3 and enable the interface.
c. Display the status for all ASA interfaces using the show interface ip brief command.
d. Display the information for the Layer 3 VLAN interfaces using the show ip address command.
e. Display the VLANs and port assignments on the ASA using the show switch vlan command.
Step 2: Configure static NAT to the DMZ server using a network object.
Configure a network object named dmz-server and assign it the static IP address of the DMZ server
(192.168.2.3). While in object definition mode, use the nat command to specify that this object is used to
translate a DMZ address to an outside address using static NAT and specify a public translated address of
209.165.200.11.
Step 3: Configure an ACL to allow access to the DMZ server from the Internet.
Configure a named access list OUTSIDE-DMZ that permits any IP protocol from any external host to the
internal IP address of the DMZ server. Apply the access list to the ASA outside interface in the in direction.
Note: Unlike IOS ACLs, the ASA ACL permit statement must permit access to the internal private DMZ
address. External hosts access the server using its public static NAT address, and the ASA translates it to the
internal host IP address and applies the ACL.
You can modify this ACL to allow only services that you want to expose to external hosts, such as web
(HTTP) or file transfer (FTP).
Step 4: Test access to the DMZ server.

a. Create a loopback 0 interface on Internet router R2 representing an external host. Assign Lo0 IP address
172.30.1.1 and a mask of 255.255.255.0. Ping the DMZ server public address from R2 using the
loopback interface as the source of the ping. The pings should be successful.
b. Clear the NAT counters using the clear nat counters command.
c. Ping from PC-C to the DMZ server at the public address 209.165.200.11. The pings should be successful.
d. Issue the show nat and show xlate commands on the ASA to see the effect of the pings. Both the PAT
(inside to outside) and static NAT (dmz to outside) policies are shown.
Note: Pings from inside to outside are translated hits. Pings from outside host PC-C to the DMZ are
considered untranslated hits.
Note: The flag is “s” indicating a static translation.
e. Because the ASA inside interface (VLAN 1) is set to a security level of 100 (the highest) and the DMZ
interface (VLAN 3) is set to 70, you can also access the DMZ server from a host on the inside network.
The ASA acts like a router between the two networks. Ping the DMZ server (PC-A) internal address
(192.168.2.3) from inside network host PC-B (192.168.1.X). The pings should be successful due to the
interface security level and the fact that ICMP is being inspected on the inside interface by the global
inspection policy. The pings from PC-B to PC-A do not affect the NAT translation counts, because both
PC-B and PC-A are behind the firewall and no translation takes place.
f. The DMZ server cannot ping PC-B on the inside network, because the DMZ interface VLAN 3 has a lower
security level and the fact that, when the VLAN 3 interface was created, it was necessary to specify the
no forward command. Try to ping from the DMZ server PC-A to PC-B at IP address 192.168.1.X. The
pings should be unsuccessful.
g. Use the show run command to display the configuration for VLAN 3.
Note: An access list can be applied to the inside interface to control the type of access to be permitted or
denied to the DMZ server from inside hosts.
Part 9: Configure ASA Clientless SSL VPN Remote Access

Step 1: Start the VPN wizard.
On PC-B, on the ASDM main menu, click Wizards > VPN Wizards > Clientless SSL VPN wizard. The SSL
VPN wizard Clientless SSL VPN Connection screen displays.
Step 2: Configure the SSL VPN user interface.

On the SSL VPN Interface screen, configure VPN-Con-Prof as the Connection Profile Name, and specify
outside as the interface to which outside users will connect.
Step 3: Configure AAA user authentication.

On the User Authentication screen, click Authenticate Using the Local User Database, enter the username
VPNuser with a password of remote. Click Add to create the new user.
Step 4: Configure the VPN group policy.

On the Group Policy screen, create a new group policy named VPN-Grp-Pol.
Step 5: Configure the bookmark list.

a. From the Clientless Connections Only – Bookmark List screen, click Manage to create an HTTP server
bookmark in the bookmark list. In the Configure GUI Customization Objects window, click Add to open
the Add Bookmark List window. Name the list WebServer-XX, where XX is your initials.
b. Add a new Bookmark with Web Mail as the Bookmark Title. Enter the server destination IP address of
PC-B 192.168.1.3 (simulating a web server).
Step 6: Verify VPN access from the remote host.

a. Open the browser on PC-C and enter the login URL for the SSL VPN into the address field
(https://209.165.200.10). Use secure HTTP (HTTPS) as SSL is required to connect to the ASA.
b. The Login window should appear. Enter the previously configured username VPNuser and password
remote, and click Logon to continue.
Step 7: Access the web portal window.

After the user authenticates, the ASA SSL web portal webpage will be displayed, listing the various
bookmarks previously assigned to the profile. If the Bookmark points to a valid server IP address or hostname
that has HTTP web services installed and functional, the outside user can access the server from the ASA
portal.
Note: In this lab, the web mail server is not installed on PC-B.
Router Interface Summary Table
Router Interface Summary
Router Model Ethernet Interface #1 Ethernet Interface #2 Serial Interface #1 Serial Interface #2
1700 Fast Ethernet 0 (Fa0) Fast Ethernet 1 (Fa1) Serial 0 (S0) Serial 1 (S1)
1800 Fast Ethernet 0/0 Fast Ethernet 0/1 Serial 0/0/0 (S0/0/0) Serial 0/0/1 (S0/0/1)
(Fa0/0) (Fa0/1)
1900 Gigabit Ethernet 0/0 Gigabit Ethernet 0/1 Serial 0/0/0 (S0/0/0) Serial 0/0/1 (S0/0/1)
(G0/0) (G0/1)
(Fa0/0) (Fa0/1)
(Fa0/0) (Fa0/1)
2900 Gigabit Ethernet 0/0 Gigabit Ethernet 0/1 Serial 0/0/0 (S0/0/0) Serial 0/0/1 (S0/0/1)
(G0/0) (G0/1)
Note: To find out how the router is configured, look at the interfaces to identify the type of router and how many
interfaces the router has. There is no way to effectively list all the combinations of configurations for each router
class. This table includes identifiers for the possible combinations of Ethernet and Serial interfaces in the device.
The table does not include any other type of interface, even though a specific router may contain one. An
example of this might be an ISDN BRI interface. The string in parenthesis is the legal abbreviation that can be
used in Cisco IOS commands to represent the interface.

Devoir À Rendre 08 06 2023

Uploaded by

Copyright:

Available Formats

Devoir À Rendre 08 06 2023

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Devoir À Rendre 08 06 2023

Uploaded by

Copyright:

Available Formats

CCNA Security

Lab - CCNA Security Comprehensive Lab

Device Interface IP Address Subnet Mask Default Gateway Switch Port

Fa0/0 209.165.200.9 255.255.255.248 N/A ASA E0/0

 Configure an intrusion prevention system (IPS) on an ISR using CCP.

Part 1: Create a Basic Technical Security Policy

Task 1: Identify Potential Sections of a Basic Network Security Policy.

Task 2: Create a “Network Equipment Security Guidelines” Document As a Supplement

Step 1: Review the objectives from previous CCNA Security labs.

Step 3: Submit the Network Device Security Guidelines to your instructor.

Part 2: Configure Basic Device Settings

Step 2: Configure basic settings for all routers.

Step 3: Configure static default routes on routers R1 and R3.

Step 4: Configure basic settings for each switch.

Step 5: Configure PC host IP settings.

Step 6: Verify connectivity between PC-C and R1 Lo1 and Fa0/0.

Part 3: Configure Secure Router Administrative Access

Task 1: Configure Access Passwords on All the Routers

Step 1: Configure the enable secret password.

Step 2: Configure the console line.

Step 3: Configure the vty lines.

Task 2: Configure Settings for R1 and R3

Step 1: Configure a minimum password length of 10 characters.

Step 2: Encrypt plaintext passwords.

Step 3: Configure a login warning banner.

Step 4: Configure the router to log login activity.

Step 5: Enable HTTP access. #####################

Step 6: Configure the local user database.

Task 3: Configure Local Authentication with AAA on R1 and R3

Step 1: Configure the local user database.

Step 2: Enable AAA services.

Step 3: Implement AAA services using the local database.

Task 4: Configure the SSH Server on R1 and R3

Step 1: Configure the domain name.

Step 2: Change the vty lines to accept SSH connections only.

Step 3: Generate the RSA encryption key pair.

Step 4: Configure the SSH version.

Step 5: Configure SSH timeouts and authentication parameters.

Step 6: Verify SSH connectivity to R1 from PC-C.

Step 1: Configure enhanced login security.

Step 3: Verify that your image and configuration are secured.

Task 6: Configure a Synchronized Time Source Using NTP

Step 1: Set up the NTP master using Cisco IOS commands.

Step 2: Configure R1 and R3 as NTP clients using the CLI.

Task 7: Configure Syslog Support on R3 and PC-C

Step 1: Install the syslog server on PC-C.

Step 3: Configure the logging severity level on R3.

Part 4: Configure a Zone-Based Policy Firewall and Intrusion Prevention

Task 1: Configure a ZBF on R3 Using CCP

Step 1: Access CCP and discover R3.

Step 2: Use the CCP Firewall wizard to configure ZBF.

Step 3: Verify firewall functionality.

Task 2: Configure IPS on R3 Using CCP

Step 1: Prepare router R3 and the TFTP server.

Step 3: Access CCP and discover R3 (if required).

Step 4: Use the CCP IPS wizard to configure IPS.

Part 5: Configure a Site-to-Site IPsec VPN between ISRs

Task 1: Configure the Site-to-Site VPN between R1 and R3

Step 1: Use the CCP VPN wizard to configure R3.