ISE 328 -  Communication and E-Commerce Security
Semester 2 5771


Topics     Reading     Projects     Grading     Lectures     Policies

Time: Wednesday 9:00 - 11:00 in Room 202
Targil: Wednesday 11:00 - 12:00 in Room 202

Instructor:

    Michael J. May
      e-mail: mjmay (AT) kinneret,ac,il
      office hours: Monday. 11:45-12:45(and by appointment)

The full detailed syllabus for the course is available here.

Reminder: Assignment 3 posted. Due 28 May 2011.

Topics:

The topics for the course include some or all of the following:

Threats and Security Requirements Foundations of Modern Cryptography
Encryption and Randomness
Hash Functions
Authentication Public/Private Key Pairs
Shared Secrets
Decentralized Cryptography
Key Management
Certi cates
Network Security Internet Security
Trust Management Electronic Banking
Secure Payments
Credit Card Transactions
Telephone and Cellular Payments Micropayments
Money Transfers Privacy Protection
Digital Cash Content Protection
Trusted Third Party Services: Digital Safes, Notaries, Agents


Reading

The following books contains useful course material, and much of the lecture content is derived from them (and other sources). Copies of these books are on reserve in the Kinneret Library or available freely online:

  • Security Engineering: A Guide for Building Dependendable Systems. (2nd edition) by Ross Anderson. link
  • Secure Electronic Commerce. (2nd Edition). by Warwick Ford and Michael S. Baum
  • Computer Security: Art and Science. by Matt Bishop.
  • Handbook of Applied Cryptography. by Alfred J. Menzes, Paul C van Oorschot, and Scott A. Vanstone. link
Other materials and readings will be introduced during the course of the semester as necessary.

Assignments

Assignment 1: Cryptography - SDES. Designer Code (as ZIP). SDES Specification. Due 30 March 2011.

Assignment 2: Hash, DES, Diffie-Hellman. (גרסא בעברית).  Modular Exponentiation Code.
                      encrypted-testing-file.txt encrypted-testing-file.pdf
                      Designer Code. Due 10 April 2011

Assignment 3: Secure Bank Protocols. Due 28 May 2011

Assignment 4: Student Research.  Due 18 June 2011.

New: Submission instructions: You may submit work using Telem, in person, or by sending email to the address ise328 at gmail.  If you send email to the ise328 address, you will receive an auto-answer response acknowledging that a message has been received.

Grading Criteria

  • 20%   Programming Projects / Assignments
  • 80%   Final Exam

Lecture Slides and Notes

Schedule

#
Date
Topic
Notes
1
23 Feb E-Commerce, Internet Security, Requirements
[pdf][targil]
2
2 March Cryptographic Foundations, History
[pdf][targil, cipher1, cipher2]
3
9 March Stream and Block Cipher Functions
[pdf][SDES, targil]
4
16 March Triple-DES, AES, CBC, Hashes
[pdf][targil, DES-cmd, DES-designer]
5
23 March Hashes, Diffie-Hellman, Public/Private
[pdf][targil, DES-cmd, DES-designer]
6
30 March Public/Private Key Pairs, RSA
[pdf][targil, hashing]
7
6 April Authentication
[pdf][targil, rsa]
8
27 April Authentication Defenses, Digital Signatures
[pdf][no targil]
9
4 May Implementing Secure Protocols
[targil]
10
11 May Key Exchange, Certi cates, PKI
[pdf][targil]
11
18 May One Time Passwords, Kerberos
[pdf][targil, OTP]
12
25 May Passwords and Authentication
[pdf]
13
1 June SSL, SSH, Access Control [pdf]
14
15 June Access Control, Web Security, Phishing
[pdf]

15 July
Final Exam Moed A - TBA 08:30 - 11:30


4 August
Final Exam Moed B - TBA 08:30 - 11:30

Academic Integrity

Since Kinneret College does not have a unified code of academic integrity, this course will abide by the University of Pennsylvania's Code of Academic Integrity. In particular, for individual projects and group projects, the following guidelines should be followed:
  • For individual projects, you must type in and edit your own code, documentation, and any other materials submitted for grading.
    • Copying someone else's file is not allowed.
    • Allowing someone else to copy a file of yours, either explicitly or implicitly by leaving your code unprotected, is not allowed.
    • Editing each other's files is not allowed
  • Regarding the ethics of what you may or may not discuss with others:
    • "High level" discussions are fine.
      For example, discussions about the problem statement.
    • "Low level" discussions are fine.
      For example, discussions about C syntax or using gdb, understanding compiler error messages, understanding the mechanics of the tools and libraries used for the projects.
    • "Mid level" discussions require discretion. In this CIS course, discussions at this level must be limited.  Unless explicitly stated otherwise, you may not collaborate significantly with classmates (except group project members) at this level.  If you have minor discussions with others at this level or get help from outside resources (tutors, web sites, etc), you must cite at the top of the submitted projects the names of the people or websites who helped you and how they did. For example:
            /**
      * Chris Brown
      * Project 1
      * 5/6/2008
      * I received tips from Jo Johnson on the i/o and example.com/mem.htm on memory
      */
  • If there is any doubt about the use of external sources or collabortation, please ask for clarification by the course staff.