Re: "Copying" PF-DTA to client via RDi's "Make Available Offline" generates a .OAR file

On 3/18/2015 11:27 AM, Dan wrote:

The point of the exercise was to demonstrate to my manager that, whoever in
the organization (likely an auditor) put the clamp on using any dev-box
database function in Data Studio, Navigator, SQuirreL, Excel, or basically
any ODBC/JDBC tool we have here, for the express purpose of keeping our
very sensitive data secure, failed to understand that any developer with a
green screen can copy/paste this sensitive data into a client side file and
make off with it.

This has relevance to RDi in that many places consider their source code
to be Confidential. Auditors would like to ensure that a developer
can't make off with the source code (say to a competitor...) Yet, in
order to do their job, they need access to that source code, so what to do?

A combination of security and auditing is one compromise. A given
developer may be authorised to change source in library X, but not
library Y. This limits the amount of code any given developer can
access. By auditing who touches what source, you can keep a record of
accesses and match that up to authorised development projects. When
developer B starts looking at code that's unrelated to the project she's
working on, her manager can go find out why.

Substitute 'end user' for 'developer' and 'payroll records' for 'source
code' and the situation seems relevant.