For Application Development & Program Management Professionals

Primary Analyst Photo	Document Information	Rate this Document
	October 13, 2009 Test Data Privacy Is Critical To Meet Compliances Data Masking Can Help Protect Test Data by Noel Yuhanna with Mike Gilpin, David D'Silva	Average: 9  (3 ratings)

This is an excerpt

Executive Summary

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.

Keywords

• data privacy
• quality assurance
• database administrators

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

This is an excerpt