This content has been marked as final. Show 5 replies
Please look into data scrambling. Protects you if data is exported from the database. You can get more info on this via Metalink. They are also profile options in some APPs, they control when this information is displayed.
Pl see this link - http://blogs.oracle.com/stevenChan/2008/02/scrambling_sensitive_ebusiness.html
This is a separately priced product from Oracle. There are 3rd party solutions available also - see http://www.mentissoftware.com/prod_iscramble.html
If you have any plans to use "Oracle Application Management Pack for Oracle E-Business Suite", please note that the latest release is 3.1 -- See (Note: 982302.1 - Getting Started with Oracle Application Management Pack for Oracle E-Business Suite, Release 3.1) for details and for the additional patches you need to apply for data scrambling.
Thanks for the advice. I will check data scrambling. We don't use OAM for cloning. We also don't have budget for custom solutions. We don't user Applications Management pack either. I was hoping to run update statements on IBY_SECURITY_SEGMENTS as part of the cloning process.
I believe direct updating the tables, specially financials, in a no-no. Also, it's actually a violation into any PCI compliance.
With the CC encryption patch(i.e. without any tools for scrambling), E-Business/iStore/iPayment are PCI compliant -- atleast on companies that I know and worked with. Even though CC numbers are stored in a "clear text" format, the value is encrypted. Somebody would need the security key in order to decrypt numbers (passing thru Oracle Apps/ Database standard security) -- applies in PROD and any number of clone instance.