RE: Restrict ability to alter variables in debugger on production

["John Earl" <john.earl@xxxxxxxxxxxxx>]

You're absolutely right Buck.  SOX is about process.

No one is saying programmers can't have access to production data.  What
the frameworks do say is that it must be reasonable, necessary,
measured, and auditable.  The days of unregulated full access to
production systems are rapidly departing.

Most of us are already doing the right thing when it comes to our data
access procedures, what SOX requires is that we document and prove that
we are doing the right thing.

jte

--
John Earl | Chief Technology Officer
The PowerTech Group
19426 68th Ave. S
Seattle, WA 98032
(253) 872-7788 ext. 302
john.earl@xxxxxxxxxxxxx
www.powertech.com 
 

 
This email message and any attachments are intended only for the use of
the intended recipients and may contain information that is privileged
and confidential. If you are not the intended recipient, any
dissemination, distribution, or copying is strictly prohibited. If you
received this email message in error, please immediately notify the
sender by replying to this email message, or by telephone, and delete
the message from your email system.
--

> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
> bounces@xxxxxxxxxxxx] On Behalf Of Buck Calabro
> Sent: Tuesday, November 16, 2004 12:15 PM
> To: midrange-l@xxxxxxxxxxxx
> Subject: Re: Restrict ability to alter variables in
> debugger on production
> 
> > All the solutions then point out to the fact
> > that there is no way anyone can fix anything
> > in a live environment without impinging on
> > SOX or data protection.
> 
> SOX mandates that you be able to produce a complete and
> verifiable
> audit trail of how the data were manipulated.  I have even
> heard of
> companies using video cameras or something like Camtasia
> to record a
> programmer's debugging/fixing session in the middle of the
> night.
> 
> The main thing to remember is that you need a documented
> process for
> handling these situations as well as a way to show that
> your people
> follow that process.
>   --buck
> 
> 
> 
> --
> 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.