Lawson Admin Segregation of Duties

Prev Go to previous topic

Go to next topic

Last Post 6/10/2014 1:33 PM by Leonard Courchaine

3 Replies

Sort:


You are not authorized to post a reply.

Author

Messages

Leonard Courchaine

(143 points)
Veteran Member
Posts:55

Send Message:

6/3/2014 5:28 PM
We're being pressured by auditors about breaking up into two the Lawson Admin who puts something (mod/CTP/Env Patch) into our Test environment and the Admin who puts it into Production. Our practice has been: 1. Dick puts quarterly patches into test; Harry puts environment patches into test. (user testing occurs) 2. Dick then puts quarterly patches into prod; Harry puts environment patches into prod. (All Lawson Admins have keys to test and prod e.g. the lawson password.) Auditors would like it if PersonA puts something into test and PersonB then puts it into production with Person A not having the ability to access production. Same with new custom mods that we put in. We'd LOVE to know how others are dealing with this type of auditor request around segregation/separation of duties with limited resources. Thanks so much, Lenny

Kwane McNeal
President
Private

(1437 points)
Veteran Member
Posts:479

Send Message:

6/4/2014 2:43 PM
Lenny, If you have one or two, and no more than two admins, typically I have seen clients do some variation to the following: 1) Document an audit exception, because the point of having two admins is one is a backup to the other. If you segregate one from PROD completely, you lose some of the benefit to fall back. 2) Setup a system to audit access to both the 'root'/'administrator' and 'lawson' accounts, by using 'su' (for UNIX), or some type of OTP (for Windows). Direct 'root'/'administrator' and 'lawson' access is forbidden, and the logs are sent to some other server the admins don't have access to. Kwane

Tim Cochrane
Private
Private

(450 points)
Veteran Member
Posts:154

Send Message:

6/6/2014 1:55 PM
Agreeing with Kwane - we've got a team of 5-7 System Admins: 5 on-site; 2 off-shore. ALL are expected to be able to handle ALL environments...otherwise they are worthless They typically work in pairs; one to make the changes and the other to validate. We're a large health care organization, so we've have to follow the same SOX requirements that you do. I don't know if our LSAs have to report anything to IA...never heard of them doing that...but our IA is comfortable with the process. Our Lawson Security group DOES have to make periodic reports to IA, so that might include any LSA activitiy, but i think the Security report is more around role/classes/user changes in LS. Kwane's worked with us before, he's seen how our system works. Tim Cochrane - Principal LM/IPA Consultant

Leonard Courchaine

(143 points)
Veteran Member
Posts:55

Send Message:

6/10/2014 1:33 PM
Guys, Thanks *very* much for your input. I'll pass it along. Seems very reasonable. Lenny

You are not authorized to post a reply.