<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://homeostasis.scs.carleton.ca/wiki/index.php?action=history&amp;feed=atom&amp;title=SystemsSec_2016W_Lecture_9</id>
	<title>SystemsSec 2016W Lecture 9 - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://homeostasis.scs.carleton.ca/wiki/index.php?action=history&amp;feed=atom&amp;title=SystemsSec_2016W_Lecture_9"/>
	<link rel="alternate" type="text/html" href="https://homeostasis.scs.carleton.ca/wiki/index.php?title=SystemsSec_2016W_Lecture_9&amp;action=history"/>
	<updated>2026-06-02T23:06:12Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.42.1</generator>
	<entry>
		<id>https://homeostasis.scs.carleton.ca/wiki/index.php?title=SystemsSec_2016W_Lecture_9&amp;diff=20724&amp;oldid=prev</id>
		<title>Josiah: Added info from lecture</title>
		<link rel="alternate" type="text/html" href="https://homeostasis.scs.carleton.ca/wiki/index.php?title=SystemsSec_2016W_Lecture_9&amp;diff=20724&amp;oldid=prev"/>
		<updated>2016-02-18T00:11:41Z</updated>

		<summary type="html">&lt;p&gt;Added info from lecture&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;&lt;br /&gt;
== Topics ==&lt;br /&gt;
&lt;br /&gt;
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&amp;#039;t understand the types of threats they are defending against. Email is a large security hole as it is the &amp;quot;key&amp;quot; to many different accounts related to that person.&lt;br /&gt;
&lt;br /&gt;
== Defensive Security Technologies ==&lt;br /&gt;
&lt;br /&gt;
* OpenSSL&lt;br /&gt;
* Anti-virus (commercial) + suites (can you set off/engage AV? - potentially dangerous)&lt;br /&gt;
* Password managers (key chains)&lt;br /&gt;
* Web validation libraries&lt;br /&gt;
* Whole disk encryption (basic usage, recovery, forensics/security analysis - is it actually encrypting your drive, what key is it using?)&lt;br /&gt;
* Host firewall&lt;br /&gt;
* Network firewall&lt;br /&gt;
* Application firewall (web proxy, maybe  get Tor running as a client/node)&lt;br /&gt;
* 2-factor authentication&lt;br /&gt;
* Captcha&lt;br /&gt;
* SSO, kerberos, OpenID, OAuth&lt;br /&gt;
* Network file systems&lt;br /&gt;
* Biometrics&lt;br /&gt;
* Intrusion detection systems - snort, log analysis&lt;br /&gt;
  &lt;br /&gt;
== Notes ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* People make a threat model and security mechanisms and provide others with their security mechanisms, but people who use it don&amp;#039;t understand the attacks/defenses as they are not security experts, and then they undermine the security technology for easy use.&lt;br /&gt;
* Not applying enough defensive technologies in hacking journals.&lt;br /&gt;
* Phones have 2 OS, one is the on you interact with, the other is the phone&amp;#039;s baseband processor OS, created by the telecom companies which has legacy code and hard to change or run a security audit.&lt;br /&gt;
* Facebook/google don&amp;#039;t just provide SSO to be nice, they track where you sign on.&lt;br /&gt;
* Facebook creates shadow profile of you if you are not on facebook but are being referred to.&lt;br /&gt;
* System security is about the mindset.&lt;br /&gt;
* People who are good at breaking into systems are not necessarily good at securing systems.&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
== Hacking Opportunities ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Can you engage/set off your anti virus?&lt;br /&gt;
* Try using whole disk encryption, recovering from forgetting your password, forensics/security analysis - is it actually encrypting your drive, what key is it using?&lt;br /&gt;
* Use Tor as a client or node - although don&amp;#039;t use Tor and a regular web browser, web browser will track you.&lt;br /&gt;
* Play with 2-factor auth on gmail, text authentication, app authenticator, recover from cellphone being lost, where are recovery passwords stored? If you don&amp;#039;t like it, how would you protect against what it&amp;#039;s trying to protect?&lt;br /&gt;
* Captcha - set up use, crack captcha.&lt;br /&gt;
* Setup a SSO system on some VM&amp;#039;s.&lt;br /&gt;
* Setup a network file system with authentication, SMB/CIFS.&lt;br /&gt;
* Biometrics - use fingerprint scanner on phone, break it.&lt;br /&gt;
* Perform log analysis of system logs/application logs (i.e. snort logs), setup tools to filter and monitor logs&lt;br /&gt;
* PGP/GPG - sign + encrypt documents, verify software.&lt;br /&gt;
* 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?&lt;br /&gt;
* SSL/TLS certs - let&amp;#039;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.&lt;br /&gt;
* Just setting up defensive security technologies can take a few weeks of your hacking journal.&lt;/div&gt;</summary>
		<author><name>Josiah</name></author>
	</entry>
</feed>