Skip to navigation

Available for Amazon RDS for PostgreSQL and Amazon Aurora PostgreSQL.

This article explains how data masking works when you restore a database in Eon.

Data masking replaces the values in columns that Eon classified as sensitive while it restores a database. Without masking, giving developers or testers a realistic copy of a production database means exposing real customer data. With masking, you restore the backup into a development or test environment and the sensitive values are already replaced.

What Eon masks

Eon masks the columns that data classification tagged with a data class, such as PII, FI, or PHI. Eon uses the resource’s latest classification results, not the results from when the snapshot was taken.

Masking changes values only, not the column type. Null values stay null. Replacement text is never longer than the original value, so a masked one-character value becomes *.

Masking covers only the columns that classification identified. Data masking is available for snapshots stored in Eon vaults only. Check the restored data before you share it.

Replacement methods

When you restore, you choose one of the following replacement methods. The replacement value depends on whether the value is a text value or another data type:

MethodText valuesOther values
Use fake dataReplaced with fake namesReplaced with random values of the same type
Mask with asterisks ***Replaced with ***Replaced with zero or empty values, such as 0, false, or 1970-01-01

With Use fake data, the same original value always gets the same fake value within a restore, so joins between masked columns still match.

Additional information