Got Private Data?
FieldShield is powerful, affordable, and easy-to-use data masking software for structured data sources (DBs and flat files), big and small.
FieldShield shields fields with a choice of data protections in 12 different functional categories. FieldShield provides role-based access controls for personally identifying information (PII) and other sensitive data on a static or dynamic basis.
FieldShield jobs are expressed in simple, audit-ready job scripts front-ended in a user-friendly Eclipse GUI. Use it to:
- Profile, protect, present, and populate your data in a familiar integrated development environment (IDE)
- Protect data in one or more sources based on your business needs, the nature of the data itself, and column-name patterns
- Specify conditions and apply rules across tables
- Encrypt, de-identify and remove individualizing characteristics without cutting off access to non-sensitive data or changing its basic appearance
- Create an XML audit log to help verify compliance with HIPAA, PCI, and other data privacy directives.
Personally-identifying information (PII) is commonly stored in databases (DB), flat files, and applications like Excel that rely on them. Names, addresses, account and contact numbers, protected health information (PHI), and other sensitive data are in motion through DB and other applications, and at rest on networks and devices.
Whether in transit or at rest, proper stewardship of this data is required to avoid lawsuits, privacy law violations, and reputation damage.
If you process PII or PHI, are you responsible for protecting it? If so, you know that data = risk, and the physical and logical security measures already in place. Consider these questions:
- Are you safe from data breaches? Would the data still be safe if it were stolen?
- Does your department comply with data privacy regulations? Can you prove it?
- Do you protect only the data at risk, so you can see and use non-sensitive data?
- Can you easily protect different data elements with different protection methods?
- Does the protected data look real enough? Is it referentially correct?
- Can you use existing metadata during protection? Is that metadata for data and jobs portable?
- Can you seamlessly combine data masking with data transformation, migration or reporting jobs?
- Can you protect in real-time or DB applications (e.g. dynamic data masking, in-situ encryption)?
- How much money and time is spent on non-surgical protection; encrypting safe data or just one DB?