FieldShield Features and Benefits
Some of What's Inside & Why You Should Care
Features / Benefits
IRI FieldShield helps you ahdere to both business rules and data privacy laws in a data-centric context.
Profile and protect database tables, flat files, and other sources at the column (field) level. Choose which columns remain clear as you secure the others with one or more supplied or custom data masking functions.
Consider some of the advantages of using FieldShield:
Sensitive data discovery
Find and classify PII, PHI, and other data matching pattern and fuzzy search criteria in databases, files, and dark data sources.
Protect faster and surer than other, bulk protection methods. Leave non-sensitive data in its original format and available for regular processing. Even if one field is compromised, the others stay safe with their own protection (vs. breaches where one password exposes all).
Rich functional choices
More than a dozen categories of protection functions allow you to make security decisions on the nature of each datum and considerations like: security level, reversibility, ciphertext appearance, and speed.
Cross-platform executable and libraries
Deploy concealment and revelation widely and easily, through bulk/batch, real-time applications, or through stored (SQL) procedures (e.g., in-situ encryption).
Database- and file-agnostic
Secure data at source and endpoints across multiple DB platforms and file formats with the same product and metadata, and/or at the same time.
Random value lookups
PseudonymizePIIusingdata from thesame or third-party source(s) to provide realism, safety, and the option of reversibility.
Cross-table masking rules
Define, enforce, and re-use protections for common-named tables and the data class libraries you identified across the database(s). Preserve referential integrity because common start values get the same end values.
National ID (NID) masking
Save research and design time in complying with de-identification requirements and local data privacy laws with standard and custom masks.
Hashing and tokenization
Validate the integrity and improve the security of encryption operations.
XML audit log file
Verify privacy law compliance efforts and support query and reporting of all runtime details.
Re-ID Risk Scoring
Reports based on peer-reviewed quasi-identifier analysis help data governance teams comply with the HIPAA Expert Determination Method rule and FERPA requirements for non-reidentifiability.
Blurring and generalization
Anonymize quasi-identifiers to reduce re-identification risk while retaining the data's research or marketing value.
Save protection design and execution time by protecting many different files and tables in the same job script and I/O pass. Consolidate multiple protections and authorizations in a single target, and thus reduce both throughput and data synchronization concerns; i.e., different people can reveal different fields from the same document.
FieldShield shares the data and job definition 4GLof its parent CoSort SortCL programs that you can run data protection with data transformation, migration, and reporting in the same job script and I/O pass if you have a CoSort package or Voracity platform license. You can also run and manage the open, self-documenting metadata outside IRI Workbench, and seamless team-share it through any source-code control system compatible with Eclipse™ (e.g., Git). AnalytiX DS and MIMB users can convert existing metadata in BI, CRM, DB, ETL, and modeling tools into the data definition file (.DDF) format that FieldShield uses to mask data used in those apps.
User-friendly job design options
Six different ways to create masking jobs in the same Eclipse front-end allows users to work in the style they prefer while reducing their learning curve in discovering and protecting data in disparate sources. Data layouts and field functions are self-documenting so data architects, DBAs, and compliance teams can easily design, modify, and verify jobs. The free Eclipse™ UI (IRI Workbench) eliminates the complexity and cost of proprietary design studios and DB-vendor-specific column encryption.