RE: Pre-Approved database changes

From: Karniotis, Stephen <Stephen.Karniotis_at_compuware.com>
Date: Fri, 18 Jun 2004 08:58:34 -0400
Message-ID: <8D81DA9D264CD311A60C0008C75D553B1775B0A1@cwus-dtw-pri02.compuware.com>

Jared:

From browsing SoX a while ago, I believe any change that does not destroy, provide access to, inhibit access to, or modify access to data is part of the pre-approved list, but can't be sure.

Things that I know can't be there are:

            Creating, modifying and removing users
            Creating, modifying and removing roles
            Creating, modifying and removing privileges on objects
            Creating, modifying or removing objects in the database (even

database links count here)

Things that can be included

Any operation that does not alter the integrity of the data or the security of the data

Any operation that is deemed maintenance such as exports, backups, reporting ==> Tuning is questionable because access to the database may be temporarily turned off

Hope this helps.

Thank You

Stephen P. Karniotis
Compuware Corporation
Direct: (313) 227-4350
Toll Free: (800) 462-7740 ext. 74350
Mobile: (248) 408-2918
Email: Stephen.Karniotis_at_Compuware.com
Web: www.compuware.com

-----Original Message-----

From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org]On Behalf Of Jared.Still_at_radisys.com
Sent: Thursday, June 17, 2004 5:00 PM
To: oracle-l_at_freelists.org
Subject: Pre-Approved database changes

Dear List,

Those of you with stringent change control standards, or are currently going

through Sarbanes Oxley, may be familiar with pre-approved changes.

Essentially, all changes will be logged to the change control repository.

Yes, all.

There will be a list of pre-approved changes. These are changes that may be performed without review by the change control board.

These are things that are naturally done throughout the course of the day as part
of normal DBA duties. These changes are of a nature that the outcome is always
predictable, and does not result in accidental downtime or outages, or have other
profoundly negative results.

Keep in mind that there is an assumed level of competence and some discretion involved on the part of the DBA. You could probably perform just about any database operation and cause problems if you don't know what you are doing or act as if you are the only user on the system.

Examples:

adding datafiles to a tablespace
changing storage parameters on an index or table modifying database statistics through collection or deletion create exports
create backups
online index rebuilds ( in the rare case that it is useful ) Vertex Tax Table loads( yes, I'm stuck with those )

These changes are assumed to occur on active database systems, and are not part of some other normally scheduled procedure, such as a data load.

I would like to add to this list, and will welcome all suggestions and/or corrections.

If it is substantial, I will post it somewhere that all can access it.

Thanks,

Jared

PS. It's due tomorrow. ;)

The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.

Please see the official ORACLE-L FAQ: http://www.orafaq.com

To unsubscribe send email to: oracle-l-request_at_freelists.org put 'unsubscribe' in the subject line.

--
Archives are at http://www.freelists.org/archives/oracle-l/
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html


-----------------------------------------------------------------

Received on Fri Jun 18 2004 - 07:57:17 CDT