Start PuTTy or another SSH client, and log in with the admin account and password cisco12345 Because AutoSecure configured SSH on R3, you will receive a PuTTY security warning. Click Yes to Issue the command more flash:pre_autosec.cfg. What are the conten

CCNA Security All contents are Copyright © 1992 –2012 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 36 of 57 ip tcp intercept drop-mode random ip tcp intercept watch-timeout 15 ip tcp intercept connection-timeout 3600 ip tcp intercept max-incomplete low 450 ip tcp intercept max-incomplete high 550 end Apply this configuration to running-config? [yes]: ENTER Applying the config generated to running-config The name for the keys will be: R3.ccnasecurity.com The key modulus size is 1024 bits Generating 1024 bit RSA keys, keys will be non-exportable...[OK] R3 000037: Dec 19 21:18:52.495 UTC: AUTOSEC-1-MODIFIED: AutoSecure configuration has been Modified on this device Step 2: Establish an SSH connection from PC-C to R3.

a. Start PuTTy or another SSH client, and log in with the admin account and password cisco12345

created when AutoSecure was run. Enter the IP address of the R3 Fa01 interface 192.168.3.1.

b. Because AutoSecure configured SSH on R3, you will receive a PuTTY security warning. Click Yes to

connect anyway. c. Enter privileged EXEC mode, and verify the R3 configuration using the show run command. d. Issue the show flash command. Is there a file that might be related to AutoSecure, and if so what is its name and when was it created? Yes. The filename is pre_autosec.cfg. It is a backup file that was created when AutoSecure ran.

e. Issue the command more flash:pre_autosec.cfg. What are the contents of this file, and what

is its purpose? This file is a saved file that contains the R3 configuration before AutoSecure ran. f. How would you restore this file if AutoSecure did not produce the desired results? Copy this file from flash to startup-config using the command copy flash:pre_autosec.cfg start and issue the reload command to restart the router. Step 3: Contrast the AutoSecure-generated configuration of R3 with the manual configuration of R1. a. What security-related configuration changes were performed on R3 by AutoSecure that were not performed in previous sections of the lab on R1? Answers will vary but could include: AutoSecure enables AAA and creates a named authentication list local_auth. Console, AUX, and vty logins are set up for local authentication. The security authentication failure rate 10 log command was added. The tcp intercept feature was enabled, ip http server was disabled, cdp was disabled, security passwords min-length was changed from 8 to 6. Logging trap debugging was enabled. Other minor but potentially exploitable services were disabled. An enable password was created. Logging buffered and logging console critical were enabled. CCNA Security All contents are Copyright © 1992 –2012 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 37 of 57 b. What security-related configuration changes were performed in previous sections of the lab that were not performed by AutoSecure? Answers will vary but could include: Telnet access was excluded from vty transport input. Additional accounts were created. c. Identify at least five unneeded services that were locked down by AutoSecure and at least three security measures applied to each interface. Note: Some of the services listed as being disabled in the AutoSecure output above might not appear in the show running-config output because they are already disabled by default for this router and Cisco IOS version. Services disabled include: no service finger no service pad no service udp-small-servers no service tcp-small-servers no cdp run no ip bootp server no ip http server no ip finger no ip source-route no ip gratuitous-arps no ip identd For each interface, the following were disabled: no ip redirects no ip proxy-arp no ip unreachables no ip directed-broadcast no ip mask-reply Step 4: Test connectivity. Ping from PC-A on the R1 LAN to PC-C on the router R3 LAN. Were the pings successful? Yes If pings from PC-A to PC-C are not successful, troubleshoot before continuing. Task 3: Restore R1 to Its Basic Configuration To avoid confusion as to what was previously configured and what CCP Security Audit tool provides for the router configuration, start by restoring router R1 to its basic configuration. Step 1: Erase and reload the router. a. Connect to the R1 console and log in as admin. b. Enter privileged EXEC mode. c. Erase the startup config and then reload the router. Step 2: Restore the basic config. a. When the router restarts, cut and paste the basic startup config for R1 that was created and saved in Part 1 of this lab. CCNA Security All contents are Copyright © 1992 –2012 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 38 of 57 b. Test connectivity by pinging from host PC-A to R1. If the pings are not successful, troubleshoot the router and PC configurations to verify connectivity before continuing.

c. Save the running config to the startup config using the copy run start command.