RE: Restrict ability to alter variables in debugger on production

>This will prevent them from
>changing production data.  

Changing production data isn't the only problem, it's changing values in
a running program. Take the example of a check run. You read the correct
name and payment from the database, but right before the write to the
print file you change the value of the name to "Walden" and the value to
"$1,000,000" and then after the print you change it back. This won't be
caught anywhere.

Vern, who is asking this question though. Is it coming from an actual
auditor or from someone preparing for the audit? The PCAOB seems to be
allowing a degree of "reasonableness" to be applied by the auditing
firms. Remember, you need to control, not prevent, access. Perhaps
something like a second set of eyes when debugging production programs
would be acceptable -- that is, when debugging production programs a
second programmer (or perhaps a manager, or someone from accounting, or
someone designated by the audit committee) must be present when the
debugger is running.

-Walden


------------
Walden H Leverich III
President & CEO
Tech Software
(516) 627-3800 x11
WaldenL@xxxxxxxxxxxxxxx
http://www.TechSoftInc.com 

Quiquid latine dictum sit altum viditur.
(Whatever is said in Latin seems profound.)