Frequently Asked Questions

What are the installation requirements for Camouflage?

Camouflage can be installed in any environment that has the following:

What type of databases does Camouflage support?

Camouflage is database independent, allowing it to connect to a number of different database types. Camouflage runs against Oracle®, DB2® UDB, SQL Server®, Sybase ASE®, MySQL®, HSQLDB and Teradata®. The software has support for various mainframe systems including DB2®, VSAM, IMS and QSAM (Flat Files).

On which platforms does Camouflage operate?

Camouflage is built on the open standards of Java, JDBC, and XML, allowing it to operate against a number of platform types and enabling project files to be transferred between operating systems. Supported platforms include UNIX®, Linux®, Windows®, MAC, z/OS and OS/390.

Does Camouflage support relational integrity?

Camouflage supports three levels of relational integrity including database RI, application RI, and cross database RI. If the relationships are defined at the database level, Camouflage automatically reads the database meta-data to enforce existing relationships. If the relationships are defined at the application level, Camouflage can be configured to enforce relational integrity. If the relationships are defined across databases, relationships can also be enforced across databases. Camouflage also allows users to maintain consistent data relationships across different applications.

Does Camouflage instill a repeatable methodology?

Camouflage saves all masking configurations in project files for database refreshes, future use and modification, and migration between different environments. The software can be invoked from the command line which also allows for integration with automated business and refresh processes.

Can Camouflage generate reports?

Camouflage incorporates reporting capabilities that enable clients to view before and after images of the masked data, to view masking configuration details, and to view impacted objects that have been modified by masking configurations.

Can users create custom transformers?

In addition to the predefined masking transformers, Camouflage encompasses a robust scripting capability that can be used alone, or in conjunction with the delivered transformers.

What security measures are built into Camouflage?

The username and password defined at the database level provides the access controls for Camouflage. Camouflage relies on the underlying operating system(s) and database(s) for access to sensitive data sources, and thus, only the top level IT personnel have access to Camouflage and the masking projects.

How is Camouflage typically deployed in an enterprise-wide environment?

Camouflage can be deployed in several ways, depending on the structure of the specific environment. The GUI and engine components of Camouflage can be installed directly on the database server or they can be installed directly on a client machine. Alternatively the two pieces can be installed in a mixed deployment environment, whereby the engine is installed directly on the server and the GUI is installed on the client machine.

Can masked data be traced back to its original values?

Camouflage has optional mapping tables which store before and after images of the masked data. These tables are stored in a secure location, and can be accessed or removed by senior level IT personnel only. By default, the mapping tables are deactivated for security purposes.