Mask existing sensitive data
Prepare a reviewed masking pipeline and inspect its output.
Use an explicit masking policy when preparing existing sensitive data for a test environment. A sensitive-field label alone does not mask values or certify that the output is safe to share.
Prepare the pipeline
- Select a read-only source connection and a small bounded extraction.
- Inventory sensitive fields and review the intended destination.
- Create a masking policy covering those fields, with the required consistency and reversibility choices.
- Dry-run representative data and inspect format failures, uncovered fields and warnings.
- Run the mask job, review its report and inspect the resulting dataset.
- Approve the specific load only after the output is ready, then verify delivery.
A useful request to the agent is:
Prepare a plan to extract a small customer sample from our read-only source, mask name, email and date of birth, and deliver it to the staging endpoint. Show the policy and a dry-run report before loading anything.
Step 3 is the one the agent does not do for you. It can read the policies a project holds and every rule in one, rehearse a policy against sample rows, run the mask and - with an approval granted for that specific key map - reverse a token. Authoring the rules stays in Masking, because those rules are what decides which real values are protected, and a field the policy does not list passes through the job unchanged.
Verify coverage
Unlisted fields can pass through unchanged, and free-text fields can contain sensitive values not obvious from their names. Review the actual output and warnings. Tokenization with reversal retains access to originals for authorized callers; treat that vault accordingly.
Keep source records out of chat, logs and shared workspace files. A transformation quarantine can also contain original values and needs restricted handling.
Retain evidence
Keep the policy, plan, run IDs, masking report and delivery checks together. These support your team's review; DataMaker completion status is not a legal compliance determination.
See Approvals, Audit and Reconciliation.