CPTR 542 Advanced Network Security

This page provides hints, insights and direction for the graduate class in Network Security. As a graduate class I am not interested in just teaching you how to use tools to exploit systems. I also want you to be able to research new methods to exploit and protect systems. Consequently you will find a balance between learning about tools and known techniques and pushing the boundary to extend those techniques and create new tools for exploits and defense. Because of this, research is a big part of this class. As we look at existing tools, we'll discuss what it does, how it works, and how to extend the functionality and research possibilities related to what we are learning.

/NotesForNextClass

Weekly Routine

1. Current Events Discussion / Research presentations (Keep it short!)
2. Retrospective on previous assignment/work.
3. Discuss Chapter
4. Discuss upcoming assignment.

Research Resources

• PTES - Penetration Testing Execution Standard (Our book loosely follows this)

• List of online databases available at Southern

• Scholar on Google is always a good resource

When doing research it helps to know where to look. Dr. Gu does a nice job of rating security conferences that you might want to research from. IEEE S & P and ACM's Conference on Computer and Communications Security top the list and are good candidates to watch.

Research Assignment

Presenting Peer-Reviewed Papers

Each period I would like you to present a summary of a peer reviewed conference paper from an ACM/IEEE/Springer conference (You may also use other notable security conferences). Most topics are your choice, but you should pick papers related to your chosen topic to write on (see next). These should only be 10 minutes max including discussion. One presentation must introduce a new attack or attack technique. One presentation must deal with privacy issues inside the US. The other papers are up to you. You may choose to do the required topics during any regular class.

Writing your own Research Paper

1. Your first paper should be a survey paper that analyzes current and historically significant research of your particular topic and makes recommendations about use.
2. Your second paper should be an implementation of a previously unimplemented idea or extension/application of some area you found interesting in your first paper.

Ideas:

• You might implement a method of attach to provide new proof of concept code
• Research specific activities related to personal privacy compromised by companies or governments that may be illegal in other countries or protected by the US constitution
• Vulnerability monitoring system based on OSVDB and nvd.nist.gov – Create a system that monitors installed list of programs and alerts to new vulnerabilities listed in the above databases. This may be used as a tool to attack or defend systems.
• An aspect of hacking, such as code-security analysis techniques and tools for various languages.

Homework Assignments

1. Research:
   1. Use peer reviewed articles in ACM/IEEE etc., to find the conditions necessary to "more easily" attack the RSA algorithm. What known attacks exist against RSA?
   2. Determine if there exists known attacks against AES. Do we consider AES to be secure?
   3. What attacks exist against hash algorithms? What algorithms are not considered secure?
2. Install Kali on your system. Let me know if you need a virtual machine for this. Write a planning and scope document that covers the issues from Chapter 1 including rules of engagement (ROE). Make sure to cover all your bases for this document. You may collaborate to write this document as a class. The ultimate target is brain2.scotnpatti.com (this server)
3. Use the techniques covered in Chapter 2 to
   1. RECON both cs.southern.edu and scotnpatti.com - make sure you follow the Rules of Engagement (ROE) agreed upon in the previous assignment.
   2. Find a willing personal target and profile that person to discover what you can about them online.
   3. Document what you find organized into three reports one for cs.southern.edu, one for scotnpatti.com and one for the "victim" who agreed to be used in (b). Turn in these documents online in eclass.
4. Using the enumeration techniques from Chapter 3
   1. Enumerate the machine targets available for exploitation and any information collected.
   2. Enumerate separately any network hardware available for exploitation.
   3. Be ready to discuss enumeration avoidance techniques
5. Using the tools we are studying from Chapter 4-5, try to exploit something from the allowed target list in our pentest plan and bring proof of your exploit. What remediation is needed. If you are unable to exploit make sure to systematically document everything you have tried. We will need this later in our report!
6. Think of a tool to solve a common problem, something that would be useful to an administrator and write a vulnerable tool. Show how to exploit it using one of the automated techniques from the chapter.

7. Write a report for your client on what you found. I will ask what tools you used for reporting, and proof that you were able to break into systems. If you have questions, I will give you time to ask in class. Make sure to give a detailed penetration test report of vulnerabilities found, exploits performed, proof of exploits and remediation recommendations etc.

8. To date you should have been able to find some sort of way into the system in the ROE and perhaps created your own administrator account, stolen files, or changed web pages. You must now fix what you broke, changed or pilfered, and then try to Cover your tracks.

Common Vocabulary and Acronyms

• MITM = Man in the middle
• Monitize = to convert into monitary value i.e. money.
• ROE = Rules of Engagement

Entertaining Links

• Buffer Overflow example

• /BufferOverFlowExample from book

• /BufferOverFlowSolution for Book

• Nice discussion of Salting

• Netcraft - shows information history of a site, interesting

• Dr. A's Kioptrix 1 solution including adding a root user.

Vulnerability Databases

• National Vulnerability Database

• Common Vulnerabilities and Exposures (CVE)

• Rapid7 Vulnerability Database

• Open Source Vulnerability Database

• Symantec Vulnerability Database

• Secunia Vulnerability List