Follow Slashdot stories on Twitter


Forgot your password?
Slashdot Deals: Cyber Monday Sale Extended! Courses ranging from coding to project management - all eLearning deals 20% off with coupon code "CYBERMONDAY20". ×

Comment Re:Physical Security is a big issue (Score 2, Insightful) 325

Your "problem" has already been solved. Encrypt the hard drive. Companies don't care about losing sensitive data other than the monetary and reputation loss. If you lose a hard drive with private info on it, you only have to report a "breach" if it's encrypted.

Somebody with physical access can just use a boot CD and do what they want anyways.

Comment Analogy (Score 5, Funny) 230

Kid: "Mommy, can I go to the store by myself?"
Mom: "No, son."

5 minutes later

Kid: "Daddy, can I go to the store by myself?"
Dad: "Sure, son. Here's a dollar. Get a candy bar".

1 minute later

Kid: "I just mentioned it to him. I don't want to go anymore. Thanks, bye!"

Mom: *Result Pending*


Submission + - Test Environment/Data Business Problem

xmarkd400x writes: Hello. This is my first post to /., but I have been a reader for a while. Most of the posts on here seem intelligent (maybe that was my first mistake!) so I figured I would give these forums a shot.

I recently graduated from college with a CS degree, and I am now working for a large insurance company. I have been tasked with generating a report/professional recommendation about a test environment and test data. I will try to describe the situation as best I can, following with (hopefully) intelligent questions.

We currently have an environment where many different sorts of applications run. Some are web applications; some are internal applications, etc. We have a development environment, a test environment, and a production environment.

The production environment is a piecemeal hodgepodge of databases, web servers, load balancers, and other machines. The test environment is representative of the production environment, but it is smaller and different sections scale differently. The development environment really isn't important to this discussion.

We attempt to do both load and functional testing in the test environment; however, the two teams often run into each other and cause test results to be invalid. Also, when the two teams set up for tests, they will often over-write each others data, causing lost time and productivity.

The solution is two-fold. The performance test team wants a dedicated environment, but upper management doesn't want to spend the money. Secondly, the performance team needs a LOT of test data, but the production data is difficult to copy due to the variety of databases as well as the existence of sensitive information.

My questions are these:
  • Is it a "best practice" to have a test environment that equals the production environment in every way possible?
  • Are there any known tools for copying and obfuscating sensitive data (i.e. from production to test)?
Thank you in advance for your responses,

Anything cut to length will be too short.