Different SOD scenarios for Finance and HR/PR

As you are planning your LSF 9 migration, keep in mind that you don't have to do security at the same time. It is dictated by the checkLS flag in the security admin tool.

We used Lawson Security Accelerator so most of our segregation of duties were built in. We had internal audit involved and reviewing our security as we tested it. That helped ID anything we missed with cross over on segregation of duties. We also did a google search and found a SOX template that listed out many of the standard scenarios to make sure we covered them.

My big lessons learned from Security is that reguardless on how you roll it out, have it built to test cross functional. The ones that got us were the one off's that had their own LAUA security class with special rights to something. Integrating all of that with rules became the hardest part.

So you know about the different Lawson Security (LS9) options - I'm a bit biased, but I'll describe the options as best I can:

1) Build everything yourself!
This is the best way, but requires an enormous commitment and large effort on your company's part.

2) Use Lawson's Security Accelerator, which provides a pre-built LS9 configuration to match 60-70% of your needs.
The standard Lawson Security Reports include an SoD report that searches through your LS9 configuration for violations. You need to determine your SoD violations and which Lawson screens are involved, and define them in this report. This report is part of the delivered Lawson Security, so it's available regardless of which of these options you choose.

3) Kinsey & Kinsey Security Migration process, which automatically builds 90-99% of your LS9 configuration.
This includes an SoD analysis tool with 205 pre-built rules and various reports that show potential SoD violations in either LAUA or LS9.

Best regards,
Dave
(303) 773-3535