Lectures will be on Wednesday at 11:00, CG01 and Thursday at 13:00, CAG21.
768 User Datagram Protocol
791 Internet Protocol
792 Internet Control Message Protocol
793 Transmission Control Protocol
826 Address Resolution Protocol
1180 A Tutorial on TCP/IP
There are lab times on the timetable, however these are unsupervised labs. Rather than set individual labs each week, I will be listing various applications and techniques that you must be familiar with. Most tools will only be legal to run on ones own LAN or the MSSF lab. Do not experiment on unauthorised machines/networks.
I would suggest picking a machine and installing a primary OS on it, such as Windows XP or Ubuntu. Install a virtual machine application and then download/create images of Operating Systems which you can then run your tools from. Backtrack is a particularly good version of Linux for performing penetration testing. There is even a pre-made virtual image available. http://www.remote-exploit.org/backtrack_download.html
You need to be familiar with using tcpdump and wireshark on a network. Examine TCP connection attempts to see the handshake process and the Initial Sequence Number (ISN) values used. This will need to be done in pairs, with one person running a service on their machine, a web server for example and the other person connecting with a web client.
|
Tip
|
You will need to disable the relative ISN values. |
Things to look out for are identifying the manufacturer from the MAC address, Wireshark should do this for you automaticly.
Implement an attack with ARP Poisoning as described in the notes. Analyse the attack implementation with Wireshark. Tools you can use are Ettercap or DSniff
There is a video demonstrating Ettercap available at http://securitytube.net/Packet-Sniffing-With-Ettercap-video.aspx
Install ARPWatch and configure it to monitor for ARP Poisoning
Install Windows or Linux on a lab machine. (You can just use the PXE boot option if you want). Disable the firewall.
From another machine, run nmap to scan the target machine. Re-enable the windows firewall, or implement a firewall on the Linux machine, and run the scan again. Does the firewall report any scanning? Examine what Nmap is doing by running Wireshark at the same time. Configure the firewall to only allow access from a certain IP. How will you scan the Windows machine without access to that restricted machine ?