Re: Audit for program at login time
Date: Sun, 16 Mar 2008 16:09:45 -0700 (PDT)
Message-ID: <82345.91933.qm@web54112.mail.re2.yahoo.com>
Thanks for all the responses. It looks like I'll have to use a trigger after all ...
Adar - yes, duly noted about autonomous transaction in a trigger
Jared - sad but true, the program can be spoofed - risk is understood and accepted
Brandon - thanks for putting together an initial cut at an answer, wow! I too was surprised calling program wasn't included in the audit stream; in fact, I was so sure it was included, I didn't even bother checking before enabling auditing (oops).
Mary Elizabeth
- Original Message ---- From: Yechiel Adar <adar666_at_inter.net.il> Cc: oracle-l_at_freelists.org Sent: Sunday, March 16, 2008 7:56:50 AM Subject: Re: Audit for program at login time
If you use login trigger to insert the values into your table, do not forget to use: pragma autonomous transaction.
Adar Yechiel
Rechovot, Israel
Mary Elizabeth McNeely wrote:
> Hello all,
>
> I am tasked with auditing who accesses the database with what program (equivalent of v$session.program) upon database login. I can get everything I want into the audit trail by using "audit connect", except the equivalent of v$session.program.
>
> (a) Does anyone know of a supported way to push the program information into sys.aud$, and if not,
>
> (b) Does anyone know of a way to accomplish this other than a login trigger? Any sample code available?
>
> Thanks in advance for any hints you can offer.
>
> Mary Elizabeth McNeely
> --
> http://www.freelists.org/webpage/oracle-l
>
>
>
>
-- http://www.freelists.org/webpage/oracle-l -- http://www.freelists.org/webpage/oracle-lReceived on Sun Mar 16 2008 - 18:09:45 CDT