Profile and Protect Data at Risk
Nullify data breaches by masking PII in your DBs and files. Automatically find and classify it, then encrypt, pseudonymize, redact, and more while preserving its referential integrity.
Learn More
Comply with Data Privacy Laws
FieldShield de-identifies data subject to CIPSEA, DPA, FERPA, GDPR, GLBA, HIPAA, PCI, POPI, etc. It also helps you verify compliance via XML audit logs and re-identification risk scores.
Learn MoreProtect Data throughout its Lifecycle
Secure your data at every stage by applying FieldShield functions in IRI Voracity operations. Anonymize during data integration (ETL), federation, replication, testing, and analytics.
Learn More
FieldShield Use Cases
Payment Card Industry Data (PCI)
"FieldShield decrypts and re-encrypts fields in our credit card migration and test sources, and easily generates and manages encryption keys."
Learn MoreProtected Health Information (PHI)
"We continue to rely on FieldShield for flat-file and DB de-identification in order to comply with government healthcare privacy regulations"
Learn MorePersonally Identifiable Information (PII)
"We use FieldShield to anonymize HR data in complex file feeds, and to segment and substitute values based on field-level conditions."
Learn MoreComplete Data Masking
Every Source
- Flat Files
- RDB & NoSQL DBs
- Semi-structured Files
- Mainframe / Index Files
- S3, HDFS, MQTT, Kafka
Every Protection
- Encryption & Decryption
- Blurring & Scrambling
- Encoding & Decoding
- Pseudonymization
- Character Masking
- Randomization
- Hashing
- Expressions
- String Manipulations
- Tokenization
- Row/Column Removal
- Custom Functions
Every Deployment
- Command Line
- Eclipse GUI
- Batch/Shell Scripts
- System/API Library Calls
- In Situ/SQL Procedures
Learn More About FieldShield
What Others Are Reading
Data Masking vs. Data Encryption
Do you know the differences between them? Learn about these two popular forms of data obfuscation and when to use them.
Read NowWhich Masking Function is Best?
Read this review of the important decision criteria, including realism, reversibility, consistency, speed, and security.
Read NowPCI Tokenization in FieldShield
The Payment Card Industry Data Security Standard, or PCI DSS, requires encryption or tokenization of primary account numbers.
Read NowTake the FieldShield Quiz
- Do you collect or process PII or other "data at risk"? Do you know where (all of) it is?
- Is that data safe from a breach; i.e., could it be used were it stolen or exposed?
- Does your department comply with data privacy regulations? Can you prove it?
- Do you use multiple tools or methods to protect different DB columns in different ways?
- Can you protect only the data at risk, so you can see and use the non-sensitive data?
- Does your masked data look real enough? Is it referentially correct?
- Can you score your masked data sets for re-ID risk and anonymize quasi-identifers?
- Does it take too long to learn, implement, modify, or optimize your data masking jobs?
- Can you mask data in your ETL, subsetting, migration/replication, CDC or reporting tasks?