One of the primary uses of IRI FieldShield is to encrypt and decrypt sensitive data in database or flat-file columns. FieldShield relies on a passphrase to derive a symmetrical encryption key used at encryption and decryption time.
One of the biggest concerns with releasing a dataset is the risk that a potential attacker can identify the owners of particular records. Even though masking or removing unique identifiers, like names and Social Security Numbers, can reduce that risk substantially, it may still not be enough.
The “New Multi Table Protection Job …” wizard in IRI Workbench described in this article is one of the ways that IRI FieldShield product (or IRI Voracity platform) users can automatically mask personally identifiable information (PII) in database columns that are part of a foreign key relationship, and thus preserve referential integrity between the tables.
This article looks at sets from an informational processing perspective; what they are; how they are constructed; and, distinct ways in which data can be drawn from sets within IRI software products using the SortCL data definition and processing program; i.e.,
Data Privacy on Fire We’re still seeing data breach headlines burning across news outlets and social media, fast and hot:The Equifax Breach was Entirely Preventable – Wired States Investigate Experian Data Breach – Krebs on Security ‘Heartbleed’ Bug in OpenSSL Exposes Millions of Online Passwords – Reuters Millions of Target Customers’ Credit, Debit Card Accounts May Be Hit by Data Breach – NBC News Neiman Marcus Data Breach Worse Than First Said – New York Times Retailers Hit by Credit-Data Breach Smaller Than Target’s – Bloomberg News
And the fire burns on.