T. Andrew Yang
|
Last updated: Jan. 21, 2009 |
|||
CSCI 5234 Web Security Note:
1.A (5 pts) Visit the class discussion group (see
the syllabus page) and join the group as a member.
Throughout this class, you are responsible for regularly visiting the
discussion group to find recent announcements, reminders, and discussions.
Alternatively, you may set up the account so messages posted to the
group will be automatically forwarded to your chosen email account. Print
out the confirmation message in response to your membership request, and
attach it to this assignment.
1.C Study the textbooks and/or applicable web sites to find answers for the following questions. Online glossaries such as those listed in the syllabus page may also be used. It is important that you clearly identify the source(s) of your information.
2.A Read VeriSign's Technical Brief "Building an E-Commerce Trust Infrastructure: SSL Server Certificates and Online Payment Services", and answer the following questions:
2.B Answer the following questions, based on the paper “Ten Risks of PKI: What You’re not Being Told about Public Key Infrastructure” (Ellison and Schneier, 2001, local copy is here). 1. (5 pts) In the paper, the authors discussed ten types of risks associated with certificates and PKI. Risk #2, for example, is related to ‘Who is using my key?’ Explain what this risk means and its implications in web security. 2. (20 pts, 5 pts per risk) Identify four of the risks which you think are most related to web security. Explain what each of these risks is and why you think it would have a major impact upon the security of a web application. 2.C (10 pts) Study Chapter 9 of the GS book and answer concisely (< 100 words each) the following questions. a. Explain the significance of server certificate in SSL handshake. How is the certificate processed by the client? b. Communication in SSL between the client and the server is encrypted with a session key. Explain how the session key is generated. Go to the Index Note: This is an individual project.
The goal of this project is for you to visit refereed publications (as well as some relevant web sites) to perform a detailed investigation of a chosen research topic. The topic you choose ideally should be related to Web technologies and their security issues/control. See sample research projects for some potential topics. If you need suggestions when choosing the topic, feel free to discuss with the instructor. Items to be submitted:
A preliminary abstract of your presentation topic is due early in the semester. Each student should publish his/her abstract in the class discussion board by the due date. The abstract should be 1-2 pages long, and contains the following sections: (1) Class name (i.e., CSCI5234 Web Security) (2) Your name and an email address that you check regularly (that is, at least once a day) (3) Topic of your investigation (4) General description of the topic (5) Why is the topic worth investigating? How is it related to web security? (6) Three or more articles related to the topic. VERY Important: Make sure you properly cite the work of other researchers or professionals. Visit http://sce.uhcl.edu/yang/citing.htm for more information about cited references. Warning: Missing or improper cited references in your abstract and final report will result in poor score for your presentation. (7) A tentative outline (agenda) of your final report. That is, the sections/subsections that you plan to include in the final paper.
Warning: Missing or improper cited references in your abstract and final report will result in poor score for this assignment.
i. Title ii. Your name (and email address) iii. An abstract (50-100 words) iv. Introduction to the topic v. Significance of the chosen topic with respect to the security of web-based applications vi. Your findings vii. Future work: research ideas and projects possibly related to the topic viii. Conclusion ix. Appendix (if any)
Go to the Index
Each team shall select one of the projects from the project list and notify the instructor the chosen topic. A detailed design, along with a prototype, is due for in-class presentation and demo around the midterm time (that is, project 1 demo in the syllabus page). o Requirements 1. The design of your project shall consist of three or more tiers, including the front tier (a web client), the middle tier (a web application), and the back tier (a DBMS). The front tier provides the web clients proper user interface to the web application, which processes the clients' requests and, if necessary, forwards the request to the DBMS at the back end. 2. In your design, potential vulnerability of the whole application shall be identified and discussed. 3. Use diagrams (UML, EER, etc.) and textual descriptions to present your design. 4. The prototype shall properly demonstrate how the three tiers would work together, although details may be filled in later in the projects. If you have any doubt concerning what should be completed in each stage of the project, feel free to consult the instructor. o Deliverables
of the Projects (1) Preliminary
Design The preliminary design of your project should illustrate the system architecture (front end, middle tier, back end, etc.) of the application you plan to build. Publish your preliminary design in the class discussion board to solicit your classmates’ and the instructor’s comments. (2) Detailed Design and Prototype demonstration a) Each team should publish, in the discussion group, its project’s detailed design, which contains the following: a. A UML diagram illustrating the design of the application, the source programs, a readme file explaining how the source programs would be used or installed, as well as any specific configuration files and/or steps; b. A relational database model for the data stored in the database server. b) Each team needs to give an in-class demonstration of the prototype. See the class schedule for the demo date. Note: Each team has about 15 minutes to demonstrate its application. Peer evaluation will be part of the evaluation process. (3) Final
report The final project report should contain the system architecture, the final detailed design, the source programs (if applicable), responses to comments made by the instructor and the classmates. Publish the final project report in the class discussion board. |
|