Re: [BPCS-L] Sox&BPCS

[Lisa.Abney@xxxxxxxxxxxxxxxxx]

Genyphyr ...

Interesting that you say that *ALLOBJ authority is NOT required ... even 
for 4.05 (non CD)?  (Technically, it's not that the user profile has 
*ALLOBJ authority ... we were instructed by SSA that the user profile has 
to have SSA as a group profile, and that profile has to have *ALLOBJ 
authority.)  I specifically asked that question of the SSA help desk about 
9 months ago, and was told that, while there was a  BMR available for 
later versions, it was not available for our version (although we might be 
able to retrofit it to make it work, etc.).  That e-mail from the help 
desk is what I used to document for our auditors why our profiles are set 
the way they are.

Lisa D. Abney
Manager Development Support
Sensient Technology
Phone:  (317) 240-1418





Genyphyr Novak <genyphyr.novak@xxxxxxxxxxxxx> 
Sent by: bpcs-l-bounces+lisa.abney=sensient-tech.com@xxxxxxxxxxxx
02/23/2005 02:52 PM
Please respond to
"SSA's BPCS ERP System" <bpcs-l@xxxxxxxxxxxx>


To
bpcs-l@xxxxxxxxxxxx
cc

Subject
Re: [BPCS-L] Sox&BPCS











Hello,

I would like to mention: BPCS does NOT require any user to have *ALLOBJ
authority to run the product. Even when it was recommended to use the SSA
group profile for users enrolled in BPCS this was not true. Nor do we any
longer require or recommend that the user enrolled in BPCS should have an
SSA group profile for any currently supported version of the product
including BPCS 4.05 CD. Be aware that any user can update BPCS data via 
use
of their PC even if they do not have command line access by use of ODBC
connections - so it is not secure if your AS/400 is linked to your PC
network.

There are BMRs out there (please see the archives for more on this topic)
delivering recompiled KRSO objects so that User Profile *OWNER is used, 
and
to secure the command line from adopting too much authority. These BMRs
ship with README instructions explaining how to use the recompiled 
objects,
along with an understanding and use of iSeries security features, in order
to properly protect your BPCS data files.

Thanks,

Genyphyr Novak
SSA GT R&D

message: 2
date: Tue, 22 Feb 2005 14:18:36 -0500
from: Lisa.Abney@xxxxxxxxxxxxxxxxx
subject: Re: [BPCS-L] Sox&BPCS

Danny ...

We passed our first Sarbanes Oxley audit in December with flying colors.
It was a LOT of work, but the work was on the development side ... change
control, developer access to objects, etc.  ... nothing to do with BPCS.
(And we are on 4.05 ... not a particularly current version!)  The only
thing they really questioned about BPCS was the fact that that release
runs with users having all object authority, but once we documented for
them that that was a requirement of the software, and that we control the
risks by the other security features we have in place (users not having
command line access, etc.), that was acceptable.  Is there something in
particular your auditors are questioning, with regards to BPCS?

Lisa D. Abney
Manager Development Support
Sensient Technology
Phone:  (317) 240-1418-- 
This is the SSA's BPCS ERP System (BPCS-L) mailing list
To post a message email: BPCS-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/bpcs-l
or email: BPCS-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/bpcs-l.

Delivered-To: lisa.abney@xxxxxxxxxxxxxxxxx