Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!husc6!necntc!ci-dandelion!ulowell!page
From: page@ulowell.cs.ulowell.edu (Bob Page)
Newsgroups: comp.unix.wizards
Subject: Re: UNIX classified operation
Message-ID: <1407@ulowell.cs.ulowell.edu>
Date: Thu, 18-Jun-87 17:32:18 EDT
Article-I.D.: ulowell.1407
Posted: Thu Jun 18 17:32:18 1987
Date-Received: Sun, 21-Jun-87 15:28:26 EDT
References: <175@uw-apl.UUCP>
Reply-To: page@ulowell.cs.ulowell.edu (Bob Page)
Organization: University of Lowell
Lines: 18
Keywords: UNIX, classified, DoD, audit

cel@uw-apl.UUCP (Curtis Lacy) wrote in article <175@uw-apl.UUCP>:
>New DoD requirements for classified computing require that we provide
>on demand an audit trail from which they can reconstruct all "actions
>to open, close, create and destroy classified files"

If 'audit trail' means a simple log of what happened to the file, when
and by whom, this is not too hard if you modify the library routines
to do the logging when they see some special flag in the inode.

If you mean be able to reproduce any file at any point in its lifetime,
it's a little bit harder than that.  :-)

This reponse is in the generic sense; I have not done any work in this
area, nor do I know people who have.

..Bob
-- 
Bob Page, U of Lowell CS Dept.   page@ulowell.{uucp,edu,csnet}