From: "Robert Potter" <robertp72@charter.net>
To: "'SELinux ML'" <selinux@tycho.nsa.gov>
Cc: "'Nick Gray'" <nick-lists@austin.rr.com>
Subject: RE: system auditing or event logging facilities
Date: Tue, 28 Dec 2004 19:02:13 -0800 [thread overview]
Message-ID: <000101c4ed52$cfed67c0$f2167144@Eng21> (raw)
In-Reply-To: <1104285346.22401.75.camel@hawaii.grays-systems.com>
For auditing and potential certification (like C2), visit InterSect Alliance
for their SNARE product, or look into Secure Auditing for Linux (SAL).
SAL is a DARPA project on SourceForge to develop a kernel level auditing
package for Red Hat Linux that is compliant with the Common Criteria
specifications (C2 level equivalency). It uses encryption to protect logged
data. While it is not ready to meet a C2 cert, you can see details of
progress and a comparison between common criteria and the current software
version at: http://secureaudit.sourceforge.net
You might also ask Trent Jaeger at IBM research for the latest info, as he
reads this list.
Regards,
Rob Potter
-----Original Message-----
From: owner-selinux@tycho.nsa.gov [mailto:owner-selinux@tycho.nsa.gov] On
Behalf Of Nick Gray
Sent: Tuesday, December 28, 2004 5:56 PM
To: SELinux ML
Subject: system auditing or event logging facilities
I am looking into C2/Capp auditing/event logging. Has there been any
work on this in regards to SELinux ?
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov
with
the words "unsubscribe selinux" without quotes as the message.
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2004-12-29 3:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-29 1:55 system auditing or event logging facilities Nick Gray
2004-12-29 3:02 ` Robert Potter [this message]
2004-12-29 13:31 ` Steve G
2004-12-30 6:06 ` SE-Linux File server Jayendren Anand Maduray
2005-01-03 13:48 ` Stephen Smalley
2005-01-04 5:50 ` Jayendren Anand Maduray
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='000101c4ed52$cfed67c0$f2167144@Eng21' \
--to=robertp72@charter.net \
--cc=nick-lists@austin.rr.com \
--cc=selinux@tycho.nsa.gov \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.