The Travelin' Librarian Uncategorized ICIW2008: Implementation of a Multilevel Wiki for Cross-Domain Collaboration

ICIW2008: Implementation of a Multilevel Wiki for Cross-Domain Collaboration

Cynthia E. Irvine, Naval Post Graduate School, Monterey, CA

  • Motivation
    • collaboration permits information sharing
    • attractive collaboration tool
    • can it be applied in an MLS environment
    • [M: don’t comment on Wikipedia’s “legitimacy”, not relevant here in the least]
  • objective
    • develop multilevel wiki
    • want high assurance policy enforcement
    • run it as untrusted subject outside of TCB
  • Testbed design slide
  • highlights
    • high assurance components
    • [“thin client running OS from a CD”???]
    • COTS components
    • Underlying server
      • BAE XTS-400
      • “{linux like” interface
  • background
    • more than 140 wiki engines available
    • aims
      • narrow list
      • select one or two to test
  • selection methodology
    • extensive public use
      • wiki engines
      • wikimatrix
      • wikipedia
    • considerations for MYSEA environment
      • execute on red hat 8
      • interface w/ apache
      • simple setup, flat-file system
    • other considerations
      • popularity
      • features
        • MediaWiki used as a baseline
  • Flat-file wiki list
  • Short-listed wikis features slide
    • PmWiki
    • TWiki
  • 2 determining factors
    • identity-based access control
    • concurrent editing
  • Decision
    • TWiki
    • better footprint
    • better user control
    • better editing
  • porting methodology
    • run on plain Red Hat 8
    • Port Wiki to XTS-400 for execution as a single-level subject
    • make multilevel aware
  • web-based collaboration support
    • logs into system
    • logs into wiki
    • user can read, edit, create
    • high users able to read and modify content at high, able to view at low
    • low users only able to read and modify wiki content at low, can link to high but not create high target
  • wiki design & architecture
    • directory organization
  • standard twiki architacture
    • apache runs as singe user
    • file system DAC
    • wiki DAC
  • MYSEA WebDAV DAC
    • Apache
    • MYSEA Apache Config
  • Implications
    • Users can bypass TWiki access controls by going directly to filesystem
  • Solution Space
    • run on dedicated server
  • Testing
    • conductedtesting at various stages
    • objectives
    • test plans conform to MYSEA documentation standard
  • Wiki in MYSEA visualization slide
  • Future work
    • Single signon
    • Multilevel data fusion
Tags:

Leave a Reply

Your email address will not be published. Required fields are marked *

 

This site uses Akismet to reduce spam. Learn how your comment data is processed.