NetNews Usenet Archive 1992 #18/NN_1992_18.iso/spool/vmsnet/misc/729

Internet Message Format | 1992-08-19 | 1.7 KB

Path: sparky!uunet!snorkelwacker.mit.edu!stanford.edu!rutgers!dziuxsolim.rutgers.edu!zodiac.rutgers.edu!leichter
From: [e-mail]
Newsgroups: vmsnet.misc
Subject: Re: How to boot VMS from a failed AUDIT writingREAD/NEW/FOLLOWUP
Message-ID: <[e-mail]>
Date: 19 Aug 92 12:27:59 GMT
References: <[e-mail]> <[e-mail]> <[e-mail]>
Sender: [e-mail]
Organization: Rutgers University Computing Services
Lines: 20
Nntp-Posting-Host: cancer.rutgers.edu

Terry Poot complains that the default configuration of the audit server makes
the system unbootable if the audit log fills.

This is really due to the DoD!  The audit server was designed around the DoD
secure system requirements as part of reaching C2 certification back in VMS
V4.5, or whichever version was actually certified.  A major requirement is
that all security-relevant actions be logged - and as part of that that the
system refuse to run when it cannot write log entries.  (I believe the certi-
fication actually included an exception because, if the log was being written
to a hard-copy device, it was possible for the system to continue if the
output device ran out of paper!)

Now, you can say that this feature should only be there if you ask for it.
However, the certification requirements must be met on the system AS IT
WOULD BE INSTALLED "OUT OF THE BOX".  Given the past history of systems that
are secure if you set them up right - but never seem to actually get set up
right - this is a wise policy.  Unfortunately, it means imposing a real
inconvenience on people who DON'T want this level of auditing.

                            -- Jerry-