RE: audit suggestion
- From: "Knight, Jon" <jknight@xxxxxxxxxxxxxx>
- To: "'ryan_gaffuri@xxxxxxxxxxx'" <ryan_gaffuri@xxxxxxxxxxx>, KATHERINE_KAYLOR@xxxxxxxxxx, oracle-l@xxxxxxxxxxxxx
- Date: Mon, 24 Jan 2005 13:04:30 -0600
Yeah, and call it "crun" ...
Jon Knight
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx]
On Behalf Of ryan_gaffuri@xxxxxxxxxxx
Sent: Monday, January 24, 2005 12:54 PM
To: KATHERINE_KAYLOR@xxxxxxxxxx; oracle-l@xxxxxxxxxxxxx
Subject: Re: audit suggestion
go around them. write your own job scheduler. its easy to do. its just an
infinite loop that polls on a certain directory. just have a data file that
tells it what to run and when. you can use the 'date' function to manage
time.
its pretty easy. you are technically not violating any rules by doing this.
What company did the audit? I will make sure not to hire them.
-------------- Original message --------------
> We just completed an external audit and one of the findings from the
> auditors is that DBAs should not have cron rights in Unix. The finding
> basically stated that a DBA could schedule something to run malicious
--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
Other related posts:
