<plug> (I host their web site, but have no financial interest in the software)
I missed the beginning of this thread so if SAFE/3000 has already
been mentioned, I apologize. It does have the ability to both audit
who has changed files (although not "what" they have changed within
the file), and restrict who can access the file in a particular mode.
You can get more information on SAFE/3000 at:
http://www.editcorp.com/Business/MontereySoftware/
</plug>
Regards,
Michael L Gueterman
Easy Does It Technologies
email: [log in to unmask]
http://www.editcorp.com
voice: (509) 943-5108
fax: (509) 946-1170
--
----------
From: Mark Landin[SMTP:[log in to unmask]]
Sent: Friday, April 04, 1997 6:32 AM
To: [log in to unmask]
Subject: Re: [HP3000-L] SOPHISTICATED SECURITY S/W FOR HP3000
In article <[log in to unmask]>, [log in to unmask]
says...
>
>Hi, HP3K Specialists ......
>
>My company is currently evaluating security software for HP3000 (MPE/iX
>5.0).
>
>We hv evaluated Security/3000, which is quite popular in the 3000
>environmentm, but we are looking for some sophisticated security
>features, that is,
>
><< ABLE TO TRACE WHICH USERS HAS MODIFIED A FILE IN MPE SYSTEM >>
>
Well, if you are talking IMAGE files then proper IMAGE logging will do that for
you. If you are talking other kinds of files, there may be some help for you in
the system logging subsystem. I know you can track file opens/closes...I don't
know that it does record-level modification tracking.
Hmmm...now I know XM (Transaction Manager) operates by keeping before/after
data images for files which are attached to it (through a special FOPEN call, I
believe)...usually just for IMAGE transactions. Normally your
other MPE files are not attached to XM, and XM to my knowledge does not have a
logging facility. However, you COULD attach the files you are most concerned
about to the XM...then the trick would be to get XM to retain it's before/after
images in a manner appropriate for periodic auditing.
Another option, again if you are interested in just some files, would be to
modify the applications (assuming you can) that affect them to do their own
logging.
Doesn't sound simple, does it? :)
--
Mark Landin
T. D. Williamson, Inc.
UNIX Sys. Admin
"If you take the smooth, you gotta take the rough" -- Rob Halford
|
