Study Guide for Final

This is simply a guide of topics that I consider fair game for the final. I don't promise to ask you about them all, or about any of these in particular; but I may very well ask you about any of these.

  1. Fundamentals
    1. Saltzer and Schroeder's principles of secure design
    2. The Harrison-Ruzzo-Ullman result
    3. Relationship of security policy to security
  2. Cryptography
    1. Types of attacks: ciphertext only, known plaintext, chosen plaintext, chosen ciphertext
    2. Types of ciphers: substitution, transposition, product (both substitution and transposition)
    3. Goal of ciphers; what makes a cipher theoretically unbreakable
    4. Caesar cipher, Vigenere cipher, one-time pad
    5. What the DES is, characteristics
    6. Public key cryptosystems
    7. RSA
    8. Confidentiality and authentication with secret key and public key systems
  3. User and System Authentication
    1. One-way hash functions (cryptographic hash functions)
    2. UNIX password scheme, what the salt is and its role
    3. Challenge-response schemes
    4. Attacking authentication systems: guessing passwords, spoofing system, countermeasures
  4. Access Control
    1. Multiple levels of privilege
    2. UNIX protection scheme
    3. ACLs, capabilities, lock-and-key
    4. MULTICS ring protection scheme
    5. MAC, multilevel (military) security model
    6. Differences between MAC, DAC, ORCON
    7. Bell-LaPadula model
  5. Integrity Models
    1. Biba's model
    2. Clark-Wilson model
    3. Chinese Wall model
    4. File signature generation (integrity checksumming, etc.) and checking
    5. Safe practises ("safe hex")
  6. Computerized Vermin
    1. Trojan horse
    2. Computer virus
    3. Computer Worm
    4. Bacteria
    5. Logic Bomb
  7. Network Security
    1. Internet Security Architecture model
    2. Public key management, including certificates, the binding of a name to a principal (user), and certificate management schemes
    3. Digital signatures (what it is)
  8. Security in Programming
    1. Unknown interaction with other system components
    2. Overflow (both numeric and buffer)
    3. Race conditions (TOCTTOU flaw)
    4. Environment (shell variables, UIDs, file descriptors, etc.)
    5. Not resetting privileges

You can also see this document as a Binhex Framemaker version 5 document, Postscript document, or a plain ASCII text document.
Send email to

Department of Computer Science
University of California at Davis
Davis, CA 95616-8562

Page last modified on 3/17/97