Sarbanes & Oxley ----> 'OOPS' and 'HANKY PANKY'

Dear James,

Sometimes DB2 integrity problems are accidents and sometimes
they're not. SOX auditors must assess the adequacy of internal
controls that monitor for both 'oops' and 'hanky-panky' risks.

SOX audits are retrospective, so enterprises with a Sarbanes-Oxley
compliance requirement must immediately erase any hint of
vulnerability to unobserved database 'hanky-panky.' Stitch-in-Time
Database Integrity Software does just that; the product even observes
and reports this kind of mischief:

              A.  first turn the audit security OFF,
              B.  accomplish the hanky-panky,
              C.  then turn the security back ON again.

That 'hanky-panky' approach tricks audit software that relies on
triggers ... but ... it will not escape the gaze of Stitch-in-Time:
   http://www.unbeatenpathintl.com/award/source/1.html

Stitch-in-Time will tell your security officer:

   1) WHO did it, and ...
   2) precisely WHEN they did it, and ...
   3) exactly WHAT they did, and ...
   4) HOW they did it

A free demonstration copy of the fully-functional software
is available.

This page: http://www.unbeatenpathintl.com/SO-act/source/1.html
includes a link to the official interpretation of the Sarbanes-Oxley
Act published by PCAOB, the Public Company Accounting
Oversight Board. (PCAOB is sometimes pronounced 'peek-a-boo').

Cheers,

Clare Holtham
Small Blue LTD
Voice line: (44) 1-737-824248
North American contact: (262) 681-3151
clare.holtham@xxxxxxxxxxxxxxx
www.smallblue.co.uk


----- Original Message ----- 
From: "James H H Lampert" <jamesl@xxxxxxxxxxx>
To: <midrange-l@xxxxxxxxxxxx>
Sent: Tuesday, August 24, 2004 1:02 AM
Subject: RE: Sarbanes & Oxley


> It was in response to a customer query about SOX compliance via
> QuestView's "audit trail print" function that we developed the new
> "Journal View" functionality: the former was never intended as anything
> beyond "oops prevention," while journaling a file is a much more robust
> way of keeping track of changes.
>
> --
> JHHL
>
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>