For Application Development & Delivery Professionals

Test Data Privacy Is Critical To Meet Compliances

Data Masking Can Help Protect Test Data

Why Read This Report

Using customer, employee, or other confidential data straight from production for testing or developing applications violates data privacy laws and regulations and makes that data a soft target for attacks. Data privacy is not just a concern for production systems; it extends to nonproduction environments, too, including test, development, quality assurance (QA), staging, and training databases — wherever private data resides. Although many database administrators (DBAs) and security and risk professionals are revisiting security policies for test data, most still are not securing such data. All enterprises dealing with private data in test environments should mask or generate test data to comply with regulations such as Payment Card Industry (PCI), the Health Insurance Portability and Accountability Act (HIPAA), Sarbanes-Oxley (SOX), and European Union (EU) as well as to protect against internal and external attacks.
US $ 2495
Become A Client

Get objective, pragmatic guidance that helps you make tough decisions and succeed in a complex world. Contact us to learn more.

Already A Client?
Log in to read this document.

TABLE OF CONTENTS

  • Test Data Privacy Often Gets Lower Priority Despite Exposing Private Data
  • Data Masking And Data Generation Can Help Protect Private Data
  • Ten Steps To A Successful Data Masking Initiative
  • The Data Masking Vendor Landscape Is Growing But Also Consolidating
  • RECOMMENDATIONS

    Data Masking Should Be Part Of Your Enterprise Data Security Strategy
  • Related Research Documents