From: Joy Latten <latten@austin.ibm.com>
To: linux-audit@redhat.com, redhat-lspp@redhat.com
Subject: labeled ipsec auditing
Date: Thu, 5 Oct 2006 16:23:00 -0500 [thread overview]
Message-ID: <200610052123.k95LN0S9017784@faith.austin.ibm.com> (raw)
I am auditing when an ipsec policy is added and removed from the
Security Policy Database. Should I also add audit when an SA is
added and removed? SAs can quickly fill up log since there can be many of them
and they also have a lifetime associated with them that can result in
continuous renewal. I looked at how Paul implemented netlabel auditing,
but was wondering is there any specific info I should audit for
labeled ipsec?
Regards,
Joy
next reply other threads:[~2006-10-05 21:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-05 21:23 Joy Latten [this message]
2006-10-05 22:04 ` labeled ipsec auditing Steve Grubb
2006-10-05 22:15 ` [redhat-lspp] " Paul Moore
2006-10-09 19:09 ` Klaus Weidner
2006-10-09 19:15 ` Paul Moore
2006-10-09 19:30 ` Klaus Weidner
2006-10-10 23:25 ` Joy Latten
2006-10-11 0:00 ` Klaus Weidner
2006-10-11 13:38 ` Serge E. Hallyn
2006-10-11 18:07 ` [redhat-lspp] " Joy Latten
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=200610052123.k95LN0S9017784@faith.austin.ibm.com \
--to=latten@austin.ibm.com \
--cc=linux-audit@redhat.com \
--cc=redhat-lspp@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox