Requirements
Operating System
DATPROF Privacy requires one of the following:
Microsoft Windows 7 or later
Microsoft Windows Server 2012 or later
Additionally, the .NET Framework 4.8 must be installed, and the user installing the software must have the necessary permissions to install applications.
Hardware
CPU: x86 1 GHz or more
Memory: At least 4 GB RAM
Disk Space: At least 1 GB of free disk space
Supported Databases
DATPROF follows the software lifecycle guidelines set by database vendors. This ensures compatibility and support with the latest versions of database systems while maintaining the stability and reliability of the tool. By aligning with the database vendors' lifecycle, DATPROF ensures that its solutions stay up-to-date with new features, security patches, and performance enhancements.
Oracle | Version 11.2 and later |
---|---|
Microsoft SQL Server | Version 2008 (not for Runtime) Version 2012 Version 2014 Version 2016* Version 2017* Version 2019* Version 2022 and later* |
DB2 LUW | 10.5 and later |
DB2 for i | 7.2 7.3 7.4 |
DB2 for z/OS | 13.0 and later |
PostgreSQL | 9.5 and later |
MySQL | 8.0 |
MariaDB | 10.4 |
Azure SQL | Not applicable - SaaS solution. |
*Check the Powershell module remarks
Oracle RDBMS
Permissions and Roles
If the Privacy User is the TABLE_OWNER
Minimum System Privileges
CREATE SESSION
CREATE TABLE
Minimum Object privileges
EXECUTE permission on dbms_random package
EXECUTE permission on dbms_metadata package
Quota
Unlimited tablespace
If the Privacy User is not the same as the TABLE_OWNER these additional permissions are required:
SELECT on the tables to mask
REFERENCES on the tables to mask
ALTER on the tables to mask
CREATE ANY INDEX
DROP ANY INDEX
CREATE ANY TABLE
INSERT ANY TABLE
SELECT_CATALOG_ROLE
When you create your own procedures, functions, use sequences, or reference views in your scripts, it is essential to ensure that the Privacy user is granted the necessary permissions to access and execute these elements.
Microsoft SQL Server
Permissions
The user masking the database should have dbo permissions in the database targeted for data masking.
Powershell module dependency
To retrieve DDL information from Microsoft SQL Server, DATPROF Runtime uses a PowerShell module. Over time, Microsoft has replaced the original "SQLPS" module with the "SqlServer" module.
As of version 4.0, the SqlServer module is included with DATPROF Privacy and no longer needs to be installed manually.
Microsoft PowerShell version 5 or later is required to use the SqlServer module.
Open a PowerShell window on your system as administrator.
To check your current PowerShell version, run the following command:
CODE$psversiontable.Psversion
If the major version is lower than 5, you need to upgrade PowerShell. To do so, download and install Windows Management Framework version 5.x from the following link: Windows Management Framework 5.1
Linux systems
When using Runtime on a Linux system, PowerShell must be installed, and the SQL Server PowerShell module needs to be manually installed.
To install PowerShell on a Linux system, refer to the Microsoft documentation: Install PowerShell on Linux.
Once PowerShell is installed, follow these steps to install the SQL Server module:
Open a PowerShell window on your system (either as the user running Runtime or as root).
Execute the following command to install the required module:
CODEInstall-Module -Name SqlServer
This will install the necessary SQL Server module for PowerShell, enabling you to manage SQL Server from your Linux environment.
DB2 LUW
Requirements
To use DATPROF Privacy for DB2 Linux, Unix, and Windows (LUW), the following IBM software is required on the client PC:
IBM DB2 Data Server Driver Package
Once installed, DATPROF Privacy will use the 32-bit DLLs located in the subfolders netf40 or netf40_32. These DLLs are necessary for establishing a connection and working with IBM DB2 databases.
Permissions
The user responsible for masking the database must have the following permissions in the targeted database:
CONNECT: Permission to establish a connection to the database.
DATAACCESS: Permission to access the data within the database.
CREATETAB: Permission to create tables, which is required during the data masking process.
These permissions ensure that the user has the necessary access to perform data masking tasks effectively.
DB2 iSeries
Requirements
To use DATPROF Privacy with DB2 iSeries, you should have one of the following installed:
IBM i Access for Windows 7.1, or
IBM i Access Client Solutions
This software can be obtained from the IBM website.
Permissions
The user responsible for masking the database must have DBADM (Database Administrator) permissions in the database schema targeted for data masking.
DB2 for z/OS (Mainframe)
Requirements
In order to use Privacy with DB2 for z/OS databases, the user must possess their own db2jcc_license_cisuz.jar file - This is the IBM Data Server for JDBC and SQLJ license file that allows access to the database through the JDBC protocol. This is a separate license that must be acquired through IBM. This file must then be placed in the Drivers sub-folder of the Privacy installation folder. If this is not done, the user is greeted by the following error upon trying to test a connection to the database:
Permissions
The user masking the database requires admin level permissions in the database.
Azure SQL
Permissions
The user masking the database should have admin level permissions in the database targeted for data masking.
PostgreSQL, MySQL and MariaDB
Permissions
You should at least have select permissions on the tables to import.
To execute a scenario database owner permissions are required.