Computer Systems Security: Winter 2016 Course Outline - Revision history

Soma at 14:05, 17 March 2016

2016-03-17T14:05:07Z

← Older revision		Revision as of 14:05, 17 March 2016
Line 1:		Line 1:
	~~'''This outline is not yet finalized.'''~~

	==Course Information==		==Course Information==

Soma: /* Hacking Journal */

2016-03-16T14:53:38Z

Hacking Journal

← Older revision		Revision as of 14:53, 16 March 2016
Line 56:		Line 56:

	While students may choose to focus on one project primarily, students should attempt at least one hacking project in each of the four major categories of material of the course, OS, Network, Software, and Web.		While students may choose to focus on one project primarily, students should attempt at least one hacking project in each of the four major categories of material of the course, OS, Network, Software, and Web.

			The hacking journal should be submitted in the form of weekly updates and a final report. The final report should be a nicely formatted version, in PDF, of all previously submitted updates (optionally edited for clarity), discussion of any additional work completed after the last hacking update, and a summary statement of no more than two pages describing your overall experiences with the hacking journal. In this summary statement explain what you learned, what challenges you had, and to what degree you feel the exercise was worthwhile.

			Your final grade will be half your grade for the top five hacking journal updates, half from the grade on your final report. The report will be graded out of 10: 4 points for breadth, 3 for depth, 3 for overall quality of the hacking. One point will be subtracted from the grade if no summary statement is present; otherwise the summary does not affect the report grade.

	===Assignments/Reading Analyses===		===Assignments/Reading Analyses===

Soma: /* Grading */

2016-02-29T20:57:08Z

Grading

← Older revision		Revision as of 20:57, 29 February 2016
Line 35:		Line 35:
	* 20% Class Participation		* 20% Class Participation
	* 20% Hacking Journal		* 20% Hacking Journal
	* 10% Assignments		* 10% Assignments (Reading Analyses)
	* 20% Midterm (Feb. 25th, in class)		* 20% Midterm (Feb. 25th, in class)
	* 30% Final Exam		* 30% Final Exam
Line 57:		Line 57:
	While students may choose to focus on one project primarily, students should attempt at least one hacking project in each of the four major categories of material of the course, OS, Network, Software, and Web.		While students may choose to focus on one project primarily, students should attempt at least one hacking project in each of the four major categories of material of the course, OS, Network, Software, and Web.

	===Assignments===		===Assignments/Reading Analyses===

	~~The course~~ assignments ~~are based on the material covered~~ in ~~lecture~~ and the ~~assigned readings~~. ~~They are short answer~~ and should be submitted in PDF or text format via [https://carleton.ca/culearn/ cuLearn].		In lieu of regular assignments, students will be required to do security reading analyses of five readings. These readings may be ones assigned for class; however, all readings must be analyzed before they have been discussed in class. Outside selections must be published in reputable security venues.

			Optionally, students may submit 10 reading analyses. In this case, assignments will count as 20% of their grade and the hacking journal will count as 10%.

			Reading analyses may be submitted at any time before the final exam and should be submitted in PDF or text format via [https://carleton.ca/culearn/ cuLearn].

	===Midterm and Final Exam===		===Midterm and Final Exam===

Soma: /* Course Information */

2016-01-18T17:38:23Z

Course Information

← Older revision		Revision as of 17:38, 18 January 2016
Line 8:		Line 8:
	*'''Institution:''' Carleton University, School of Computer Science		*'''Institution:''' Carleton University, School of Computer Science
	*'''Instructor:''' [http://people.scs.carleton.ca/~soma Anil Somayaji] (anilsomayaji at connect.carleton.ca): Tuesdays 12:30-2 (and by appointment) in HP 5137		*'''Instructor:''' [http://people.scs.carleton.ca/~soma Anil Somayaji] (anilsomayaji at connect.carleton.ca): Tuesdays 12:30-2 (and by appointment) in HP 5137
	*'''TA:''' Borke Obada-Obieh (BorkeObadaObieh at cmail.carleton.ca): ~~TBD~~ in HP 1170		*'''TA:''' Borke Obada-Obieh (BorkeObadaObieh at cmail.carleton.ca): Wednesdays 3-4:30 PM in HP 1170
	*'''Meeting Time:''' Tuesdays and Thursdyas 10:05-11:25 AM, TB 238		*'''Meeting Time:''' Tuesdays and Thursdyas 10:05-11:25 AM, TB 238
	*'''Course Website''': http://homeostasis.scs.carleton.ca/wiki/index.php/Computer_Systems_Security_(Winter_2016)		*'''Course Website''': http://homeostasis.scs.carleton.ca/wiki/index.php/Computer_Systems_Security_(Winter_2016)

Soma: /* Course Information */

2016-01-11T21:39:08Z

Course Information

← Older revision		Revision as of 21:39, 11 January 2016
Line 7:		Line 7:
	*'''Title:''' Computer Systems Security		*'''Title:''' Computer Systems Security
	*'''Institution:''' Carleton University, School of Computer Science		*'''Institution:''' Carleton University, School of Computer Science
	*'''Instructor:''' [http://people.scs.carleton.ca/~soma Anil Somayaji] (anilsomayaji at connect.carleton.ca): Tuesdays 12:30-2 ~~in HP 1170~~ (and by appointment) in HP 5137		*'''Instructor:''' [http://people.scs.carleton.ca/~soma Anil Somayaji] (anilsomayaji at connect.carleton.ca): Tuesdays 12:30-2 (and by appointment) in HP 5137
	*'''TA:''' Borke Obada-Obieh (BorkeObadaObieh at cmail.carleton.ca): TBD		*'''TA:''' Borke Obada-Obieh (BorkeObadaObieh at cmail.carleton.ca): TBD in HP 1170
	*'''Meeting Time:''' Tuesdays and Thursdyas 10:05-11:25 AM, TB 238		*'''Meeting Time:''' Tuesdays and Thursdyas 10:05-11:25 AM, TB 238
	*'''Course Website''': http://homeostasis.scs.carleton.ca/wiki/index.php/Computer_Systems_Security_(Winter_2016)		*'''Course Website''': http://homeostasis.scs.carleton.ca/wiki/index.php/Computer_Systems_Security_(Winter_2016)

Soma: /* Course Information */

2016-01-11T21:38:49Z

Course Information

← Older revision		Revision as of 21:38, 11 January 2016
Line 7:		Line 7:
	*'''Title:''' Computer Systems Security		*'''Title:''' Computer Systems Security
	*'''Institution:''' Carleton University, School of Computer Science		*'''Institution:''' Carleton University, School of Computer Science
	*'''Instructor:''' [http://people.scs.carleton.ca/~soma Anil Somayaji] (anilsomayaji at connect.carleton.ca): ~~TBD~~ in HP 5137		*'''Instructor:''' [http://people.scs.carleton.ca/~soma Anil Somayaji] (anilsomayaji at connect.carleton.ca): Tuesdays 12:30-2 in HP 1170 (and by appointment) in HP 5137
	*'''TA:''' Borke Obada-Obieh (BorkeObadaObieh at cmail.carleton.ca): TBD ~~in HP 1170~~		*'''TA:''' Borke Obada-Obieh (BorkeObadaObieh at cmail.carleton.ca): TBD
	*'''Meeting Time:''' Tuesdays and Thursdyas 10:05-11:25 AM, TB 238		*'''Meeting Time:''' Tuesdays and Thursdyas 10:05-11:25 AM, TB 238
	*'''Course Website''': http://homeostasis.scs.carleton.ca/wiki/index.php/Computer_Systems_Security_(Winter_2016)		*'''Course Website''': http://homeostasis.scs.carleton.ca/wiki/index.php/Computer_Systems_Security_(Winter_2016)

Soma: /* Hacking Journal */

2016-01-09T23:11:30Z

Hacking Journal

← Older revision		Revision as of 23:11, 9 January 2016
Line 51:		Line 51:
	The hacking journal is a journal of a student's explorations of computer security technology and methods (attacks and defenses) over the course of the semester. Every student should spend 3-4 hours a week on work that is documented in the hacking journal. The documentation may be concise and need not contain full sentences; however, it should cover the technical challenges encountered and the attempts to find solutions to those challenges (successful or not). It should also contain citations for any references consulted and help obtained from any other individuals.		The hacking journal is a journal of a student's explorations of computer security technology and methods (attacks and defenses) over the course of the semester. Every student should spend 3-4 hours a week on work that is documented in the hacking journal. The documentation may be concise and need not contain full sentences; however, it should cover the technical challenges encountered and the attempts to find solutions to those challenges (successful or not). It should also contain citations for any references consulted and help obtained from any other individuals.

	Students should be prepared to share their progress informally during class. The hacking journal will need to submit their journal twice: once on February 12th (before March Break) and once at the end of the semester.		Students should be prepared to share their progress informally during class. The hacking journal will need to submit their journal twice: once on February 12th (before March Break) and once at the end of the semester. You may maintain your hacking journal as one or many files, in any format you choose; for submission, however, you should if necessary combine them into one file that is either in text or PDF format.

	Hacking opportunities will be discussed throughout the class and kept track of [[SystemsSec 2016W Hacking Opportunities\|on the class wiki]].		Hacking opportunities will be discussed throughout the class and kept track of [[SystemsSec 2016W Hacking Opportunities\|on the class wiki]].

Soma: /* Hacking Journal */

2016-01-09T22:26:51Z

Hacking Journal

← Older revision		Revision as of 22:26, 9 January 2016
Line 48:		Line 48:

	===Hacking Journal===		===Hacking Journal===

			The hacking journal is a journal of a student's explorations of computer security technology and methods (attacks and defenses) over the course of the semester. Every student should spend 3-4 hours a week on work that is documented in the hacking journal. The documentation may be concise and need not contain full sentences; however, it should cover the technical challenges encountered and the attempts to find solutions to those challenges (successful or not). It should also contain citations for any references consulted and help obtained from any other individuals.

			Students should be prepared to share their progress informally during class. The hacking journal will need to submit their journal twice: once on February 12th (before March Break) and once at the end of the semester.

			Hacking opportunities will be discussed throughout the class and kept track of [[SystemsSec 2016W Hacking Opportunities\|on the class wiki]].

			While students may choose to focus on one project primarily, students should attempt at least one hacking project in each of the four major categories of material of the course, OS, Network, Software, and Web.

	===Assignments===		===Assignments===

Soma: /* Assignments */

2016-01-09T22:03:37Z

Assignments

← Older revision		Revision as of 22:03, 9 January 2016
Line 50:		Line 50:

	===Assignments===		===Assignments===

			The course assignments are based on the material covered in lecture and the assigned readings. They are short answer and should be submitted in PDF or text format via [https://carleton.ca/culearn/ cuLearn].

	===Midterm and Final Exam===		===Midterm and Final Exam===

Soma at 19:30, 9 January 2016

2016-01-09T19:30:02Z

← Older revision		Revision as of 19:30, 9 January 2016
Line 32:		Line 32:

	Students enrolled in COMP 4108 have the following grading scheme:		Students enrolled in COMP 4108 have the following grading scheme:

	~~'''NOT FINAL'''~~

	* 20% Class Participation		* 20% Class Participation
	* 20% Hacking Journal		* 20% Hacking Journal
	* 10% Assignments		* 10% Assignments
	* 20% Midterm (~~TBD~~)		* 20% Midterm (Feb. 25th, in class)
	* 30% Final Exam		* 30% Final Exam

	Each of these elements are explained below.		Each of these elements are explained below.

	==Class Participation==		===Class Participation===

	You are expected to attend every class for this course. Moreover, you are expected to participate in each class. This participation part of your grade will be based in part upon attendance; however, it will also be based upon the degree to which you were an active participant. Students who attend every class but who do nothing while in class will get a worse participation grade than those who miss some classes but who fully participate in those they do attend.		You are expected to attend every class for this course. Moreover, you are expected to participate in each class. This participation part of your grade will be based in part upon attendance; however, it will also be based upon the degree to which you were an active participant. Students who attend every class but who do nothing while in class will get a worse participation grade than those who miss some classes but who fully participate in those they do attend.
Line 49:		Line 47:
	Note that mini presentations and group work are part of class participation.		Note that mini presentations and group work are part of class participation.

	==Midterm and Final Exam==		===Hacking Journal===

			===Assignments===

			===Midterm and Final Exam===

	Students will be required to complete an in-class midterm exam and a formally scheduled final exam. These will be essay tests based on the material covered in class. Sample questions will be made available during study sessions prior to the exams.		Students will be required to complete an in-class midterm exam and a formally scheduled final exam. These will be essay tests based on the material covered in class. Sample questions will be made available during study sessions prior to the exams.