Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Focus-Sun
[Top] [All Lists]

Re: Dealing with BSM Audit Logs

Subject: Re: Dealing with BSM Audit Logs
Date: Fri, 20 Oct 2006 13:42:13 +0200
The only tools I'm aware of are;

   - emerald expert-bsm    last release 2002 :-(
   -ISS Realsecure server sensor

In addition Solaris 10 supports now XML as output format which is supposed to be easier to parse, right?

bbr

Crist J. Clark wrote:
Sarbanes-Oxley has reared its ugly head. The word has come down
from on high that we need to know everything root does on the
affected systems. Using Solaris's built-in audit tools seems
like the obvious choice. So, I have,

        root:lo,ex,pc,fw,fm,fc,fd:no

In the audit_user file. Great. Most of the time this captures
what we want without too much cruft...

Most of the time. We had one system generate two GBs of logs
over two days (impractical). Now it is back to a few MB per day
(reasonable). I'm still trying to figure out exactly why, but
it looks like ufsdump/ufsrestore is hell on accounting. Not
for all of the files getting touched, as I first expected,
but rather to wild amounts of signalling (kill(2)) between
processes.

Anyway, I am in search of tools to deal with audit logs. For
example, I suspect that this noise is from ufsdump/restore,
but this is hard to back out. It'd be sweet to have a tool
where I could pull out all of the logs related to a process,
including its children, and look at them. Something interactive
would be so-o cool. Using auditreduce(1M) and praudit(1M) with
grep, perl, and awk only goes so far, especially when it
comes to GBs of logs.

Are there tools out there for this? Any leads, from Sun, free
stuff, your scripts, or third-party commercial, would help.

(Oh, and peeve with auditreduce(1M), it can't handle large
files?!)

<Prev in Thread] Current Thread [Next in Thread>