From: LC Bruzenak <lenny@bruzenak.com>
To: Valdis.Kletnieks@vt.edu
Cc: Linux-audit@redhat.com
Subject: Re: Auditing File Changes
Date: Mon, 10 Jul 2006 14:56:47 -0500 [thread overview]
Message-ID: <1152561408.4275.17.camel@fryspc> (raw)
In-Reply-To: <200607101942.k6AJgUo2016221@turing-police.cc.vt.edu>
On Mon, 2006-07-10 at 15:42 -0400, Valdis.Kletnieks@vt.edu wrote:
...
>
> Probably depends on what actual problem he's trying to solve by recording
> all the changes.
Most likely the same one I have been working on all my career:
Security guy: Please deliver system with maximum security.
System guy (me): What do you need to know?
Security guy: Any and all changes to security-relevant files.
System guy: Which ones are those?
Security guy: All of 'em.
Basically my plan is this:
As Steve Grubb said, instrument the processes with trusted access.
Have file watches which note when certain "critical" files are opened
for write/append.
Have an audit analysis program which compares the trusted accesses to
the total accesses; the delta shows potentially interesting mods.
LCB.
--
LC Bruzenak
lenny@bruzenak.com
next prev parent reply other threads:[~2006-07-10 19:56 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-10 17:29 Auditing File Changes eklinger
2006-07-10 17:42 ` Valdis.Kletnieks
2006-07-10 17:44 ` Steve Grubb
2006-07-10 19:32 ` Casey Schaufler
2006-07-10 19:42 ` Valdis.Kletnieks
2006-07-10 19:56 ` LC Bruzenak [this message]
2006-07-10 20:38 ` Valdis.Kletnieks
2006-07-10 20:51 ` Valdis.Kletnieks
2006-07-10 21:01 ` Klaus Weidner
2006-07-10 21:39 ` Casey Schaufler
2006-07-10 21:02 ` Timothy R. Chavez
2006-07-10 20:55 ` Timothy R. Chavez
2006-07-10 21:08 ` Timothy R. Chavez
2006-07-10 21:11 ` eklinger
2006-07-10 21:22 ` Valdis.Kletnieks
2006-07-10 21:37 ` Timothy R. Chavez
2006-07-10 22:09 ` eklinger
2006-07-10 23:37 ` Darren Cole
2006-07-11 12:56 ` Stephen John Smoogen
2006-07-11 13:20 ` Steve Grubb
2006-07-10 19:46 ` Klaus Weidner
2006-07-10 20:24 ` Casey Schaufler
2006-07-10 21:15 ` Klaus Weidner
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=1152561408.4275.17.camel@fryspc \
--to=lenny@bruzenak.com \
--cc=Linux-audit@redhat.com \
--cc=Valdis.Kletnieks@vt.edu \
/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.