Project Title: Explaining and Recovering from Computer Break-ins

System Name: DERBI: Diagnosis, Explanation and Recovery from computer Break-Ins

Overhead Transparency Slides from a Selection of Presentations

• Principal Investigator Meetings
  • 1999 December 13-15, Arlington, VA: M-S PowerPoint (147K)
    Additional slide: Postscript, GIF, Large GIF
  • 1998 December 14-17, Lexington, MA: M-S PowerPoint (172K)
    Additional slide: Postscript, GIF, Large GIF
  • 1998 February 3-4, Annapolis, MD: HTML (10K; 40K GIF optional), PDF (62K), PostScript (464K) M-S PowerPoint (78K)
  • 1997 July 29-31, Menlo Park, CA: HTML (5K), PDF (49K), PostScript (141K), M-S PowerPoint (75K)
  • 1997 February 25-27, Savannah, GA: HTML (10K), PDF (24K), PostScript (74K), M-S PowerPoint (28K)
  • 1996 August 26-28, Santa Cruz, CA: HTML (5K)
• Conferences
  • Computer Misuse and Anomoly Detection IV (CMAD-4), 1996 November 12-14, Monterey, CA: PDF (14K), PostScript (36K), M-S PowerPoint (22K)
• Workshops
  • Adaptive Architecture Workshop: 1998 May 12-13, Menlo Park, CA: HTML (9K; 40K GIF optional), PDF (72K), PostScript (542K), M-S PowerPoint (52K),
  • Future Directions for Intrusion Detection: 1995 July 24-25, UC Davis: HTML (9K), PDF (38K), PostScript (97K), M-S PowerPoint (40K),

Notes on potential problems

• HTML: Conversion to HTML done in multiple steps: from M-S PowerPoint to M-S Word (RTF), then to HTML, and then substantial manual fixing was applied. M-S Office97 produces notoriously non-compliant HTML (starting with line 1: the lack of a DTD declaration).
  In case you suspect errors in our manual conversion, the major problems we tried to correct are:
  • The second and fourth levels of indenting are consistently missing their <UL></UL> delimiters (they appear one level too high, but in a smaller font). Presumably this applies to all even-number levels of indenting.
  • When you have a list (UL, OL) underneath a list-item (LI), the closing tag (<LI>) is supposed to come after the embedded list, not before it.
    Netscape 3.0 and IE3 do not do not barf on this error, but the next generation of browsers may be considerably more picky.
  • Myriad instances of problems with the placement of the beginning and ending tags, especially FONTs: For example, they are often just outside a tag they should be inside.
    Again, the common browsers (as of early 1998) do not complain about these problems.
  Another quality product from Microsoft.
  We used the W3C HTML Validation Service on these pages.
• Microsoft PowerPoint: The presentations were created in PPT 4.0, PPT 95 and PPT 97. We have attempted to convert all the presentations put on this site into PPT 4.0 because that is the most recent version that is widely usable by the software installed on the PC's and Macintoshes "in the community."
• PostScript:
  • Level 2, Version 3.0:
    The conversion specified "Level 2 with Level 1 compatibility", but we have not tested these files with older printers.
  • In conversion from PowerPoint, some presentations had their top-level bullets rendered as the letter "n", other places as underscore.
  • Orientation: the pages appear upside-down in some viewers. Look for the "Orientation" setting (or similar name) and try resetting it to "Landscape" or "Upside Down"
• PDF is derived from the PostScript files, and hence the conversion errors from M-S PowerPoint to PostScript also appear in the PDF files.

Plug-ins

• PDF: If your browser does not have a PDF viewer, you can get a free one for most common platforms: Adobe Acrobat(R) Reader.
  Warning: check the sizes before deciding whether, or when, to download -- the PC version is roughly 4MB.
• M-S PowerPoint: You can get a free viewer for M-S PowerPoint for some platforms from Microsoft Office Converters and Viewers. If you are unable to read the PPT files here, that site also has some converters to handle version incompatibilities.

Project Home Page

AI Center Home Page

SRI International Home Page