Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-1569927.1
Update Date:2016-02-02
Keywords:

Solution Type  Technical Instruction Sure

Solution  1569927.1 :   VSM / SVA - Secure Erasure Of Customer Data On Return of Disk Drive or Box  


Related Items
  • Sun StorageTek VSM4 System
  •  
  • Sun StorageTek VSM5 System
  •  
  • Sun StorageTek V2X SVA Disk System
  •  
Related Categories
  • PLA-Support>Sun Systems>TAPE>Virtual Tape>SN-TP: VSM
  •  




In this Document
Goal
Solution


Applies to:

Sun StorageTek VSM4 System - Version All Versions to All Versions [Release All Releases]
Sun StorageTek VSM5 System - Version All Versions to All Versions [Release All Releases]
Sun StorageTek V2X SVA Disk System - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Goal

 What is the process to ensure secure customer data destruction on return of a VSM/SVA or VSM/SVA disk drive?

Solution

This is what occurs when an HDA is returned to Oracle.
                
        All HDD FRU/CRUs that are returned have the data erased as the first step in the test process. All drives that spin up go through test process and data erasure. The Blancco software is used.   Below is an excerpt of the product description:

       The Blancco Software ensures the secure erasure of customer data from HDD and SSD drives contained within supported Oracle systems. This software conforms to the Oracle mandated erasure algorithm using the US Department of Defense Sanitizing standard DoD 5220.22-M three-pass overwrite. 

 

When a VSM is returned / decommissioned the following is done: 

                   
        A special code release (Clean code) is loaded on the VSM.  The sole purpose of this code is making all customer data on the subsystem unaddressable.  Clean code can be applied (or   IMLed) into the machine when the VTSS product is deinstalled to ensure that customer data cannot be accessed when the subsystem is re-installed at another location. 

               Operation:
               Functional microcode writes customer data to backend storage.
               Mapping tables (pointers) contained in the functional track table are used to link customer data with physical locations on the back-end disks (Array + cylinder).  Without accurate mapping table information customer data becomes unaddressable.

               Clean code is loaded and IML’d similarly to functional code.
               When clean code is IML’d it destroys the machine’s configuration information. The configuration information includes the VTV inventory table, HDA grouping, and the access to the functional track-mapping table.  

               When the clean code IML finishes it will post a message to inform the CSE how many HDAs were cleaned.  The number of HDAs cleaned must be equal to the number of HDAs installed for the clean operation to have been successful.


                   
There is no certificate issued for either of these situations.


Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback