March 17, 2010, 12:22PM
Using Live Data In Development Is Risky
1 CommentThose charged with the care and feeding of
database information stores, beware: A new statistic tucked into a
comprehensive study of financial services firms' data protection
policies shows that even at the most security-aware organizations,
application developers still use live data in their development and
test environments including many in financial firms. Read the full article. [Dark Reading]
Recommended Reads
Commenting on this Article is closed.
Today's Most Popular
- Attackers Using Fake Google Analytics Code to Redirect Users to Black Hole Exploit Kit
- Google Releases Beta of Chrome for Android
- Flash With Sandbox in the Works for Firefox
- DDoS Attacks Take on Political Motivations as Attackers Evolve
- Anonymous Leaks FBI, Scotland Yard Phone Call Detailing Hacking Investigations
Most Commented Stories
Newsletter Sign-up
Take Our Poll
Follow Threatpost
 |  |  |  |
| Tumblr |
Comments
Hand wringing aside, there's no substitute for live data for app testing, because it contains numerous anomalies, misformatting, garbage characters, overloaded fields, unknown codes, etc. (inherited from prior apps that touched it) that will crash your app, making you look super bad in front of powerful end users. No data generation tool can deliver the precise data quality problems seen in large-firm datasets, so get over it. The developers are under NDA, and it makes no sense to do otherwise, as the field survey data clearly shows!