Database integrations
Validate dedicated read accounts for PostgreSQL, MySQL, MariaDB, SQL Server and Oracle. Browse schemas, tables and columns, then select a bounded export scope. Verified TLS is the default; credentials are encrypted.
Protect Identity | Data Masking
Data Masking
Enterprise
Discover sensitive information in databases, apply reusable protection policies and manage masked exports. Connect PostgreSQL, MySQL, MariaDB, SQL Server and Oracle, redact images and PDFs locally, and transform text, CSV or JSON in your Protect Identity workspace.
Core capabilities
Protect data before sharing.
Sensitive-field discovery
Sample up to 25 rows and inspect entity counts without returning original row values. Choose detection-based or whole-value protection for selected columns, including numeric identifiers.
Reusable masking policies
Select supported English entities, add custom detection patterns, choose confidence thresholds and override transformations per entity. Replace, mask, redact, salt-hash or produce tokens consistent within one job.
Images & PDF redaction
Use local OCR to identify sensitive text in PNG, JPEG, single-frame TIFF and PDF files. Export freshly encoded images or flattened PDF pages without the original text layer or attachments.
Managed jobs & exports
Track background jobs and policy versions. Export selected database data as CSV or JSON; protected artifacts are encrypted and expire after 24 hours. Failed and interrupted jobs never provide partial exports.
Text & structured data
Inspect detections and transform UTF-8 text, CSV or JSON using saved policies. JSON keys are retained; numeric JSON values must first be converted to strings. No external AI API is required.
In practice
A clear operating workflow.
Connect the initial context, the operational decision and the evidence you review.
Connect and discover
Validate a read account, browse the database structure and inspect sampled sensitive-field detections.
Define the protection
Save a policy with custom recognizers, entity-specific transformations and a confidence threshold.
Run a masking job
Select columns and row limits, or upload an image/PDF for local OCR redaction. Monitor the job in your workspace.
Review and export
Inspect the job scope and transformation counts, download the protected result and review it before sharing.
Install independently or add Data Masking to your Protect Identity deployment with a separately signed entitlement, dedicated encrypted state and a private processing service. Combined installations retain platform sign-in and MFA.
Automated English detection and OCR can miss sensitive data. Database jobs produce bounded read-only exports, with up to 10,000 selected rows and 32 columns; they do not modify source records. Documents support up to 6 MiB and ten PDF pages. DICOM de-identification, cloud storage crawling, scheduled runs, database write-back and recoverable encryption vaults are outside this release.
Before you get started
Questions,
answered.
Which databases can I connect?
PostgreSQL, MySQL, MariaDB, Microsoft SQL Server and Oracle Database. Configure a network route, dedicated read account and verified TLS trust from your self-hosted deployment. Oracle connections use a service name.
What is the enterprise price?
R15,000 per enterprise deployment per year excluding VAT. R17,250 including 15% VAT, with annual recurring billing through PayFast.
What is retained?
Database credentials and policies are encrypted. Original submitted source content is processed in memory. Protected export artifacts are encrypted and retained for 24 hours; job history records metadata and policy versions.
Does masking guarantee anonymous data?
No. Detection and OCR can miss sensitive information. Sampling cannot establish that an entire database is free of sensitive data. Review every export before sharing.
Protect Identity
See Data Masking in action.
Build a demonstration around your environment, operating priorities and evidence requirements.