From the user EXEC or privileged EXEC prompt, issue the show login command to see the current Use the login block-for command to configure a 60 second login shutdown quiet mode timer if
g. End the Telnet session with the exit command.
Task 4: Configure Enhanced Virtual Login Security on Routers R1 and R3 Step 1: Configure the router to protect against login attacks. Use the login block-for command to help prevent brute-force login attempts from a virtual connection, such as Telnet, SSH, or HTTP. This can help slow down dictionary attacks and help protect the router from a possible DoS attack.a. From the user EXEC or privileged EXEC prompt, issue the show login command to see the current
router login attack settings. R1 show login No login delay has been applied. No Quiet-Mode access list has been configured. Router NOT enabled to watch for login Attacksb. Use the login block-for command to configure a 60 second login shutdown quiet mode timer if
two failed login attempts are made within 30 seconds. R1config login block-for 60 attempts 2 within 30 c. Exit global configuration mode and issue the show login command. R1 show login Is the router enabled to watch for login attacks? Yes What is the default login delay? 1 second between successive attempts. CCNA Security All contents are Copyright © 1992 –2012 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 10 of 57 R1 show login A default login delay of 1 second is applied. No Quiet-Mode access list has been configured. Router enabled to watch for login Attacks. If more than 2 login failures occur in 30 seconds or less, logins will be disabled for 60 seconds. Router presently in Normal-Mode. Current Watch Window Time remaining: 29 seconds. Login failures for current window: 0. Total login failures: 0. Step 2: Configure the router to log login activity. a. Configure the router to generate system logging messages for both successful and failed login attempts. The following commands log every successful login and log failed login attempts after every second failed login. R1config login on-success log R1config login on-failure log every 2 R1config exit b. Issue the show login command. What additional information is displayed? All successful logins are logged. Every 2 failed logins are logged. Step 3: Test the enhanced login security login configuration. a. From PC-A, establish a Telnet session with R1. PC-A telnet 10.1.1.1 b. Attempt to log in with the wrong user ID or password two times. What message was displayed on PC- A after the second failed attempt? Connection to host lost What message was displayed on the router R1 console after the second failed login attempt? Dec 14 22:45:22.851: SEC_LOGIN-4-LOGIN_FAILED: Login failed [user: x] [Source: 192.168.1.3] [localport: 23] [Reason: Login Authentication Failed - BadUser] at 22:45:22 UTC Sun Dec 14 2008 c. From PC-A, attempt to establish another Telnet session to R1 within 60 seconds. What message was displayed on PC-A after the attempted Telnet connection? Connecting To 10.1.1.1...Could not open connection to the host, on port 23: Connect failed What message was displayed on router R1 after the attempted Telnet connection? Dec 14 22:24:48.171: SEC-6-IPACCESSLOGP: list sl_def_acl denied tcp 192.168.1.3 1068 - 0.0.0.023, 1 packet CCNA Security All contents are Copyright © 1992 –2012 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 11 of 57 d. Issue the show login command within 60 seconds. What additional information is displayed? Quiet- Mode status. Router is currently denying logins from all sources. R1 show login A default login delay of 1 seconds is applied. No Quiet-Mode access list has been configured. Router enabled to watch for login Attacks. If more than 2 login failures occur in 30 seconds or less, logins will be disabled for 60 seconds. Router presently in Quiet-Mode. Will remain in Quiet-Mode for 34 seconds. Denying logins from all sources. Task 5: Configure the SSH Server on Router R1 and R3 Using the CLI In this task, you use the CLI to configure the router to be managed securely using SSH instead of Telnet. Secure Shell SSH is a network protocol that establishes a secure terminal emulation connection to a router or other networking device. SSH encrypts all information that passes over the network link and provides authentication of the remote computer. SSH is rapidly replacing Telnet as the remote login tool of choice for network professionals. Note: For a router to support SSH, it must be configured with local authentication, AAA services, or username or password authentication. In this task, you configure an SSH username and local authentication. Step 1: Configure a domain name. Enter global configuration mode and set the domain name. R1 conf t R1config ip domain-name ccnasecurity.com Step 2: Configure a privileged user for login from the SSH client.a. Use the username command to create the user ID with the highest possible privilege level and a
Parts
» CCNA Security 1.1 Instructor Lab Manual
» Lab A: Researching Network Attacks and Security Audit Tools
» Lab A: Securing the Router for Administrative Access
» Use the username command to create the user ID with the highest possible privilege level and a
» Issue the undebug all or the no debug ntp all command to turn off debugging.
» Click OK in the Commands Delivery Status window.
» Use the show logging command to see the type and level of logging enabled.
» Save the running config to the startup config using the copy run start command.
» Lab A: Securing Administrative Access Using AAA and RADIUS
» Click Send and you should see a Send Access_Request message indicating the server at
» Clear the log on the WinRadius server by choosing Log Clear from the main menu.
» Lab A: Configuring CBAC and Zone-Based Firewalls
» Issue the show run command to review the current basic configuration on R1.
» Display the Extended ACL named autosec_firewall_acl, which is applied to S000 inbound.
» Display the Extended ACL named autosec_firewall_acl that is applied to S000 inbound.
» Click Finish to complete the Firewall wizard.
» Lab A: Configuring an Intrusion Prevention System IPS Using the CLI and CCP
» From the R1 CLI, verify that the directory is present using the dir flash: or dir flash:ipsdir
» Apply the IPS rule to an interface with the ip ips name direction command in interface
» Verify connectivity between R1 and PC-A, the TFTP server, using the ping command.
» Use the show ip ips all command to see an IPS configuration status summary. To which
» For Protocol, select tftp from the drop-down menu. Enter the IP address of the PC-C TFTP server
» Lab A: Securing Layer 2 Switches Instructor Version
» From the router R1 CLI, use the show interface command and record the MAC address of the
» Set the SPAN source interface using the monitor session command in global configuration mode.
» Lab A: Exploring Encryption Methods Instructor
» Lab A: Configuring a Site-to-Site VPN Using Cisco IOS and CCP
» Verify the IKE policy with the show crypto isakmp policy command.
» Save the running config to the startup config for R1 and R3 using the copy run start command.
» Click the Launch the selected task button to begin the CCP Site-to-Site VPN wizard.
» Lab B: Configuring a Remote Access VPN Server and Client
» In the Command Delivery Status window, click OK. How many commands are delivered? 103 with
» Lab C Optional: Configuring a Remote Access VPN Server and Client
» Lab A: Security Policy Development and Implementation
» Verify that R1 and R3 have made an association with R2 using the show ntp associations
» Choose FastEthernet 01 as the Inside Trusted interface and Serial 001 as the Outside Untrusted
» From PC-A, Telnet to R2 at IP address 10.1.1.2 using the vty line password ciscovtypass.
» If the ipsdir directory is not listed, create it.
» Secure the router running configuration and securely archive it in persistent storage flash.
» Lab A: Configuring ASA Basic Settings and Firewall Using CLI
» Display the ASA file system using the show file system command to determine what prefixes are
» Display the current running configuration using the show running-config command.
» You can configure the ASA to accept HTTPS connections using the http command. This allows
» Issue the show route command to display the ASA routing table and the static default route just
» Save the RSA keys to persistent flash memory using either the copy run start or write mem
» Lab B: Configuring ASA Basic Settings and Firewall Using ASDM
» View this Access Rule in ASDM by choosing Configuration Firewall Access Rules. It appears
» Lab C: Configuring Clientless and AnyConnect Remote Access SSL VPNs Using ASDM
» Enable HTTP access to R1 using the ip http server command in global config mode. Also set
» From the Add Bookmark List window, click Add to open the Add Bookmark window. Enter Web Mail as
» Lab D: Configuring a Site-to-Site IPsec VPN Using CCP and ASDM
» Use the reload command to restart the ASA. This will cause the ASA to come up in CLI Setup
» In the Peer Identity section, select Peer with static IP address and enter the IP address of the
Show more