Notes for February 11, 1998

1. Greetings and felicitations!
   1. Reading: Pfleeger, pp. 176-198; Garfinkel & Spafford, pp. 327-340
2. Puzzle
   1. Problem is remote execution of code (downloadable or otherwise)
3. Malicious logic
   1. Quickly review Trojan horses, viruses, bacteria; include animal and Thompson's compiler trick
   2. Logic Bombs
   3. Worms (Schoch and Hupp)
4. Review trust and TCB
   1. Notion is informal
   2. Assume trusted components called by untrusted programs

5. Ideal: program to detect malicious logic
   1. Can be shown: not possible to be precise in most general case
   2. Can detect all such programs if willing to accept false positives
   3. Can constrain case enough to locate specific malicious logic
   4. Can use: writing, structural detection (patterns in code), common code analyzers, coding style analyzers, instruction analysis (duplicting OS), dynamic analysis (run it in controlled environment and watch)
6. Best approach: data, instruction typing
   1. On creation, it's type "data"
   2. Trusted certifier must move it to type "executable"
   3. Duff's idea: executable bit is "certified as executable" and must be set by trusted user
7. Practise: blocking writing to communicate information or do damage
   1. Limit writing (use of MAC if available; show how to arrange system executables)
   2. Isolation
   3. Quarantine
8. Practise: Trust
   1. Untrusted software: what is it, example (USENET)
   2. Check source, programs (what to look for); C examples
   3. Limit who has access to what
   4. Your environment (how do you know what you're executing); UNIX examples
   5. Least privilege; above with root
9. Practise: detecting writing
   1. Integrity check files a la binaudit, tripwire; go through signature block
   2. LOCUS approach: encipher program, decipher as you execute.
   3. Co-processors: checksum each sequence of instructions, compute checksum as you go; on difference, complain