1. What is the exact nature of the problem trying to be solved with this request?

a) non-Encrypted volumes: Reformatting partitions does not necessarily delete information contained on the media. It is possible on a redeployed system to blind open a new file of a fixed, predetermined size without first wiping the content and capture information previously saved on the media possibly containing restricted data.

b) Encrypted volumes: Volume usage can be tracked and analysed when the encrypted volume is in an offline state by comparing null/non-null device content.

2. List the business requirements.

a) Systems that had access to sensitive/confident/secure information (i.e. payroll, accounting, HIPPA data, etc) are required to be wiped (nulled or randomized as appropriate to the storage technology) as part of the reimage/re-deployment process.

b) All encrypted volumes should be randomized prior to setup so as to mask actual encrypted volume usage.

3. Do you have specific timeline dependencies?

No specific timeline dependencies at this time. We currently "shred" (DBAN) storage volumes as a manual step prior to (re)imaging. This can be sometimes inconvenient as the null/randomize can take hours on larger volumes. If left to run overnight, the install process cannot be started until the next business day.

4. Can you please explain us the what are the functional requirements? If test cases can be provided this would be even more ideal.

After partitioning but before formatting a partition, the partition should be filled with (optionally) NULL (0) or random data.

5. Would you be able to assist in testing this functionality if implemented?

Yes.