Computer Systems Security (Winter 2016)

2016-02-23T16:09:34Z

Josiah: Changed title of lecture 9

==Course Outline==

[[Computer Systems Security: Winter 2016 Course Outline|Here]] is the course outline.

==Hacking Opportunities==

The [[SystemsSec 2016W Hacking Opportunities|Hacking Opportunities]] page lists potential hacking opportunities that you can attempt for your hacking journal. If you attempt but do not successfully accomplish one of them, be sure to document what you tried. As you learn more, you may come back to them and try again.

==Resources==

===Readings===

* For the first part of the course we will be reading selections from Trent Jaeger's [http://www.morganclaypool.com/doi/abs/10.2200/S00126ED1V01Y200808SPT001 Operating Systems Security] textbook. You can download the PDF [http://www.morganclaypool.com.proxy.library.carleton.ca/doi/abs/10.2200/S00126ED1V01Y200808SPT001 through Carleton's library]. In the reading assignments this text will be referred to as "Jaeger".
* An excellent but dated text on browser security is Michal Zalewski's [https://code.google.com/p/browsersec/wiki/Main Browser Security Handbook].

===Other Courses===

* Dan Boneh ran an excellent course at Stanford in Spring 2015 on [https://crypto.stanford.edu/cs155/ Computer and Network Security]. This course has many interesting readings that we will not be covering. Also, the assignments are very good sources for hacking opportunities.
* The assignments from the Winter 2015 run of COMP 4108 [https://www.ccsl.carleton.ca/~askillen/COMP4108/ are available]. They are a reasonable start for several hacking opportunities.

==Lectures and Exams==

<table style="width: 100%;" border="1" cellpadding="4" cellspacing="0">
<tr valign="top">
<th>
Date
</th>
<th>
Topic
</th>
<th>
Readings
</th>
</tr>
<tr>
<td>
Jan. 7

</td>
<td>
[[SystemsSec 2016W Lecture 1|Introduction]]

</td>
<td>Jaeger, Chapter 1 (Introduction)</td></tr>
<tr>
<td>
Jan. 12

</td>
<td>
[[SystemsSec 2016W Lecture 2|Access Control, Security Hacking 101]]

</td>
<td>Jaeger, Chapter 2 (Access Control Fundamentals)</td></tr>
<tr>
<td>
Jan. 14

</td>
<td>
[[SystemsSec 2016W Lecture 3|Multics, UNIX, and Windows]]

</td>
<td>Jaeger, Chapter 3 (Multics) and Chapter 4 (UNIX & Windows) </td></tr>
<tr>
<td>
Jan. 19

</td>
<td>
[[SystemsSec 2016W Lecture 4|Secure OSs, theory and practice]]

</td>
<td>Jaeger, Chapter 6 (Security Kernels) and Chapter 7 (Securing Commercial Operating Systems)</td></tr>
<tr>
<td>
Jan. 21

</td>
<td>
[[SystemsSec 2016W Lecture 5|LSM, SELinux, & Capabilities]]

</td>
<td>Jaeger, Chapter 9 (LSM & SELinux) and Chapter 10 (Secure Capability Systems)</td></tr>
<tr>
<td>
Jan. 26

</td>
<td>
[[SystemsSec 2016W Lecture 6|Secure Virtual Machines, Systems Assurance]]

</td>
<td>Jaeger, Chapter 11 (Secure Virtual Machine Systems) and Chapter 12 (System Assurance)</td></tr>
<tr>
<td>
Jan. 28

</td>
<td>
[[SystemsSec 2016W Lecture 7|Lecture 7]]

</td>
<td></td></tr>
<tr>
<td>
Feb. 2

</td>
<td>
[[SystemsSec 2016W Lecture 8|Lecture 8]]

</td>
<td></td></tr>
<tr>
<td>
Feb. 4

</td>
<td>
[[SystemsSec 2016W Lecture 9|Defensive Security Technologies / Hacking Opportunities]]

</td>
<td></td></tr>
<tr>
<td>
Feb. 9

</td>
<td>
[[SystemsSec 2016W Lecture 10|Lecture 10]]

</td>
<td></td></tr>
<tr>
<td>
Feb. 11

</td>
<td>
[[SystemsSec 2016W Lecture 11|Modeling a potential attack/ Midterm FAQ]]

</td>
<td></td></tr>
<tr>
<td>
Feb. 23

</td>
<td>
[[SystemsSec 2016W Lecture 12|Midterm Review]]

</td>
<td></td></tr>
<tr>
<td>
Feb. 25

</td>
<td>
Midterm (in class)

</td>
<td></td></tr>
<tr>
<td>
Mar. 1

</td>
<td>
[[SystemsSec 2016W Lecture 13|Lecture 13]]

</td>
<td>Stack smashing, Stackguard</td></tr>
<tr>
<td>
Mar. 3

</td>
<td>
[[SystemsSec 2016W Lecture 14|Lecture 14]]

</td>
<td>ASLR, Return-oriented Programming</td></tr>
<tr>
<td>
Mar. 8

</td>
<td>
[[SystemsSec 2016W Lecture 15|Lecture 15]]

</td>
<td>Network Firewalls</td></tr>
<tr>
<td>
Mar. 10

</td>
<td>
[[SystemsSec 2016W Lecture 16|Lecture 16]]

</td>
<td>Application Firewalls</td></tr>
<tr>
<td>
Mar. 15

</td>
<td>
[[SystemsSec 2016W Lecture 17|Lecture 17]]

</td>
<td></td></tr>
<tr>
<td>
Mar. 17

</td>
<td>
[[SystemsSec 2016W Lecture 18|Lecture 18]]

</td>
<td></td></tr>
<tr>
<td>
Mar. 22

</td>
<td>
[[SystemsSec 2016W Lecture 19|Lecture 19]]

</td>
<td></td></tr>
<tr>
<td>
Mar. 24

</td>
<td>
[[SystemsSec 2016W Lecture 20|Lecture 20]]

</td>
<td></td></tr>
<tr>
<td>
Mar. 29

</td>
<td>
[[SystemsSec 2016W Lecture 21|Lecture 21]]

</td>
<td></td></tr>
<tr>
<td>
Mar. 31

</td>
<td>
[[SystemsSec 2016W Lecture 22|Lecture 22]]

</td>
<td></td></tr>
<tr>
<td>
Apr. 5

</td>
<td>
[[SystemsSec 2016W Lecture 23|Lecture 23]]

</td>
<td></td></tr>
<tr>
<td>
April 7

</td>
<td>
[[SystemsSec 2016W Lecture 24|Lecture 24]]

</td>
<td></td></tr>
<tr>
<td>
April 19, 9 AM

</td>
<td>
Final Exam

</td>
<td></td></tr>
</table>

==Assignments==
<table style="width: 100%;" border="1" cellpadding="4" cellspacing="0">
<tr valign="top">
<th>
Due Date
</th>
<th>
Assignments
</th>
</tr>
<tr>
<td>
Jan. 30

</td>
<td>
[[SystemsSec 2016W: Assignment 1|Assignment 1]]

</td>
</tr>
<tr>
<td>
Feb. 22

</td>
<td>
[[SystemsSec 2016W: Assignment 2|Assignment 2]]

</td>
</tr>
<tr>
<td>
Mar. 19

</td>
<td>
[[SystemsSec 2016W: Assignment 3|Assignment 3]]

</td>
</tr>
<tr>
<td>
April 4

</td>
<td>
[[SystemsSec 2016W: Assignment 4|Assignment 4]]

</td>
</tr>
</table>

==Lecture Notes Guidelines==

Part of your participation mark is doing notes for at least one of the lectures. Here are the guidelines for those notes.

The class TA Borke (BorkeObadaObieh at cmail.carleton.ca) will be handling course notes. Please contact her to schedule your class to take notes.

Borke or Anil will set you up with an account on this wiki. You'll enter your initial draft notes here and then work with Borke to make sure they are of sufficient quality. This may require a few rounds of revisions; however, if you follow the guidelines below it shouldn't be too bad.

You should plan on organizing your notes as follows:
* Organize them in at least the following sections: Topics & Readings and Notes.
* The Topics & Readings section lists the main topics covered in the class, e.g. "buffer overflows". Please use an unordered bulleted list (using *'s in wiki markup). In this section also list readings relevant to the lecture that were mentioned in class.
* Put your notes in the Notes section.

Use (nested) lists if appropriate for the notes; however, please have some text that isn't bulleted. Please try to make the notes even if you did not attend lecture; however, you don't need to cover every small bit of information that was covered. In particular the notes do not need to include digressions into topics only tangentially related to the course. Complete sentences are welcome but not required.

SystemsSec 2016W Lecture 9

2016-02-18T00:11:41Z

Josiah: Added info from lecture

== Topics ==

Many security solutions are unusable because they are too complicated. Focusing around a good threat model is important. There is a trade off between good security and cost. Better security means more restrictions and lower usability. The people who use security software often don't understand the types of threats they are defending against. Email is a large security hole as it is the "key" to many different accounts related to that person.

== Defensive Security Technologies ==

* OpenSSL
* Anti-virus (commercial) + suites (can you set off/engage AV? - potentially dangerous)
* Password managers (key chains)
* Web validation libraries
* Whole disk encryption (basic usage, recovery, forensics/security analysis - is it actually encrypting your drive, what key is it using?)
* Host firewall
* Network firewall
* Application firewall (web proxy, maybe get Tor running as a client/node)
* 2-factor authentication
* Captcha
* SSO, kerberos, OpenID, OAuth
* Network file systems
* Biometrics
* Intrusion detection systems - snort, log analysis

== Notes ==

* People make a threat model and security mechanisms and provide others with their security mechanisms, but people who use it don't understand the attacks/defenses as they are not security experts, and then they undermine the security technology for easy use.
* Not applying enough defensive technologies in hacking journals.
* Phones have 2 OS, one is the on you interact with, the other is the phone's baseband processor OS, created by the telecom companies which has legacy code and hard to change or run a security audit.
* Facebook/google don't just provide SSO to be nice, they track where you sign on.
* Facebook creates shadow profile of you if you are not on facebook but are being referred to.
* System security is about the mindset.
* People who are good at breaking into systems are not necessarily good at securing systems.

== Hacking Opportunities ==

* Can you engage/set off your anti virus?
* Try using whole disk encryption, recovering from forgetting your password, forensics/security analysis - is it actually encrypting your drive, what key is it using?
* Use Tor as a client or node - although don't use Tor and a regular web browser, web browser will track you.
* Play with 2-factor auth on gmail, text authentication, app authenticator, recover from cellphone being lost, where are recovery passwords stored? If you don't like it, how would you protect against what it's trying to protect?
* Captcha - set up use, crack captcha.
* Setup a SSO system on some VM's.
* Setup a network file system with authentication, SMB/CIFS.
* Biometrics - use fingerprint scanner on phone, break it.
* Perform log analysis of system logs/application logs (i.e. snort logs), setup tools to filter and monitor logs
* PGP/GPG - sign + encrypt documents, verify software.
* S/MIME - use in email service for encrypting email, need to get email certificate, how to get one and installing it on your email application?
* SSL/TLS certs - let's encrypt - new service for getting well supported SSL certs for everyone (valid for only 30 days but can be auto-renewed), use a self-sign cert - how does it work/how is it different.
* Just setting up defensive security technologies can take a few weeks of your hacking journal.

Soma-notes - User contributions [en]

Computer Systems Security (Winter 2016)

SystemsSec 2016W Lecture 9