TrustedBSD Audit Project

[Andrew R. Reiter]

TrustedBSD Audit Project
------------------------

Introduction

The purpose of this project is to design and implement the audit system
for TrustedBSD.  This document is meant to describe the thoughts and goals
behind the project and provide a basis for the design document.  The design
document will the guideline for the implementation and hopefully we can all
get it ready within the next couple of weeks, or however long deemed necesary
by possible mailing list discussions.  Discussions have been taking place 
between Logan Gabriel, Andrew Reiter, Robert Watson, and Stephanie Wehner 
and we felt it was best to move the conversations and design talk to an 
open forum.  We encourage all to help in this process.


Thoughts & Goals List
---------------------

 - Develop functional, standards adhering, and optimized audit system
   for TrustedBSD.

 - Adhere to Posix.1e specification which defines an interface to a 
   trusted audit system.  
   - We should deviate and/or expand upon the specification where it is
     deemed by all to be necesary or uniquely helpful.

 - Design and Implement a possible alarm interface for alerting admins
   to critical problems, which can include something like storage space
   running out.

 - Research and possibly develop a new local filestore and local filesystem
   pair for the sole purposes of holding audit records.  The goal is to 
   maximize use of storage space and create the ability for optimized 
   audit record lookups. 
   - This includes topics like compression and format of the record on disk.

 - Research and implement remote logging capabilities.

This is meant to be an overview of the goals, but if you believe there is 
something worth seriously looking at that is not mentioned here, please 
email the list.



To Unsubscribe: send mail to majordomo at trustedbsd.org
with "unsubscribe trustedbsd-audit" in the body of the message