This is the Data Protection Privacy (DPP) guide for MediationZone. This document is designed to assist you , in understanding and implementing the necessary data protection measures when configuring personal data processing within the MediationZone platform.
As you implement the configurations and workflows necessary for your projects, this guide will serve as a resource for best practices and effective efficient data management strategies within MediationZone.
| Table of Contents |
|---|
| minLevel | 1 |
|---|
| maxLevel | 6 |
|---|
| outline | false |
|---|
| style | disc |
|---|
| type | list |
|---|
| printable | true |
|---|
|
...
Data Protection
...
Enabling Agents in MediationZone
You can use two different agents for data protection in MediationZone; Data Masking and Encryption.
Data Masking Agent
MediationZone offers data masking capabilities through its Data Masking Agentagent, ensuring that sensitive personal data is protected in compliance with data protection regulations. This With this agent facilitates you can both masking and unmasking of specified mask and unmask specific fields within User Data Records (UDRs), providing flexibility for batch and real-time data processing workflows.
Key Features:
Masking Methods: The Data Masking Agent utilizes a profileProfile-based approach, allowing providing you with a selection of specific methods for masking—Cryptomasking; Crypto, Database, or Hash. Each method is tailored to different operational needs and compliance requirements. Supported databases for the Database masking method include Oracle, Postgres, and SAP HANA.
Encryption and Decryption: Offers strong Strong encryption and decryption capabilities using AES-128 and AES-256 standards.
Key Management: Secure management of encryption keys through a JCEKS keystore.
Data Transformation: Ability to transform input data into random data using SHA-256 hashing.
Profile Management: Supports the use of Support for multiple profiles within the agent, enabling different configurations for various data handling requirements.
Error Handling and Logging: error Error handling and detailed logging mechanisms to track operations and troubleshoot issues.
For more detailed information on each feature functionality and configuration steps, please refer to see the Data Masking Agent section in the MediationZone documentation.
Encryption Agent
MediationZone offers encryption capabilities through its Encryption Agentagent. This feature functionality is crucial for protection of data in transit and at rest.
CapabilitiesKey Features:
Encryption standards: Implements Support for AES-128 and AES-256 encryption methods.
Key management: Encryption keys can be managed using the Secure management of encryption keys through a JCEKS keystore or an external keystore.
Data transformation: Employs SHA-256 hashing to anonymise data.
Detailed configurational guidelines are available in For more information on functionality and configuration, see the Encryption Agent section of in the InfoZone MediationZone documentation.
...
Guidelines for DPP compliance in workflows
MediationZone provides a suite of agents and profiles that enable customers you to store data temporary temporarily or permanently. These can be used for integrating data protection standards into their your workflows. Understanding how to leverage these agents effectively efficiently is crucial for maintaining compliance.
In the following sections, we describe the different agents and profiles that are typically used for storing data and the interactions that can be used guidelines for using them in a DPP context.
Archiving Agent, Profile and Inspector
| Expand |
|---|
Archiving Agent provides comprehensive data management capabilities. These agents support both archival and retrieval processes. Looking up Archived Data: Customers can use the Archive Inspector tool to look up Archived files. This tool is accessible through the Execution Manager and provides advanced search functionality that allows users to search for files within specified periods. Deleting Archived Data: The Archive Cleaner task is responsible for the automated deletion of outdated archives based on the purge criteria set within the Archive profile. Customers can manually trigger cleanup processes to ensure that data does not exceed its intended retention period.
Access more information by visiting Archiving section in the InfoZone documentation. |
...
| title | Exapand to read more about guidelines for the Archiving agent, profile and inspector. |
|---|
|
The Archiving agent provides comprehensive data management capabilities. |
...
This agent, profile and inspector support both archival and retrieval processes. |
...
...
...
...
...
...
...
...
...
...
on functionality and configuration, see the Archiving section in the |
...
MediationZone software description. |
Amazon S3 Forwarding
...
Agent
| Expand |
|---|
| title | Expand to read more about guidelines for the Amazon S3 aorwarding agent. |
|---|
|
The Amazon S3 forwarding agent provides capabilities to write data to S3. For best practices around data security |
...
...
see the Amazon S3 documentation. |
Data Veracity Forwarding Agent
...
| Expand |
|---|
| title | Expand to read more about guidelines for the Data Veracity forwarding agent. |
|---|
|
|
...
...
...
...
...
...
With advanced filtering and saved filters, you can streamline recurrent searches and improve efficiency in managing records. View and Inspect Data: Once records are located,
|
...
...
...
...
user interface. This action flags the records but does not remove them from the database. Force Deletion: For immediate removal,
|
...
...
Force Delete option available to administrators. This option should be used with caution, as it permanently removes the record from the database, ensuring that sensitive data is irrecoverable. Automated Cleanup via Maintenance Task: Configure the DataVeracity_Maintenance system task to automatically remove records that have been marked for deletion. This task can be
|
...
...
...
...
...
...
...
...
...
...
See the specific documentation provided by each database platform provider. Implement encryption and secure data handling practices as recommended: |
...
For more information on functionality and configuration, see the Data Veracity section in the |
...
MediationZone documentation. |
Error Correction System
...
| Expand |
|---|
| title | Expand to read more about guidelines for the Error Correction System. |
|---|
|
|
...
Use the ECS Inspector's Search function to find specific UDRs or batches. You can filter searches based on various criteria such as workflow, agent, error code, or insert period. Advanced search options allow for more detailed filtering, including the use of wildcards and intervals for specified fields. Using Saved Filters: For frequent searches, you can save your search settings as filters for quick future access. This is particularly useful for regularly monitoring or auditing records that meet specific criteria.
|
...
...
Search function, you can selectively delete entries. Ensure that the records are in a reprocessed state, as only reprocessed entries can be safely removed without affecting ongoing processes. Bulk Deletion: For managing larger volumes of data, the Bulk Edit feature allows you to delete multiple records simultaneously. This tool is ideal for removing batches of sensitive information efficiently. Scheduled Cleanup: Use the ECS Maintenance System Task to set up automatic purging of outdated or unnecessary records. This can be configured to remove records based on their reprocessing state and can be tailored to ensure compliance with data retention policies.
|
...
Secure Management: Restrict Field Edits: To prevent unauthorized modifications, configure restricted fields to protect sensitive data within UDRs from being edited. Monitor and Audit: Regularly review the ECS Maintenance logs and use the statistics reports to ensure that deletions and data management practices comply with organisational security policies.
|
...
...
on functionality, see th Error Correction System section in the |
...
MediationZone documentation. |
SQL Forwarding & Processing
...
Agents
| Expand |
|---|
| title | Expand to read more about guidelines for the SQL forwarding and processing agents. |
|---|
|
|
...
...
Use the SQL Forwarding Agent to execute SQL DELETE commands. In the agent’s configuration dialog, enter SQL statements specifically designed to target and delete sensitive records. Example: DELETE FROM customer_records WHERE customer_id = $(UDR.CustomerID);. Dynamic Data Handling: Leverage MIM values and UDR field variables in your SQL statements to ensure that only the intended records are targeted for deletion, enhancing security and precision. Stored Procedures Support: For complex deletion requirements, configure the agent to call stored procedures that encapsulate deletion logic. This approach enhances security by abstracting the deletion logic into the database layer. Example SQL call: CALL secure_delete_procedure($(UDR.CustomerID));.
|
...
...
on functionality and configuration, see the SQL Agents section in the |
...
MediationZone documentation.. |
Disk Forwarding Agent
...
| Expand |
|---|
| title | Expand to read more about guidelines for the Disk forwarding agent. |
|---|
|
|
...
forwarding agent to store files in secured directories. Ensure that these directories have appropriate permissions set to prevent unauthorized access. Use secure file system permissions and regularly audit access rights. Path Configuration: Carefully define and regularly review the paths used for storing
|
...
...
...
...
...
...
option to prevent the creation of unnecessary data files. Retention Policy: Define and enforce a data retention policy specifying how long files should be retained in both temporary and permanent storage. Automate the deletion of files that are beyond their retention period to prevent accumulation of outdated sensitive data.
|
...
...
...
...
...
...
on functionality and configuration, see the Disk Forwarding Agent - Batch section in the |
...
MediationZone documentation. |
Database Forwarding Agent
...
| Expand |
|---|
| title | Expand to read about guidelines for the Database forwarding agent. |
|---|
|
|
...
...
...
...
...
whenevr possible, as they allow for better control of the data manipulation logic and can encapsulate business rules and data validation steps. Transaction ID Management: Implement transaction ID management to ensure that each batch operation can be uniquely identified and managed. This helps in maintaining data integrity, particularly in rollback scenarios and inter-workflow communications.
|
...
...
...
...
...
...
...
forwarding agent. Audit logs should capture key details about the transactions, including transaction IDs, timestamps, and user IDs
|
...
...
For more information on functionality and configuration, see the Database Forwarding Agent section in the |
...
MediationZone documentation. |
Batch-Based Real-Time Agents
...
| Expand |
|---|
| title | Expand to read about guidelines for the batch-based real-time agents. |
|---|
|
|
...
use secure protocols like SSH2 for encryption. Cryptography: Regularly update and manage cryptographic measures such as public and private keys, ensuring that keys are rotated and managed according to security policies.
|
...
...
...
Use the agent's capabilities to retry connections and resume interrupted transfers securely. Prevention of Data Corruption/Loss: Configure agents to handle decoding errors and connection retries appropriately to prevent data corruption or loss.
|
...
...
Audit and Compliance: Auditing Data Transfer: Regularly audit data transfers, access logs, and security settings to ensure compliance with data protection policies. Use built-in logging and event management in agents to track and monitor all activities.
|
...
...
on functionality and configuration, see the Batch-Based Real-Time Agents section in the |
...
MediationZone documentation. |