Security for BPCS #8 ---> Stocking Stuffers for SOX

Dear Jim  ~  response #8,

This final response puts the wrapper on how Unbeaten Path
can help Badger Meter impress your SOX auditors. We've 
developed some clever and affordable products specifically
for BPCS that will knock the socks off your external auditors.

Please take a look at our "Stocking Stuffers (tm) for SOX"
http://www.unbeatenpathintl.com/SOXstuffers/source/1.html

You will find these ideas:

++ Internal Control Microscope Reports
      40 audit reports designed by experts in BPCS functionality
      and DB2 design. Even huge enterprises with exceptionally 
      deep, BPCS-savvy IS staffs have learned new things from 
      these reports.  

++ Locksmith Archiving for BPCS 
     You never want to tell a SOX auditor that the old records 
     have been purged, even if you have back-up tapes. Try our 
     free demo. 
  
++ Decipher Data Presentation De-mangler
      No SOX auditor will be impressed by the nonsense column
      headings and bad edit codes that arrive with vanilla BPCS 6.x 
      and 8.x. Our free demo will show you how you can fix the 
      missing decimal points, blanks instead of zeroes, huge numbers 
      instead of dates, etc., etc., etc. once and for all. 

God bless,

Milt Habeck
Unbeaten Path International

Toll free North America:  (888) 874-8008
International voice: (262) 681-3151
European contact: (44) 1-737-824248
mhabeck@xxxxxxxxxx   
www.unbeatenpathintl.com   



++++++++   +++++++   +++++++   +++++++   +++++++   +++++
From: Reinardy, James
To: bpcs-l@xxxxxxxxxxxx
Sent: Wednesday, June 09, 2004 3:17 PM
Subject: DB2 Users

Hello All,

We are running BPCS 6.04 on iSeries.  I am trying to understand the
relationship between iSeries users, BPCS users and DB2 file access. The
concern is arising because of Sarbanes-Oxley.  Our auditors are
suggesting that we need to lock down file privileges against the BPCS
database, but we are a little unclear about what user BPCS uses for data
access against DB2.  Is it the individual user that is logged into BPCS,
that user with a changed profile (SSA perhaps vs. *PUBLIC), or some other
generic user?

The idea here is to restrict access on a file by file basis for AS400Query,
SQL queries, ODBC connections, etc.  However, we want to be sure if
we lock things down that we don't break BPCS screens and batch
jobs.  Any suggestions on how to improve our understanding in this area
would be appreciated.

Regards,

Jim Reinardy
Director-IS
Badger Meter, Inc.