Home » Solutions » Field Protection » Filtering Redaction
Field-Level Filtering/Redaction 
Remove Sensitive Data from Tables, Files, Reports

Challenges:
Sometimes sensitive information is not needed for future processing steps, or is not allowed to appear in target tables, files or reports at all. In these cases, you must prevent private fields within your data sources from appearing in your output results.

While DBAs can remove columns in tables, most of the tools available for processing data in files or reports are either cumbersome or expensive, and cannot offer the ability to combine field-level redaction from flat files, much less combine that ability with other field-level protections like encryption, de-identification, or pseudonymous data masks.

Solutions:

If you are processing files, you can select which input fields will go to output reports and hand-off files on a need-to-know basis.

With either IRI's FieldShield package or CoSort SortCL tool, you can selectively omit records from your input or output files based on conditional evaluation logic, i.e., filtering. Or, you can simply not specify certain input fields in the output target, i.e., redaction.

These are just two field protection techniques among many available to FieldShield and SortCL users. Additional functions like encryption, de-identificaiton, and obfuscation are also possible on other fields at the same time. SortCL users have the additional option to perform standard data transformations and produce output reports in the same job script and I/O pass as the field protections.

See also:
Solutions > Field Protection
Solutions > Data Governance > Privacy Protection
Products > FieldShield
Products > FieldShield GUI
Products > CoSort > SortCL
Products > CoSort > SortCL > Metadata

Request More Info:

* IRI WILL NOT share this info