[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [redhat-lspp] labeled ipsec auditing



Quoting Joy Latten (latten austin ibm com):
> On Mon, 2006-10-09 at 14:30 -0500, Klaus Weidner wrote:
> > On Mon, Oct 09, 2006 at 03:15:09PM -0400, Paul Moore wrote:
> > > Going back to Joy's original mail I think it was the establishing or deleting of
> > > an SA with SELinux context that we were concerned about (at least that is what I
> > > was concerned about) as that could generate quite a bit of traffic.  Based on
> > > your comments above it looks like that is something we need to do.
> > 
> > Here's what Joy wrote: 
> > 
> > > 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? 
> > 
> > If I understand it correctly, SAs can also be added and removed manually,
> > and unless we forbid that admins do that, it would need to be audited.
> > 
> 
> Then do I only want to audit when an SA or SPD is manually added or
> deleted? Or just audit them regardless?

Hi Joy,

you didn't quote the part of Klaus' email which I was hoping you'd
answer:

> If the SPD completely determines the rules for ipsec related to MLS, it
> would not be necessary to audit the individual additions and deletions,
> but I'm not convinced that's the case. Does modifying the SPD
> automatically tear down any currently active SAs that do not match the
> updated policy?

-serge


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]