Hindi Vidya Prachar Samiti’s

RAMNIRANJAN JHUNJHUNWALA COLLEGE OF ARTS, SCIENCE &

COMMERCE
(EMPOWERED AUTONOMOUS COLLEGE)

AFFILIATED TO
UNIVERSITY OF
MUMBAI

DEPARTMENT OF INFORMATION TECHNOLOGY

2023-2024

T.Y.B.SC. (IT) SEM VI

PAPER RJSUITp602 – Security in computing

Name - Gupta Suraj Rammurti Rekha

Roll no - 6453
 Hindi Vidya Prachar Samiti’s

Ramniranjan Jhunjhunwala College of Arts, Science &

Commerce
(Empowered Autonomous College)

Affiliated to

UNIVERSITY OF MUMBAI

This is to certify that Mr. Gupta Suraj Rammurti Rekha, Roll No. 6453
of TY BSc IT class has completed the required number of Experiment of
Practical Security in computing, in partial fulfillment of the Requirements
for the award of the degree of Bachelor of Science (Information Technology)
during the academic year 2023-2024.

College seal Sign of

Co-Ordinator
 Practical 1
Packet Tracer - Configure Cisco Routers for
Syslog, NTP, and SSH Operations

Topology:

Addressing Table

Device Interface IP Address Subnet Mask Default

Gateway

R1 G0/1 192.168.1.1 255.255.255.0 N/A

S0/0/0 (DCE) 10.1.1.1 255.255.255.252 N/A

R2 S0/0/0 10.1.1.2 255.255.255.252 N/A

S0/0/1 (DCE) 10.2.2.2 255.255.255.252 N/A

R3 G0/1 192.168.3.1 255.255.255.0 N/A

S0/0/1 10.2.2.1 255.255.255.252 N/A

PC-A NIC 192.168.1.5 255.255.255.0 192.168.1.1

PC-B NIC 192.168.1.6 255.255.255.0 192.168.1.1

PC-C NIC 192.168.3.5 255.255.255.0 192.168.3.1

Objectives
• Configure OSPF MD5 authentication.
• Configure NTP.
• Configure routers to log messages to the syslog server.
• Configure R3 to support SSH connections.

Background / Scenario
In this activity, you will configure OSPF MD5 authentication for secure routing updates.
The NTP Server is the master NTP server in this activity. You will configure authentication
on the NTP server and the routers. You will configure the routers to allow the software clock
to be synchronised by NTP to the time server. Also, you will configure the routers to
periodically update the hardware clock with the time learned from NTP.
The Syslog Server will provide message logging in this activity. You will configure the
routers to identify the remote host (Syslog server) that will receive logging messages.
You will need to configure timestamp service for logging on the routers. Displaying the
correct time and date in Syslog messages are vital when using Syslog to monitor a network.
You will configure R3 to be managed securely using SSH instead of Telnet. The servers have
been preconfigured for NTP and Syslog services respectively. NTP will not require
authentication. The routers have been pre-configured with the following passwords:
• Enable password: ciscoenpa55 // password is set to access the EXEC mode of routers
Pre-configured the routers with the following passwords 1st for Enabling, 2nd for
Virtual Terminal, 3rd for Console .

R1:

R2:

R3:
Virtual teletype (VTY) is a command line interface (CLI) that allows users to access a
device's control plane.VTY is a virtual port that provides access to Telnet or SSH.
For example, Cisco hardware supports a maximum of 16 line virtual interfaces, i.e.
(0,1,2,3,…,15).The abstract “0 - 4” means that the device can allow 5 simultaneous virtual
connections which may be Telnet or SSH.
• Password for vty lines: ciscovtypa55 // vty is used for remote access of a device's CLI
R3:

//login enables password authentication

R2:

R1:

For Console:
R1:

R2:
R3:

Do the OSPF on all the router put all of them under area 0[1(unique processid), 0(area
id)]
R1:

R2:

R3:
Part 1 :Configure OSPF MD5 Authentication

Step 1: Test connectivity.

All devices should be able to ping all other IP addresses.

Step 2: Configure OSPF MD5 authentication for all routers in area 0

OSPF MD5 authentication is a type of authentication that uses the MD5 algorithm to
compute a hash value from the contents of an OSPF packet. It also uses the MD5 algorithm
to compute a password.
OSPF MD5 authentication is more secure than simple text authentication. It ensures that
unauthorised IP resources cannot inject OSPF routing messages into the network without
detection. This helps to ensure the integrity of the routing tables in the OSPF routing
network.

Do same for all three routers i.e R1 , R2 , R3

R1(config) #router ospf 1
R1(config-router) #area 0 authentication message-digest

Step 3: Configure the MD5 key for all the routers in area 0.

Configure an MD5 key on the serial interfaces on R1, R2 and R3. Use the password
MD5pa55 for key 1.

//(key id)
//ip…..key (command to configure an ospf md5 authentication key)
//md5(type)

Step 4: Verify configurations.

Part 2: Configure NTP
Network Time Protocol (NTP) is a protocol that synchronises the clocks of network devices,
like routers, switches, and firewalls, with a central source clock.
The Network Time Protocol (NTP) is a networking protocol for clock synchronisation
between computer systems over packet-switched, variable-latency data networks.
Step 1: Enable NTP authentication on PC-A.
a. On PC-A, click NTP under the Services tab to verify NTP service is enabled.
b. To configure NTP authentication, click Enable under Authentication. Use key 1 and
password NTPpa55 for authentication.
Step 2: Configure R1, R2, and R3 as NTP clients.

R1(config)# ntp server 192.168.1.5

R2(config)# ntp server 192.168.1.5
R3(config)# ntp server 192.168.1.5

Verify client configuration using the command show ntp status.

Step 3: Configure routers to update hardware clock.

Configure R1, R2, and R3 to periodically update the hardware clock with the time learned
from NTP.
//synchronises h/w clock with time obtained from NTP server

Verify that the hardware clock was updated using the command show clock

Step 4: Configure NTP authentication on the routers

Configure NTP authentication on R1, R2, and R3 using key 1 and password NTPpa55.
R1(config)# ntp authenticate
R1(config)# ntp trusted-key 1
R1(config)# ntp authentication-key 1 md5 NTPpa55

//enables ntp authentication(exchange of ntp packets between device and ntp server)
//1(authentication key trusted for authenticating NTP packets)
//1(authentication key)//md5(authentication method)
Step 5: Configure routers to timestamp log messages.
Do same for all three routers i.e R1 , R2 , R3
Configure timestamp service for logging on the routers
//ser……log(enable timestamp for log msg)
//datetime-timestamp includes date nd time
//msec(date nd time + milliseconds)
Part 3: Configure Routers to Log Messages to the Syslog Server

Step 1: Configure the routers to identify the remote host (Syslog Server) that will
receive logging messages.

Step 2: Verify logging configuration.

Use the command show logging to verify logging has been enabled.

Step 3: Examine logs of the Syslog Server.

From the Services tab of the Syslog Server’s dialogue box, select the Syslog services
button. Observe the logging messages received from the routers.
Part 4: Configure R3 to support SSH Connections
SSH stands for Secure Shell, or Secure Socket Shell. It's a cryptographic protocol that allows
two computers to communicate and share data over an insecure network, such as the internet.
It's used to log in to a remote server to execute commands and data transfer from one
machine to another.
The port is used for Secure Shell (SSH) communication and allows remote administration
access to the VM.
Step 1: Configure a domain name

//ip…..name(sets domain name used by device to generate SSH)

Step 2: Configure users for login to SSH server on R3.

Create a user ID of SSHadmin with the highest possible privilege level and a secret password
of ciscosshpa55.

R3(config)# username SSHadmin privilege 15 secret ciscosshpa55

//15(for admins)

Step 3: Configure the incoming vty lines on R3.

Use the local user accounts for mandatory login and validation. Accept only SSH connections
//device should use local username and password
//SSH is the only allowed transport protocol for incoming connection on VTY line
Step 4: Erase existing key pairs on R3.

Any existing RSA key pairs should be erased on the router.

Step 5: Generate the RSA encryption key pair for R3.

The router uses the RSA key pair for authentication and encryption of transmitted SSH data.
Configure the RSA keys with a modulus of 1024. The default is 512, and the range is from
360 to 2048.

Step 6: Verify the SSH configuration.

Use the show ip ssh command to see the current settings. Verify that the authentication
timeout and retries are at their default values of 120 and 3.

Step 7: Configure SSH timeouts and authentication parameters.

The default SSH timeouts and authentication parameters can be altered to be more restrictive.
Set the timeout to 90 seconds, the number of authentication retries to 2, and the version to 2.
Step 8: Attempt to connect to R3 via Telnet from PC-C.

Open the Desktop of PC-C. Select the Command Prompt icon. From PC-C, enter the
command to connect to R3 via Telnet.

This connection should fail because R3 has been configured to accept only SSH connections
on the virtual terminal lines.

Step 9: Connect to R3 using SSH on PC-C.

Open the Desktop of PC-C. Select the Command Prompt icon. From PC-C, enter the
command to connect to R3 via SSH. When prompted for the password, enter the password
configured for the administrator ciscosshpa55.

ssh –l SSHadmin 192.168.3.1

//ssh(initiates)//-l(specify username)
Step 10: Connect to R3 using SSH on R2.

To troubleshoot and maintain R3, the administrator at the ISP must use SSH to access the
router CLI. From the CLI of R2, enter the command to connect to R3 via SSH version 2
using the SSHadmin user account.
When prompted for the password, enter the password configured for the administrator:
ciscosshpa55.

R2# ssh –v 2 –l SSHadmin 10.2.2.1

//-v(verbose mode)//2(ssh version)

 Practical 2
Configure AAA Authentication on Cisco Routers

Topology

Addressing Table

Device Interface IP Address Subnet Mask Default

Gateway

R1 G0/1 192.168.1.1 255.255.255.0 N/A

S0/0/0 (DCE) 10.1.1.2 255.255.255.252 N/A

R2 G0/0 192.168.2.1 255.255.255.0 N/A

S0/0/0 10.1.1.1 255.255.255.252 N/A

S0/0/1 (DCE) 10.2.2.1 255.255.255.252 N/A

R3 G0/1 192.168.3.1 255.255.255.0 N/A

S0/0/1 10.2.2.2 255.255.255.252 N/A

TACACS+ NIC 192.168.2.2 255.255.255.0 192.168.2.1

Server

RADIUS Server NIC 192.168.3.2 255.255.255.0 192.168.3.1

PC-A NIC 192.168.1.3 255.255.255.0 192.168.1.1

PC-B NIC 192.168.2.3 255.255.255.0 192.168.2.1

PC-C NIC 192.168.3.3 255.255.255.0 192.168.3.1

Objectives
• Configure a local user account on R1 and configure authenticate on the console and vty
lines using local AAA.
• Verify local AAA authentication from the R1 console and the PC-A client.
• Configure server-based AAA authentication using TACACS+.
• Verify server-based AAA authentication from the PC-B client.
• Configure server-based AAA authentication using RADIUS.
• Verify server-based AAA authentication from the PC-C client.

Background / Scenario
The network topology shows routers R1, R2 and R3. Currently, all administrative security is
based on knowledge of the enabled secret password. Your task is to configure and test local
and server-based AAA solutions.
You will create a local user account and configure local AAA on router R1 to test the console
and vty logins.
o User account: Admin1 and password admin1pa55
You will then configure router R2 to support server-based authentication using the TACACS+
protocol. The TACACS+ server has been pre-configured with the following:
o Client: R2 using the keyword tacacspa55
o User account: Admin2 and password admin2pa55
Finally, you will configure router R3 to support server-based authentication using the
RADIUS protocol. The RADIUS server has been pre-configured with the following:
o Client: R3 using the keyword radiuspa55
o User account: Admin3 and password admin3pa55
The routers have also been pre-configured with the following:
o Enable secret password: ciscoenpa55
o OSPF routing protocol with MD5 authentication using password: MD5pa55

Pre-configured the routers with enable secret password

Do same for all three routers i.e R1 , R2 , R3

Do the OSPF on all the router put all of them under area 0
Part 1: Configure Local AAA Authentication for Console Access on R1
AAA stands for Authentication, Authorization, and Accounting. It's a security framework that
controls and tracks user access to computer networks. AAA is a requirement for network
security.
AAA has three parts:
Authentication: Uses a username and password to identify a user. It grants or denies access
based on a user's account and password.
Authorization: Determines what level of access a user has on the network.
Accounting: Tracks a user's activity while accessing network resources. This includes the
amount of time spent in the network, the services accessed, and the amount of data
transferred. Accounting data is used for trend analysis, capacity planning, and billing

Step 1: Test connectivity.

● Ping from PC-A to PC-B.
● Ping from PC-A to PC-C.
● Ping from PC-B to PC-C.

Step 2: Configure a local username on R1.

Configure a username of Admin1 with a secret password of admin1pa55.

R1(config)# username Admin1 secret admin1pa55

Step 3: Configure local AAA authentication for console access on R1.

Enable AAA on R1 and configure AAA authentication for the console login to use the local
database.

R1(config)# aaa new-model //enable aaa authentication

R1(config)# aaa authentication login default local

Step 4: Configure the line console to use the defined AAA authentication method.

Enable AAA on R1 and configure AAA authentication for the console login to use the default
method list.

R1(config)# line console 0 //li…0(apply authentication on console 0)

R1(config-line)# login authentication default //login….default(should use login
authentication using local username and password)

Step 5: Verify the AAA authentication method.

Verify the user EXEC login using the local database.

Part 2: Configure Local AAA Authentication for vty Lines on R1

Step 1: Configure domain name and crypto key for use with SSH.

a. Use ccnasecurity.com as the domain name on R1.

b. Create an RSA crypto key using 1024 bits.
How many bits in the modulus [512]: 1024

R1(config)# ip domain-name ccnasecurity.com

R1(config)# crypto key generate rsa

Step 2: Configure a named list AAA authentication method for the vty lines on R1.

Configure a named list called SSH-LOGIN to authenticate logins using local AAA.

R1(config)# aaa authentication login SSH-LOGIN local //a…in(aaa authentication should be

used for login)
//SSH…IN(name of list)

Step 3: Configure the vty lines to use the defined AAA authentication method.

Configure the vty lines to use the named AAA method and only allow SSH for remote
access.
//S…IN(named list used for login attempts)
Step 4: Verify the AAA authentication method.

Verify the SSH configuration SSH to R1 from the command prompt of PC-A..

C:\> ssh -l Admin1 192.168.1.1

Password: admin1pa55
Part 3: Configure Server-Based AAA Authentication Using TACACS+ on R2
TACACS+ (Terminal Access Controller Access Control Server) is a security protocol used in
the AAA framework to provide centralized authentication for users who want to access a
network. It's an improved version of the original TACACS protocol, which was developed by
Cisco.
TACACS+ uses TCP port 49 and is a TCP-based access control protocol. It allows a device
to forward a user's username and password to an authentication server to determine whether
access can be allowed. It also provides authorization and accounting services.

Step 1: Configure a backup local database entry called Admin.

For backup purposes, configure a local username of Admin2 and a secret password of
admin2pa55.

R2(config)# username Admin2 secret admin2pa55

Step 2: Verify the TACACS+ Server configuration.

Click the TACACS+ Server. On the Services tab, click AAA. Notice that there is a Network
configuration entry for R2 and a User Setup entry for Admin2.
Step 3: Configure the TACACS+ server specifics on R2.

Configure the AAA TACACS server IP address and secret key on R2.

Note: The commands tacacs-server host and tacacs-server key are deprecated. Currently,
Packet Tracer does not support the new command tacacs server.

Step 4: Configure AAA login authentication for console access on R2.

Enable AAA on R2 and configure all logins to authenticate using the AAA TACACS+ server.
If it is not available, then use the local database.
Step 5: Configure the line console to use the defined AAA authentication method.

Configure AAA authentication for console login to use the default AAA authentication
method.

Step 6: Verify the AAA authentication method.

Verify the user EXEC login using the AAA TACACS+ server.
Part 4: Configure Server-Based AAA Authentication Using RADIUS on R3

Step 1: Configure a backup local database entry called Admin.

For backup purposes, configure a local username of Admin3 and a secret password of
admin3pa55.

Step 2: Verify the RADIUS Server configuration.

Click the RADIUS Server. On the Services tab, click AAA. Notice that there is a Network
configuration entry for R3 and a User Setup entry for Admin3.

Step 3: Configure the RADIUS server specifics on R3.

Configure the AAA RADIUS server IP address and secret key on R3.
Note: The commands radius-server host and radius-server key are deprecated. Currently
Packet Tracer does not support the new command radius server.

Step 4: Configure AAA login authentication for console access on R3.

Enable AAA on R3 and configure all logins to authenticate using the AAA RADIUS server.
If it is not available, then use the local database.

Step 5: Configure the line console to use the defined AAA authentication method.

Configure AAA authentication for console login to use the default AAA authentication
method.

Step 6: Verify the AAA authentication method.

Verify the user EXEC login using the AAA RADIUS server.
 Practical 3
Configuring Extended ACLs - Scenario 1

Topology

Addressing Table
Device Interface IP Address Subnet Mask Default
Gateway

R1 G0/0 172.22.34.65 255.255.255.224 N/A

G0/1 172.22.34.97 255.255.255.240 N/A

G0/2 172.22.34.1 255.255.255.192 N/A

Server NIC 172.22.34.62 255.255.255.192 172.22.34.1

PC1 NIC 172.22.34.66 255.255.255.224 172.22.34.65

PC2 NIC 172.22.34.98 255.255.255.240 172.22.34.97

Objectives
Part 1: Configure, Apply and Verify an Extended Numbered ACL
Part 2: Configure, Apply and Verify an Extended Named ACL

Background / Scenario
Two employees need access to services provided by the server. PC1 needs only FTP access
while PC2
needs only web access. Both computers are able to ping the server, but not each other.

Part 1: Configure, Apply and Verify an Extended Numbered ACL

Extended Access Control Lists (ACLs) act as the gatekeeper of your network. They either
permit or deny traffic based on protocol, port number, source, destination, and time range.
The range of customization is massive.
Step 1: Configure an ACL to permit FTP and ICMP.

a. From global configuration mode on R1, enter the following command to determine
the first valid number for an extended access list.

b. Add 100 to the command, followed by a question mark.

c. To permit FTP traffic, enter a permit, followed by a question mark.

d. This ACL permits FTP and ICMP. ICMP is listed above, but FTP is not, because
FTP uses TCP. Therefore,enter tcp to further refine the ACL help.
e. Notice that we could filter just for PC1 by using the host keyword or we could allow
any host. In this case, any device is allowed that has an address belonging to the
172.22.34.64/27 network.

f. Calculate the wildcard mask determining the binary opposite of a subnet mask.
11111111.11111111.11111111.11100000 = 255.255.255.224
00000000.00000000.00000000.00011111 = 0.0.0.31

g. Enter the wildcard mask.

R1(config)# access-list 100 permit tcp 172.22.34.64 0.0.0.31 ?
h. Configure the destination address. In this scenario, we are filtering traffic for a single
destination, which isserver. Enter the host keyword followed by the server’s IP address.
R1(config)# access-list 100 permit tcp 172.22.34.64 0.0.0.31 host 172.22.34.62 ?

i. Notice that one of the options is <cr> (carriage return). In other words, you can press
Enter and the statement would permit all TCP traffic. However, we are only permitting
FTP traffic; therefore, enter the eq keyword, followed by a question mark to display the
available options. Then, enter ftp and press Enter.
where,
access-list 100 specifies the extended ACL with numeric identifier.
permit allow.
tcp IP protocol to match. (commonly used for FTP)
172.22.34.66, the source IP address.
0.0.0.31 is the wildcard mask.
host is the keyword followed by the server’s IP address(destination) i.e, 172.22.34.62.
eq ftp specifies traffic equal to FTP having port number 21.
Then press Enter.
j. Create a second access list statement to permit ICMP (ping, etc.) traffic from PC1 to
Server. Note that the access list number remains the same and no particular type of
ICMP traffic needs to be specified.

k. All other traffic is denied, by default.

Step 2: Apply the ACL on the correct interface to filter traffic.

From R1’s perspective, the traffic that ACL 100 applies to is inbound from the network
connected to Gigabit Ethernet 0/0 interface. Enter interface configuration mode and
apply the ACL.

Step 3: Verify the ACL implementation.

a. Ping from PC1 to Server. If the pings are unsuccessful, verify the IP addresses before
continuing.
b. FTP from PC1 to Server. The username and password are both cisco.
pc> ftp 172.22.34.62

d. Ping from PC1 to PC2. The destination host should be unreachable, because the
traffic was not explicitly permitted.
Part 2: Configure, Apply and Verify an Extended Named ACL

Step 1: Configure an ACL to permit HTTP access and ICMP.

a. Named ACLs start with the ip keyword. From the global configuration mode of R1,
enter the following command, followed by a question mark.

b. You can configure named standard and extended ACLs. This access list filters both
source and destination IP addresses; therefore, it must be extended. Enter
HTTP_ONLY as the name. (For Packet Tracer scoring, the name is case-sensitive.)

c. The prompt changes. You are now in extended named ACL configuration mode. All
devices on the PC2 LAN need TCP access. Enter the network.

d. An alternative way to calculate a wildcard is to subtract the subnet mask from.

255.255.255.255 - 255.255.255.240 = 0. 0. 0. 15
R1(config-ext-nacl)# permit tcp 172.22.34.96 0.0.0.15 ?

e. Finish the statement by specifying the server address as you did in Part 1 and filtering
www traffic.
f. Create a second access list statement to permit ICMP (ping, etc.) traffic from PC2 to
Server. Note: The prompt remains the same and a specific type of ICMP traffic does not
need to be specified.

where,
ip acces-list extended signals that subsequent lines of configuration will define rules and
criteria.
Enter HTTP_ONLY as the name.
permit tcp because all devices on the PC2 LAN need TCP access. Enter the source address,
i.e,172.22.34.98 followed by a wildcard mask 0.0.0.15.
172.22.34.62 is the server address as you did in Part 1 and filtering www traffic with port
number 80.

Step 2: Apply the ACL on the correct interface to filter traffic.

From R1’s perspective, the traffic that access list HTTP_ONLY applies to is inbound
from the network
connected to Gigabit Ethernet 0/1 interface. Enter the interface configuration mode and
apply the ACL.

Step 3: Verify the ACL implementation.

a. Ping from PC2 to Server. The ping should be successful, if the ping is unsuccessful,
verify the IP addresses before continuing.

b. FTP from PC2 to Server. The connection should fail.

c. Open the web browser on PC2 and enter the IP address of Server as the URL. The
connection should be successful.
 Practical 4

Topology :

Addressing Table :
Device Interface IP Address Subnet Mask Default Gateway

R1 G0/1 192.168.1.100 255.255.255.0 N/A

S0/0/0 (DCE) 1.1.1.1 255.255.255.252 N/A

S0/0/0 1.1.1.2 255.255.255.0 N/A

R2 S0/0/1 (DCE) 2.2.2.1 255.255.255.252 N/A

G0/1 192.168.17.100 255.255.255.0 N/A

R3 G0/1 192.168.19.100 255.255.255.0 N/A

S0/0/1 2.2.2.2 255.255.255.252 N/A

PC-A NIC 192.168.1.1 255.255.255.0 192.168.1.100

PC-B NIC 192.168.17.1 255.255.255.0 192.168.1.100

PC-C NIC 192.168.19.2 255.255.255.0 192.168.17.100

Server NIC 192.168.19.1 255.255.255.0 192.168.19.100

Laptop NIC 192.168.1.5 255.255.255.0 192.168.19.100

Objectives
● Blocking Web browser communication from PC-A to Server.
● Blocking FTP connection from PC-B to Server.
● Blocking ICMP connection from laptop to Server.

Part 1: RIP Routing

Part 2: Denying access

1. Blocking Web browser communication from PC-A to Server.

R2(config)#access-list 100 deny tcp host 192.168.1.1 host 192.168.19.1 eq www

2. Blocking FTP connection from PC-B to Server.

R2(config)#access-list 100 deny tcp host 192.168.17.1 host 192.168.19.1 eq ftp

3. Blocking ICMP connection from laptop to Server.

R2(config)#access-list 100 deny icmp host 192.168.1.5 host 192.168.19.1

4. All other IP traffic is denied, by default.So use the command

R2(config)#access-list 100 permit ip any any

From R1’s perspective, the traffic that access list HTTP_ONLY applies to
is inbound from the network connected to Serial0/0/1 interface. Enter
the interface configuration mode and apply the ACL.

R2(config)#interface Serial0/0/1
R2(config-if)#ip access-group 100 out
R2(config-if)#exit

To Check if the following conditions have been implemented or not use

the command.
Part 3: Checking Results :

1) Blocking Web browser communication from PC-A to Server.

2) Blocking FTP connection from PC-B to server.

3) Blocked ICMP Connection from Laptop to server.

 Practical 5
Configure IP ACLs to Mitigate Attacks

Topology:

Addressing Table:
Device Interface IP Address Subnet Mask Default Switch
Gateway Port

R1 G0/1 192.168.1.1 255.255.255.0 N/A S1 F0/5

S0/0/0 (DCE) 10.1.1.1 255.255.255.252 N/A N/A

R2 S0/0/0 10.1.1.2 255.255.255.252 N/A N/A

S0/0/1 (DCE) 10.2.2.2 255.255.255.252 N/A N/A

Lo0 192.168.2.1 255.255.255.0 N/A N/A

R3 G0/1 192.168.3.1 255.255.255.0 N/A S3 F0/5

S0/0/1 10.2.2.1 255.255.255.252 N/A N/A

PC-A NIC 192.168.1.3 255.255.255.0 192.168.1.1 S1 F0/6

PC-C NIC 192.168.3.3 255.255.255.0 192.168.3.1 S3

F0/18

Objectives
• Verify connectivity among devices before firewall configuration.
• Use ACLs to ensure remote access to the routers is available only from management station
PC-C.
• Configure ACLs on R1 and R3 to mitigate attacks.
• Verify ACL functionality.

Background/Scenario
Access to routers R1, R2, and R3 should only be permitted from PC-C, the management
station. PC-C is also used for connectivity testing to PC-A, which is a server providing DNS,
SMTP, FTP, and HTTPS services.
Standard operating procedure is to apply ACLs on edge routers to mitigate common threats
based on source and destination IP address. In this activity, you will create ACLs on edge
routers R1 and R3 to achieve this goal. You will then verify ACL functionality from internal
and external hosts.

The routers have been pre-configured with the following:

The routers have been pre-configured with the following:

Same For All 3 Routers

Same For All 3 Routers

SSH login username and password:
SSHadmin/ciscosshpa55

Same For All 3 Routers

Only on R2 set loopback address

Update routing table

Static Routing
R1
R1

R2
R3

Part 1: Verify basic network connectivity.

Step 1: From PC-A, verify connectivity to PC-C and R2.

a. From the command prompt, ping PC-C (192.168.3.3).

b. From the command prompt, establish an SSH session to R2 Lo0 interface
(192.168.2.1) using username SSHadmin and password ciscosshpa55. When finished,
exit the SSH session.

SERVER(PC-A)> ssh -l SSHadmin 192.168.2.1

Step 2: From PC-C, verify connectivity to PC-A and R2.

a. From the command prompt, ping PC-A (192.168.1.3).

b. From the command prompt, establish an SSH session to R2 Lo0 interface
(192.168.2.1) using username SSHadmin and password ciscosshpa55. Close the SSH
session when finished.

(PC-C)> ssh -l SSHadmin 192.168.2.1

c. Open a web browser to the PC-A server (192.168.1.3) to display the web page. Close
the browser when done.
Part 2: Secure Access to Routers

Step 1: Configure ACL 10 to block all remote access to the routers except from PC-C.

Use the access-list command to create a numbered IP ACL on R1, R2, and R3.

R1(config)# access-list 10 permit host 192.168.3.3

R2(config)# access-list 10 permit host 192.168.3.3
R3(config)# access-list 10 permit host 192.168.3.3

Same for All 3 Router

Step 2: Apply ACL 10 to ingress traffic on the VTY lines. Use the access-class
command to apply the access list to incoming traffic on the VTY lines.

R1(config)# line vty 0 4

R1(config-line)# access-class 10 in
R2(config-line)# access-class 10 in
R3(config-line)# access-class 10 in

Same for All 3 Router

Step 3: Verify exclusive access from management station PC-C.

a. Establish an SSH session to 192.168.2.1 from PC-C (should be successful).

PC> ssh -l SSHadmin 192.168.2.1

Password : ciscosshpa55

b. Establish an SSH session to 192.168.2.1 from PC-A (should fail).

Part 3: Create a Numbered IP ACL 120 on R1

Create an IP ACL numbered 120 with the following rules:

● Permit any outside host to access DNS, SMTP, and FTP services on server PC-A.
● Deny any outside host access to HTTPS services on PC-A.
● Permit PC-C to access R1 via SSH.

Note: Check Results will not show a correct configuration for ACL 120 until you modify it
in Part 4.

Step 1: Verify that PC-C can access the PC-A via HTTPS using the web browser.
Be sure to disable HTTP and enable HTTPS on server PC-A.
Step 2: Configure ACL 120 to specifically permit and deny the specified traffic. Use the
access-list command to create a numbered IP ACL.

R1(config)# access-list 120 permit udp any host 192.168.1.3 eq domain

R1(config)# access-list 120 permit tcp any host 192.168.1.3 eq smtp
R1(config)# access-list 120 permit tcp any host 192.168.1.3 eq ftp
R1(config)# access-list 120 deny tcp any host 192.168.1.3 eq 443
R1(config)# access-list 120 permit tcp host 192.168.3.3 host 10.1.1.1 eq 22

Step 3: Apply the ACL to interface S0/0/0. Use the ip access-group command to apply
the access list to incoming traffic on interface S0/0/0.

R1(config)# interface s0/0/0

R1(config-if)# ip access-group 120 in

Step 4: Verify that PC-C cannot access PC-A via HTTPS using the web browser.

Part 4: Modify an Existing ACL on R1

Permit ICMP echo replies and destination unreachable messages from the outside network
(relative to R1). Deny all other incoming ICMP packets.

Step 1: Verify that PC-A cannot successfully ping the loopback interface on R2.

PC> ping 192.168.2.1

Step 2: Make any necessary changes to ACL 120 to permit and deny the specified
traffic. Use the access-list command to create a numbered IP ACL.

R1(config)# access-list 120 permit icmp any any echo-reply

R1(config)# access-list 120 permit icmp any any unreachable
R1(config)# access-list 120 deny icmp any any
R1(config)# access-list 120 permit ip any any

Step 3: Verify that PC-A can successfully ping the loopback interface on R2.

PC> ping 192.168.2.1

Part 5: Create a Numbered IP ACL 110 on R3

Deny all outbound packets with source address outside the range of internal IP addresses on
R3.
Step 1: Configure ACL 110 to permit only traffic from the inside network. Use the
access-list command to create a numbered IP ACL.

R3(config)# access-list 110 permit ip 192.168.3.0 0.0.0.255 any

Step 2: Apply the ACL to interface G0/1. Use the ip access-group command to apply the
access list to incoming traffic on interface G0/1.

Part 6: Create a Numbered IP ACL 100 on R3

On R3, block all packets containing the source IP address from the following pool of
addresses: any RFC 1918 private addresses, 127.0.0.0/8, and any IP multicast address. Since
PC-C is being used for remote administration, permit SSH traffic from the 10.0.0.0/8 network
to return to the host PC-C.

Step 1: Configure ACL 100 to block all specified traffic from the outside network.

You should also block traffic sourced from your own internal address space if it is not an
RFC 1918 address.
In this activity, your internal address space is part of the private address space specified in
RFC 1918. Use the access-list command to create a numbered IP ACL.

R3(config)# access-list 100 permit tcp 10.0.0.0 0.255.255.255 eq 22 host 192.168.3.3

R3(config)# access-list 100 deny ip 10.0.0.0 0.255.255.255 any
R3(config)# access-list 100 deny ip 172.16.0.0 0.15.255.255 any
R3(config)# access-list 100 deny ip 192.168.0.0 0.0.255.255 any
R3(config)# access-list 100 deny ip 127.0.0.0 0.255.255.255 any
R3(config)# access-list 100 deny ip 224.0.0.0 15.255.255.255 any
R3(config)# access-list 100 permit ip any any

Step 2: Apply the ACL to interface Serial 0/0/1. Use the ip access-group command to
apply the access list to incoming traffic on interface Serial 0/0/1.

R3(config)# interface s0/0/1

R3(config-if)# ip access-group 100 in

Step 3: Confirm that the specified traffic entering interface Serial 0/0/1 is handled
correctly.

a. From the PC-C command prompt, ping the PC-A server. The ICMP echo replies are
blocked by the ACL since they are sourced from the 192.168.0.0/16 address space.

b. Establish an SSH session to 192.168.2.1 from PC-C (should be successful).

 Practical 6
Configuring IPv6 ACLs

Topology

Addressing table:

Device Interface IP Address Default Gateway

R1 G0/0 2001:DB8:1:10::1/64 N/A

G0/1 2001:DB8:1:11::1/64 N/A

S0/2/0 (DCE) 2001:DB8:1:1::1/64 N/A

R2 S0/2/0 2001:DB8:1:1::2/64 N/A

S0/3/0 (DCE) 2001:DB8:1:2::2/64 N/A

R3 G0/0 2001:DB8:1:30::1/64 N/A

S0/2/0 2001:DB8:1:2::1/64 N/A

PC0 NIC 2001:DB8:1:10::10/64 FE80::1

PC1 NIC 2001:DB8:1:10::11/64 FE80::1

Server NIC 2001:DB8:1:30::30/64 FE80::3

Objective:
● Configure , Apply and Verify an IPv6 ACL
● Configure , Apply , and Verify a Second IPv6 ACL

Configure Router for IPv6 address:

R1

R2

R3
Assigning IP to PC0 and PC1 and Server
Ping output:
Set router Id:

R1#conf t
Enter configuration commands, one per line. End with CNTL/Z.
R1(config)#hostname R1
R1(config)#ipv6 unicast-routing
R1(config)#ipv6 router eigrp 1
R1(config-rtr)#no shutdown
R1(config-rtr)#eigrp router-id 1.1.1.1
R1(config-rtr)#end

R2>en
R2#conf t
Enter configuration commands, one per line. End with CNTL/Z.
R2(config)#ipv6 unicast-routing
R2(config)#ipv6 router eigrp 1
R2(config-rtr)#no shutdown
R2(config-rtr)#eigrp router-id 2.2.2.2

R3>en
R3#conf t
Enter configuration commands, one per line. End with CNTL/Z.
R3(config)#ipv6 unicast-routing
R3(config)#ipv6 router eigrp 1
R3(config-rtr)#no shutdown
R3(config-rtr)#eigrp router-id 3.3.3.3
Inform it to all the interface:

R1

R1>en
R1#conf t
Enter configuration commands, one per line. End with CNTL/Z.
R1(config)#interface GigabitEthernet0/0
R1(config-if)#ipv6 eigrp 1
R1(config-if)#ex
R1(config)#interface GigabitEthernet0/1
R1(config-if)#ipv6 eigrp 1
R1(config-if)#ex
R1(config)#interface Serial0/0/0
R1(config-if)#ipv6 eigrp 1
R1(config-if)#ex

R2
R3

Copy the configuration File:

In order to check all the setup:

Part 1: Configure, Apply, and Verify an IPv6 ACL

Step 1: Configure an ACL that will block HTTP and HTTPS access.
Configure an ACL named BLOCK_HTTP on R1 with the following statements.

A. Block HTTP and HTTPS traffic from reaching Server3.

Configure ACL on R1:

B. Allow all other IPv6 traffic to pass.

Step 2: Apply the ACL to the correct interface.

Step 3: Verify the ACL implementation.

Open the web browser of PC1 to http://2001:DB8:1:30::30 or

https://2001:DB8:1:30::30. The website should appear.
Open the web browser of PC2 to http://2001:DB8:1:30::30 or
https://2001:DB8:1:30::30. The website should be blocked.

Ping from PC2 to 2001:DB8:1:30::30. The ping should be successful.

Part 2: Configure, Apply, and Verify a Second IPv6 ACL

Step 1: Create an access list to block ICMP.

Set named ACL for blocking from PC1 and PC2 to server ICMP Packet (Ping
Command):

R3(config)#ipv6 access-list BLOCK_ICMP

R3(config-ipv6-acl)#deny icmp any any
R3(config-ipv6-acl)#permit ipv6 any any
R3(config-ipv6-acl)#
R3(config-ipv6-acl)#end
R3(config-if)#exit
R3(config)#interface GigabitEthernet0/0
R3(config-if)#ipv6 traffic-filter BLOCK_ICMP out
R3(config-if)#
Step 2: Apply the ACL to the Correct Interface

Step 3: Verify that the proper access list functions

a. Ping from PC2 to 2001:DB8:1:30::30. The ping should fail.

b. Ping from PC1 to 2001:DB8:1:30::30. The ping should fail.

c. Open the web browser of PC1 to http://2001:DB8:1:30::30 or
https://2001:DB8:1:30::30. The website should display.
 Practical 7
Configuring a Zone-Based Policy Firewall (ZPF)

Topology

IP Addressing :

Device Interface IP Address Subnet Mask Default

Gateway

R1 G0/1 192.168.1.1 255.255.25.0 NA

S0/0/0(DCE) 10.1.1.1 255.255.255.252 NA

R2 S0/0/0 10.1.1.2 255.255.255.252 NA

S0/0/1 (DCE) 10.2.2.2 255.255.255.252 NA

R3 G0/1 192.168.3.1 255.255.255.0 NA

S0/0/1 10.2.2.1 255.255.255.252 NA

PC-A NIC 192.168.1.3 255.255.255.0 192.168.1.1

PC-C NIC 192.168.3.3 255.255.255.0 192.168.3.1

Objectives
• Verify connectivity among devices before firewall configuration.
• Configure a zone-based policy (ZPF) firewall on R3.
• Verify ZPF firewall functionality using ping, SSH, and a web browser.
Background/Scenario
ZPFs are the latest development in the evolution of Cisco firewall technologies. In this
activity, you will configure a basic ZPF on an edge router R3 that allows internal hosts access
to external resources and blocks external hosts from accessing internal resources. You will
then verify firewall functionality from internal and external hosts.

The routers have been pre-configured with the following:

o Console password: ciscoconpa55
o Password for vty lines: ciscovtypa55
o Enable password: ciscoenpa55

Do same for all three routers i.e R1 , R2 , R3

Static Routing
Configure SSH
Part 1: Verify Basic Network Connectivity

Verify network connectivity prior to configuring the zone-based policy firewall.

Step 1: From the PC-A command prompt, ping PC-C at 192.168.3.3.

Step 2: Access R2 using SSH.

a. From the PC-C command prompt, SSH to the S0/0/1 interface on R2 at 10.2.2.2. Use
the username Admin and password Adminpa55 to log in. PC> ssh -l Admin 10.2.2.2
b. Exit the SSH session.
Step 3: From PC-C, open a web browser to the PC-A server.
a. Click the Desktop tab and then click the Web Browser application. Enter the PC-A IP
address 192.168.1.3 as the URL. The Packet Tracer welcome page from the web server
should be displayed.
b. Close the browser on PC-C.

Part 2: Create the Firewall Zones on R3

Note: For all configuration tasks, be sure to use the exact names as specified.

Step 1: Enable the Security Technology package.

a. On R3, issue the show version command to view the Technology Package licence
information.

b. If the Security Technology package has not been enabled, use the following command
to enable the package.

R3(config)# license boot module c1900 technology-package securityk9

c. Accept the end-user license agreement.
d. Save the running-config and reload the router to enable the security license.
e. Verify that the Security Technology package has been enabled by using the show
version command.

Step 2: Create an internal zone. Use the zone security command to create a zone named
IN-ZONE.
R3(config)# zone security IN-ZONE
R3(config-sec-zone) exit

Step 3: Create an external zone. Use the zone security command to

create a zone named OUT-ZONE.

R3(config-sec-zone)# zone security OUT-ZONE

R3(config-sec-zone)# exit

Part 3: Identify Traffic Using a Class-Map

Step 1: Create an ACL that defines internal traffic.

Use the access-list command to create extended ACL 101 to permit all IP protocols from the
192.168.3.0/24 source network to any destination.

R3(config)# access-list 101 permit ip 192.168.3.0 0.0.0.255 any

Step 2: Create a class map referencing the internal traffic ACL.

Use the class-map type inspect command with the match-all option

R3(config)# class-map type inspect match-all IN-NET-CLASS-MAP

R3(config-cmap)# match access-group 101
R3(config-cmap)# exit

Part 4: Specify Firewall Policies

Step 1: Create a policy map to determine what to do with matched traffic. Use the
policy-map type inspect command and create a policy map named IN-2-OUT-PMAP.

R3(config)# policy-map type inspect IN-2-OUT-PMAP

Step 2: Specify a class type of inspect and reference class map IN-NET-CLASS-MAP.

R3(config-pmap)# class type inspect IN-NET-CLASS-MAP

Step 3: Specify the action of inspect for this policy map.

The use of the inspect command invokes context-based access control (other options
include pass and drop).

R3(config-pmap-c)# inspect
%No specific protocol configured in class IN-NET-CLASS-MAP for inspection. All
protocols will be inspected. Issue the exit command twice to leave config-pmap-c mode and
return to config mode.
R3(config-pmap-c)# exit
R3(config-pmap)# exit

Part 5: Apply Firewall Policies

Step 1: Create a pair of zones.

Using the zone-pair security command, create a zone pair named IN-2-OUT-ZPAIR. Specify
the source and destination zones that were created in Task 1.

R3(config)#
zone-pair security IN-2-OUT-ZPAIR source IN-ZONE destination OUT-ZONE

Step 2: Specify the policy map for handling the traffic between the two zones.
Attach a policy-map and its associated actions to the zone pair using the service-policy type
inspect command and reference the policy map previously created, IN-2-OUT-PMAP.

R3(config-sec-zone-pair)# service-policy type inspect IN-2-OUT-PMAP

R3(config-sec-zone-pair)# exit
R3(config)#

Step 3: Assign interfaces to the appropriate security zones.

Use the zone-member security command in interface configuration mode to assign G0/1
to IN-ZONE and S0/0/1 to OUT-ZONE.

R3(config)# interface g0/1

R3(config-if)# zone-member security IN-ZONE
R3(config-if)# exit
R3(config)# interface s0/0/1
R3(config-if)# zone-member security OUT-ZONE
R3(config-if)#exit

Step 4: Copy the running configuration to the startup configuration.

Part 6: Test Firewall Functionality from IN-ZONE to OUT-ZONE

Verify that internal hosts can still access external resources after configuring the ZPF.

Step 1: From internal PC-C, ping the external PC-A server.

From the PC-C command prompt, ping PC-A at 192.168.1.3. The ping should succeed.
Step 2: From internal PC-C, SSH to the R2 S0/0/1 interface.

a. From the PC-C command prompt, SSH to R2 at 10.2.2.2. Use the username Admin
and the password Adminpa55 to access R2. The SSH session should succeed.

b. While the SSH session is active, issue the command

show policy-map type inspect zone-pair sessions on R3 to view established sessions.
Step 3: From PC-C, exit the SSH session on R2 and close the command prompt window.

Step 4: From internal PC-C, open a web browser to the PC-A server web page.

Enter the server IP address 192.168.1.3 in the browser URL field, and click Go. The
HTTP session should succeed. While the HTTP session is active, issue the command
show policy-map type inspect zone-pair sessions on R3 to view established sessions.

Note: If the HTTP session times out before you execute the command on R3, you will
have to click the Go button on PC-C to generate a session between PC-C and PC-A.

R3# show policy-map type inspect zone-pair sessions

Step 5: Close the browser on PC-C.

Part 7: Test Firewall Functionality from OUT-ZONE to IN-ZONE

Verify that external hosts CANNOT access internal resources after configuring the ZPF.

Step 1: From the PC-A server command prompt, ping PC-C.

From the PC-A command prompt, ping PC-C at 192.168.3.3. The ping should fail.

Step 2: From R2, ping PC-C.

From R2, ping PC-C at 192.168.3.3. The ping should fail.

 Practical 8
Configuring IOS Intrusion Prevention System(IPS)

Topology

Addressing Table:

Device Interface IP Address Subnet Mask Default Gateway

R1 G0/1 192.168.1.1 255.255.255.0 N/A

S0/0/0 (DCE) 10.1.1.1 255.255.255.252 N/A

S0/0/0 10.1.1.2 255.255.255.0 N/A

R2
S0/0/1 (DCE) 10.2.2.2 255.255.255.252 N/A

R3 G0/1 192.168.3.1 255.255.255.0 N/A

S0/0/1 10.2.2.1 255.255.255.252 N/A

Syslog NIC 192.168.1.50 255.255.255.0 192.168.1.1

PC-A NIC 192.168.1.2 255.255.255.0 192.168.1.1

PC-B NIC 192.168.3.2 255.255.255.0 192.168.3.1

Objectives
• Enable IOS IPS.
• Configure logging.
• Modify an IPS signature.
• Verify IPS.
Background / Scenario
Your task is to enable IPS on R1 to scan traffic entering the 192.168.1.0 network.
The server labeled Syslog is used to log IPS messages. You must configure the router to
identify the syslog server to receive logging messages. Displaying the correct time and date
in syslog messages is vital when using syslog to monitor the network. Set the clock and
configure the timestamp service for logging on the routers. Finally, enable IPS to produce an
alert and drop ICMP echo reply packets inline.

The server and PCs have been preconfigured. The routers have also been preconfigured with
the following:

Do for all the Three Routers

o Console password: ciscoconpa55

o Enable password: ciscoenpa55

o SSH username and password:SSHadmin / ciscosshpa55

o OSPF 20
Part 1: Enable IOS IPS

Step 1: Enable the Security Technology package.

a. On R1, issue the show version command to view the Technology Package licence
information.

b. If the Security Technology package has not been enabled, use the following command
to enable the package.

c. Accept the end user licence agreement.

d. Save the running-config and reload the router to enable the security licence.

e. Verify that the Security Technology package has been enabled by using the show
version command.
Step 2: Verify network connectivity.

a. Ping from PC-C to PC-A. The ping should be successful.

b. Ping from PC-A to PC-C. The ping should be successful.
Step 3: Create an IOS IPS configuration directory in flash.

On R1, create a directory in flash using the mkdir command. Name the directory ipsdir.

Step 4: Configure the IPS signature storage location.

On R1, configure the IPS signature storage location to be the directory you just created.

R1(config)# ip ips config location flash:ipsdir

Step 5: Create an IPS rule.

On R1, create an IPS rule name using the ip ips name name command in global configuration
mode. Name the IPS rule iosips.

R1(config)# ip ips name iosips

Step 6: Enable logging.

IOS IPS supports the use of syslog to send event notification. Syslog notification is enabled
by default. If logging console is enabled, IPS syslog messages display. a. Enable syslog if it is
not enabled.

R1(config)# ip ips notify log

b. If necessary, use the clock set command from privileged EXEC mode to reset the
clock.

c. Verify that the timestamp service for logging is enabled on the router using the show
run Command.

Enable the timestamp service if it is not enabled.

R1(config)# service timestamps log datetime msec

d. Send log messages to the syslog server at IP address 192.168.1.50.

R1(config)#logging host 192.168.1.50

Step 7: Configure IOS IPS to use the signature categories.

Retire the all signature category with the retired true command (all signatures within the
signature release).
Unretire the IOS_IPS Basic category with the retired false command.

Step 8: Apply the IPS rule to an interface.

Apply the IPS rule to an interface with the ip ips name direction command in interface
configuration mode.
Apply the rule outbound on the G0/1 interface of R1. After you enable IPS, some log
messages will be sent to the console line indicating that the IPS engines are being initialized.
Note: The direction in means that IPS inspects only traffic going into the interface. Similarly,
out means that IPS inspects only traffic going out of the interface.
Part 2: Modify the Signature

Step 1: Change the event-action of a signature.

Un-retire the echo request signature (signature 2004, subsig ID 0), enable it, and change the
signature action to alert and drop.

Step 2: Use show commands to verify IPS.

Use the show ip ips all command to view the IPS configuration status summary.
To which interfaces and in which direction is the iosips rule applied?
Step 3: Verify that IPS is working properly.

a. From PC-C, attempt to ping PC-A. Were the pings successful? Explain.

The pings should fail. This is because the IPS rule for event-action of an echo request was set
to “deny-packet-inline”.
b. From PC-A, attempt to ping PC-C. Were the pings successful? Explain.

The ping should be successful. This is because the IPS rule does not cover echo reply. When
PC-A pings PC-C, PC-C responds with an echo reply.
Step 4: View the syslog messages.

a. Click the Syslog server.

b. Select the Services tab.
c. In the left navigation menu, select SYSLOG to view the log file.
 Practical 9
Layer 2 Security

Topology
Objectives
• Assign the Central switch as the root bridge.
• Secure spanning-tree parameters to prevent STP manipulation attacks.
• Enable port security to prevent CAM table overflow attacks.

Background / Scenario
There have been a number of attacks on the network recently. For this reason, the
network administrator has assigned you the task of configuring Layer 2 security.
For optimum performance and security, the administrator would like to ensure that
the root bridge is the 3560 Central switch. To prevent spanning-tree manipulation
attacks, the administrator wants to ensure that the STP parameters are secure. To
prevent against CAM table overflow attacks, the network administrator has decided
to configure port security to limit the number of MAC addresses each switch port can
learn. If the number of MAC addresses exceeds the set limit, the administrator would
like the port to be shutdown. All switch devices have been preconfigured with the
following:

All devices have been pre configured with:

o Enable secret password: ciscoenpa55
o Console password: ciscoconpa55
o SSH username and password: SSHadmin / ciscosshpa55

Part 1: Configure Root Bridge

Step 1: Determine the current root bridge.
Step 2: Assign Central as the primary root bridge. Using the spanning-tree
vlan 1 root
primary command, and assign Central as the root bridge.

Central(config)# spanning-tree vlan 1 root primary

Step 3: Assign SW-1 as a secondary root bridge. Assign SW-1 as the

secondary root bridge using the spanning-tree vlan 1 root secondary
command.

SW-1(config)# spanning-tree vlan 1 root secondary

Step 4: Verify the spanning-tree configuration. Issue the show spanning-

tree command to verify that Central is the root bridge.

Central# show spanning-tree

Part 2: Protect Against STP Attacks

Secure the STP parameters to prevent STP manipulation attacks.

Step 1: Enable PortFast on all access ports.

PortFast is configured on access ports that connect to a single workstation or server

to enable them to become active more quickly. On the connected access ports of the
SW-A and SW-B, use the spanning-tree portfast command.

SW-A(config)# interface range f0/1 - 4

SW-A(config-if-range)# spanning-tree portfast

SW-B(config)# interface range f0/1 - 4

SW-B(config-if-range)# spanning-tree portfast
Step 2: Enable BPDU guard on all access ports.

BPDU guard is a feature that can help prevent rogue switches and spoofing on
access ports. Enable BPDU guard on SW-A and SW-B access ports.

SW-A(config)# interface range f0/1 - 4

SW-A(config-if-range)# spanning-tree bpduguard enable

SW-B(config)# interface range f0/1 - 4

SW-B(config-if-range)# spanning-tree bpduguard enable

Note: Spanning-tree BPDU guard can be enabled on each individual port using the
spanning-tree bpduguard enable command in interface configuration mode or the
spanning-tree portfast bpduguard default command in global configuration mode. For
grading purposes in this activity, please use the spanning-tree bpduguard enable
command.

Step 3: Enable root guard.

Root guard can be enabled on all ports on a switch that are not root ports. It is best
deployed on ports that connect to other non-root switches. Use the show
spanning-tree command to determine the location of the root port on each switch. On
SW-1, enable root guard on ports F0/23 and F0/24. On SW-2, enable root guard on
ports F0/23 and F0/24.

SW-1(config)# interface range f0/23 - 24

SW-1(config-if-range)# spanning-tree guard root

SW-2(config)# interface range f0/23 - 24

SW-2(config-if-range)# spanning-tree guard root

Part 3: Configure Port Security and Disable Unused Ports

Step 1: Configure basic port security on all ports connected to host devices.

This procedure should be performed on all access ports on SW-A and SW-B. Set the
maximum number of learned MAC addresses to 2, allow the MAC address to be
learned dynamically, and set the violation to shutdown. Note: A switch port must be
configured as an access port to enable port security.

SW-A(config)# interface range f0/1 - 22

SW-A(config-if-range)# switchport mode access
SW-A(config-if-range)# switchport port-security
SW-A(config-if-range)# switchport port-security maximum 2
SW-A(config-if-range)# switchport port-security violation shutdown
SW-A(config-if-range)# switchport port-security mac-address sticky
SW-B(config)# interface range f0/1 - 22
SW-B(config-if-range)# switchport mode access
SW-B(config-if-range)# switchport port-security
SW-B(config-if-range)# switchport port-security maximum 2
SW-B(config-if-range)# switchport port-security violation shutdown
SW-B(config-if-range)# switchport port-security mac-address sticky

Step 2: Verify port security.

a. On SW-A, issue the command show port-security interface f0/1 to verify that
port security has been configured.

SW-A# show port-security interface f0/1

b. Ping from C1 to C2 and issue the command show port-security interface f0/1
again to verify that the switch has learned the MAC address for C1.
Step 3: Disable unused ports.

Disable all ports that are currently unused.

SW-A(config)# interface range f0/5 - 22

SW-A(config-if-range)# shutdown
SW-B(config)# interface range f0/5 - 22
SW-B(config-if-range)# shutdown
 Practical 10
Configure and Verify a Site-to-Site IPSec VPN Using CLI
Topology:

Addressing Table:

Devic Interface IP Address Subnet Mask Default

e Gateway

R1 G0/0 192.168.1.1 255.255.255.0 N/A

S0/0/0 (DCE) 10.1.1.2 255.255.255.252 N/A

G0/0 192.168.2.1 255.255.255.0 N/A

R2
S0/0/0 10.1.1.1 255.255.255.252 N/A

S0/0/1 (DCE) 10.2.2.1 255.255.255.252 N/A

R3 G0/0 192.168.3.1 255.255.255.0 N/A

S0/0/1 10.2.2.2 255.255.255.252 N/A

PC-A NIC 192.168.1.3 255.255.255.0 192.168.1.1

PC-B NIC 192.168.2.3 255.255.255.0 192.168.2.1

PC-C NIC 192.168.3.3 255.255.255.0 192.168.3.1

Objectives

• Verify connectivity throughout the network.

• Configure R1 to support a site-to-site IPsec VPN with R3.

Background / Scenario
The network topology shows three routers. Your task is to configure R1 and R3 to
support a site-to-site IPsec VPN when traffic flows between their respective LANs.
The IPsec VPN tunnel is from R1 to R3 via R2. R2 acts as a pass-through and has
no knowledge of the VPN. IPsec provides secure transmission of sensitive
information over unprotected networks, such as the Internet. IPsec operates at the
network layer and protects and authenticates IP packets between participating IPsec
devices (peers), such as Cisco routers.

The routers have been pre-configured with the following:

• Password for console line: ciscoconpa55
R1

R2

R3

• Password for vty lines: ciscovtypa55

R1

R2

R3

• Enable password: ciscoenpa55

R1
R2

R3

OSPF:
R1

R2

R3

Part 1: Configure IPsec Parameters on R1

Step 1: Test connectivity.

Ping from PC-A to PC-C.

Step 2: Enable the Security Technology package.

a. On R1, issue the show version command to view the Security Technology
package license information.

b. If the Security Technology package has not been enabled, use the following
command to enable the package.

R1(config)# license boot module c1900 technology-package securityk9

c. Accept the end-user license agreement.

d. Save the running-config and reload the router to enable the security license.

e. Verify that the Security Technology package has been enabled by using the
show version command.
Step 3: Identify interesting traffic on R1.

Configure ACL 110 to identify the traffic from the LAN on R1 to the LAN on R3 as
interesting. This interesting traffic will trigger the IPsec VPN to be implemented when
there is traffic between the R1 to R3 LANs. All other traffic sourced from the LANs
will not be encrypted. Because of the implicit deny all, there is no need to configure a
deny ip any any statement.

Step 4: Configure the IKE Phase 1 ISAKMP policy on R1.

Configure the crypto ISAKMP policy 10 properties on R1 along with the shared
crypto key vpnpa55. Refer to the ISAKMP Phase 1 table for the specific parameters
to configure. Default values do not have to be configured. Therefore, only the
encryption method, key exchange method, and DH method must be Configured.

Note: The highest DH group currently supported by Packet Tracer is group 5. In a

production network, you would configure at least DH 14.

Step 5: Configure the IKE Phase 2 IPsec policy on R1.

a. Create the transform-set VPN-SET to use esp-aes and esp-sha-hmac.

b. Create the crypto map VPN-MAP that binds all of the Phase 2 parameters
together. Use sequence number 10 and identify it as an ipsec-isakmp map.

Step 6: Configure the crypto map on the outgoing interface.

Bind the VPN-MAP crypto map to the outgoing Serial 0/0/0 interface.

Part 2: Configure IPsec Parameters on R3

Step 1: Enable the Security Technology package.

a. On R3, issue the show version command to verify that the Security
Technology package license information has been enabled.
b. If the Security Technology package has not been enabled, enable the
package and reload R3.

Step 2: Configure router R3 to support a site-to-site VPN with R1.

Configure reciprocating parameters on R3. Configure ACL 110 identifying the traffic
from the LAN on R3 to the LAN on R1 as interesting.

Step 3: Configure the IKE Phase 1 ISAKMP properties on R3. Configure the
crypto ISAKMP policy 10 properties on R3 along with the shared crypto key

vpnpa55.

Step 4: Configure the IKE Phase 2 IPsec policy on R3.

a. Create the transform-set VPN-SET to use esp-aes and esp-sha-hmac.

b. Create the crypto map VPN-MAP that binds all of the Phase 2 parameters
together. Use sequence number 10 and identify it as an ipsec-isakmp map.

Step 5: Configure the crypto map on the outgoing interface. Bind the VPN-MAP
crypto
map to the outgoing Serial 0/0/1 interface. Note: This is not graded.
Part 3: Verify the IPsec VPN

Step 1: Verify the tunnel prior to interesting traffic.

Issue the show crypto ipsec sa command on R1. Notice that the number of packets
encapsulated, encrypted, decapsulated, and decrypted are all set to 0.

Step 2: Create interesting traffic.

Ping PC-C from PC-A.

Step 3: Verify the tunnel after interesting traffic.

On R1, re-issue the show crypto ipsec sa command. Notice that the number of
packets is more than 0, which indicates that the IPsec VPN tunnel is working.
Step 4: Create uninteresting traffic.

Ping PC-B from PC-A.

Note: Issuing a ping from router R1 to PC-C or R3 to PC-A is not interesting traffic.
Step 5: Verify the tunnel.

On R1, re-issue the show crypto ipsec sa command. Notice that the number of
packets has not changed, which verifies that uninteresting traffic is not encrypted.