DMOne™ Platformby eAppSysAI-enabled accelerator for Oracle Fusion
DMOne™ / Modules / MaskIQ™
DMOne™ platform module, stage 3: Protect

MaskIQ™

MaskIQ™ masks personal and financial data each time a non-production environment is refreshed, so test and training environments stay usable without exposing real records.

20+ masking techniques
Applied once and irreversibly
Aligned with UK GDPR and the Data Protection Act 2018

The problem

What goes wrong without MaskIQ™

Every refresh copies real personal and financial data into test and training environments. Either testers wait while it is masked by hand, or the data stays exposed.

ProblemHow MaskIQ™ solves it
Sensitive data copied with every refresh

Masking runs after each refresh or on demand, before testers and trainers have access.

Gaps in standard masking coverage

Coverage extends to HCM, Financials, Procurement, Projects, suppliers and customers, flexfields, attachments and photos.

Regulatory exposure in test environments

Masking is aligned with UK GDPR and the Data Protection Act 2018, with audit evidence for each run.

Inconsistent masking between environments

Named, versioned rule sets are applied per environment and reused for every refresh.

The solution

How MaskIQ™ solves it

Test and training environments are released to users sooner, because masking no longer holds them up.

  • Mask after each refresh or on demand, with progress tracked at each stage
  • Reuse the same versioned rule sets at every refresh
  • Let offshore and partner teams work on masked data from the start
  • Keep masked data realistic, so integrations can still be tested

In brief

The same module, explained for three readers.

For CXOs and data owners

Test and training environments without real personal or financial data, aligned with UK GDPR and the Data Protection Act 2018.

For project managers

Plan it into every production-to-test refresh and before UAT or training starts. Masking is applied once, with no delay to testing.

For solution architects

Runs against non-production environments after a refresh. Rules per field and entity, 20+ techniques, attachments, EITs and DFFs covered, referential integrity kept, every run logged.

What it does

Oracle coverage

HCM, project and financial records, supplier and customer data, extra information types and descriptive flexfields.

Attachment anonymisation

Removes sensitive data held in attachments across non-production environments.

Rules by environment

Different rules per field and entity for DEV, TEST, UAT and training.

Usable test data

Keeps referential integrity and statistical patterns, so calculations, testing and interfaces still work.

Audit trail

Records who masked what, when and how.

How MaskIQ™ works

Masking runs within your own OCI tenancy. Data is not sent to third-party systems.

  1. Extract

    Data is taken from the non-production Oracle Fusion environment.

  2. Hold securely

    Data stays within your own tenancy throughout.

  3. Mask

    Rules are applied, with checks before each job starts.

  4. Return

    Masked data is returned to Fusion, with progress tracked at each stage.

Detailed architecture, object lists and security documentation are available to clients and SI partners on request. Request the architecture pack

Coverage

People and HR

Personal details, flexfields, extra information, documents and photos

Finance and procurement

Supplier, customer and transaction details

Projects

Project names, descriptions and related records

Control and evidence

  • Versioned rule sets for each environment, reused at every refresh
  • Checks before each masking job runs
  • A before-and-after report for each run
  • Role-based access and a full audit trail
  • Updates aligned with Oracle Fusion releases

Release flow

  1. DEV

    Changes are built and registered in the pipeline.

  2. SIT

    Promoted automatically for system and integration testing.

  3. UAT

    Promoted for user acceptance with the same versions tested in SIT.

  4. Approval

    A named approver signs off; the decision is logged.

  5. PROD

    Deployed to production, with rollback available from the pipeline.

Where it fits

Every production-to-test refresh, and before UAT and training environments are opened up.

For SI partners

Partners use MaskIQ™ to give client testers and trainers safe environments, and to run masking as part of each refresh in support.

How the partner model works

Arrange a demonstration of MaskIQ™

We will demonstrate the module using a scenario from your programme.