Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

Is test environment sanitization practically feasible and what are the mechanisms of achieving the same?

April 26, 2017achieving Environment feasible mechanisms practically sanitization Test

0

Posted

Is test environment sanitization practically feasible and what are the mechanisms of achieving the same?

1 Answer

0

Posted

There’s some irony associated with *me* answering this question. First, what is meant by “sanitization”? Do you mean “keeping it clean” or “cleaning it up” after it gets “dirty”? The key to both questions is asset management. For example, if you are setting up a new environment, you want to have it only contain what you intend for it to contain. Usually, people don’t build completely isolated environments – they leave an outside connection somewhere to facilitate acquiring software packages etc. The problem with that is knowing that your firewall policy actually does protect you (and that is not always the case). Also, once you introduce something new into your test environment, you also have to know what that “something new” brought with it – i.e. – libraries, dependencies, etc. After you have your test environment set in wet jello, you start polluting it. Worst case scenario you are working with malware and you let a piece of malware execute. Now again you have to both understa