In my opinion it is important to have privileges in test reflect
production/QA as well. In development often developers have elevated
privileges, which may lead to the use of objects in code that cannot be
accessed in the production environment. This is especially the case if
developers can use XE environments on their own workstations.
I have had several moments in the past where code was fully tested and
failed in production because the test user was granted near-DBA
privileges and the use of dynamic views and privileged packages was not
noted. It is not pretty when the DB nazi (me) has to reject a piece of
code on go-live day...
Cheers,
Tony
On 21/01/2016 7:35 am, MJ Mody wrote:
Oracle SMEs
My team and I are faced with a unique challenge/opportunity on how to best implement privileges appropriate for DEV, TEST, QA and PROD environments (e.g. Dev = Sandbox, Test = somewhat tightened, QA/Prod = same, etc.).
Reaching out to see if a Best Practice reference or STIG is available for the same.
Thank you in advance.
Best
MJ
--
//www.freelists.org/webpage/oracle-l
