Title: Message
For all auto-scheduled jobs check the user account in which the job is started up. In most systems the security profile for an autoscheduled job can either be a nominated purpose built user account or (default) a root, superuser or adminstrator level account.
 
As the job will start up in the security context of the assigned account you need to ensure that an autostart fires up in the lowest degree of priviledge necessary to enable it to run successfully.
 
Regards
Stan Dormer
 
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of BRET CARPENTER
Sent: 21 February 2002 19:40
To: [EMAIL PROTECTED]
Subject: IT Automated/Robot Jobs

Fellow Auditors:
 
Has anybody ever done an audit on their "automated/robot" IT jobs.  I have found some issues where the "automated" jobs require the operator to input data (i.e. dates) to run the job.  In this case if the date is not keyed incorrectly the Job will run, but with the incorrect data.  I am now looking for compensating controls on this particular issue which is not a problem.  However, are there any other issues that you can suggest I look at when it comes to "automated" jobs run by IT operators or the system itself.  Any comments, concerns or programs would be much appreciated.
 
Thanks,
 
Bret Carpenter
Office 1-740-322-5660
Fax 1-740-322-5034
 
 

Reply via email to