Obfuscator
Obfuscator helps you reduce exposure of sensitive values by replacing selected Fields with masked, randomized, or placeholder values.
Use Obfuscator when you need a dataset that keeps the same general structure as the input File, but should not show the original sensitive values. Common examples include preparing a customer list, employee roster, vendor file, transaction file, or test dataset for broader review.
Obfuscator is designed for repeatable obfuscation. You create a Configuration, choose the Fields it should affect, define the Rules, preview the result, and then run the Tool against an input File or compatible dataset.
What Obfuscator is for
Obfuscator is a good fit when you need to:
- mask part or all of a text value
- replace text with a fixed value such as
Redacted - generate placeholder names or email addresses
- generate random characters for IDs, codes, or other text values
- replace whole numbers, decimal numbers, dates, or date/time values with randomized values
- create an output File that can be used for demos, testing, training, or limited sharing
What Obfuscator is not for
Obfuscator does not decide which Records belong in the output. If you need to keep or remove Records based on conditions, use Filterer before or after Obfuscator.
Obfuscator is also not a validation Tool. If you need to check whether values meet business requirements, use Validator.
Obfuscator changes selected values in the output. It is not meant to create a reversible lookup back to the original values.
Typical Obfuscator workflow
A common workflow looks like this:
- Confirm the File has an Import Config that describes the Fields Obfuscator can use.
- Create or edit an Obfuscator Configuration.
- Choose the Import configuration or Import Config shown on the screen.
- Add Rules and choose the Field each Rule should change.
- Choose the obfuscation method and settings for each Rule.
- Save the Configuration.
- Run Obfuscator with an input File or compatible dataset.
- Use Preview to compare original and obfuscated values before relying on the output.
- Review the Run completion details and download the obfuscated File.
Screen overview
Obfuscator includes these main areas:
| Area | What you do there |
|---|---|
| Obfuscator Configurations | Create, edit, run, and view history for saved Obfuscator Configurations. |
| Create Obfuscator Config | Name a new Configuration, choose source data, define Rules, and save the Configuration. |
| Edit Obfuscator Config | Update the Configuration name, Import Config, Rules, description, and revision. |
| Run Obfuscator | Name the Run, choose an input File or previous dataset, preview selected Fields, start the Run, and download output. |
| Obfuscator Job History | Review recent Obfuscator Runs, including status, imported Records, exported Records, problems, and cells changed. |
| Obfuscator Job Summary | Review one Run in more detail and download available output artifacts. |
Before you begin
Before building a Configuration, be clear about which values should be changed and what the output still needs to support.
Ask yourself:
- Which Fields contain values that should not be shared?
- Do users need to recognize part of the original value, such as the first or last characters?
- Should values look like names, email addresses, numbers, dates, or random codes?
- Does the selected Import Config include the Fields your Rules need?
- Will the obfuscated output be used for testing, demos, reporting, or handoff?
- Who will review the output before it is shared?
That clarity helps you choose Rules that reduce exposure of sensitive values without making the output harder to use than necessary.
Data handling note
WebHammers jobs run on your machine. Your data stays on your machine during Tool processing. WebHammers servers store Configurations so they can be reused, shared, and managed. A Configuration may include information such as the Field names from your data files.