SECURE AND SCALABLE SOLID STATE DISK SYSTEM

• US 20080279382A1
• Filed: 05/09/2007
• Published: 11/13/2008
• Est. Priority Date: 05/09/2007
• Status: Active Grant

• Current Assignee: Kingston Technology Corporation
• Original Assignee: Kingston Technology Corporation
• Inventors: Chen, Ben Wei, Tang, Choon Tak, Chien, Yungteh
• Granted Patent: US 8,499,168 B2
• Time in Patent Office: Days
• US Class Current: 380/277
• CPC Class Codes: G06F 21/79 in semiconductor storage media, e.g. directly-addressable memories

Abstract

A solid state disk system is disclosed. The system comprises a user token and at least one level secure virtual storage controller, coupled to the host system. The system includes a plurality of virtual storage devices coupled to at least one secure virtual storage controller. A system and method in accordance with the present invention could be utilized in flash based storage, disk storage systems, portable storage devices, corporate storage systems, PCs, servers, wireless storage, and multimedia storage systems.

Claims

1. A local command processor utilized in a solid state disk system (SSDS) comprising:

a processor; and

a local command list being executed on the processor, the command list including user provision commands, a get local status command; and

factory provision commands.

2. The local command processor of claim 1 wherein the user provision command is for use by the utility in the field application, the user provision command includes password utility commands and storage partition commands, wherein the factory provision command is for use in the factory to configure the SSDS, the factory provision commands includes a virtual storage processor commands, crypto-engine configuration commands, password attribute configuration commands and a test mode command.

3. The local command processor of claim 2 wherein factory provision commands comprise virtual storage processor configuration commands, crypto-engine configuration commands, password attribute configuration commands and a test mode command.

4. The local command processor of claim 3 wherein the virtual storage processor configuration commands include get virtual storage attributes command and set virtual storage command mode commands.

5. The local command processor of claim 3 wherein the crypto-engine configuration commands include a set crypto-mode command, an enable crypto-engine command and a get encrypted key command.

6. The local command processor of claim 1 wherein the user provision commands comprise password utility commands and storage partitions commands.

7. The local command processor of claim 6 wherein the password utility commands include a set password command, a change password command, authenticate password command, a set password list command, a get password list command, a get number of attempts commands and initiate a partition request commands.

8. The local command processor of claim 7 wherein the initiate a partition request command includes a set encrypted key command a get encrypted new key command.

9. The local command processor of claim 6 wherein the storage partition includes a get virtual storage attributes command, initialize partition size command and a format command.

10. A method for factory provision of a Solid State Disk System SSDS comprising:

load factory default settings on a secure virtual storage controller in the SSDS;

configuring the secure virtual storage controller;

configuring a crypto engine of the SSDS; and

enabling the crypto engine to allow for the use of the SSDS.

11. A method for configuring a virtual storage processor of a solid state disk system (SSDS), the method comprising:

setting the virtual storage processor in virtual storage mode;

aggregating the virtual storage based on a physical storage device list;

establishing a virtual storage device list;

building a physical to logical address table by the virtual storage processor based upon the device list; and

setting the status of virtual storage processor to ready.

12. A method for configuring a crypto-engine of a solid state disk system (SSDS) comprising:

issuing a set crypto-mode command;

issuing a set maximum number of attempts command;

issuing a get encrypted key command and providing a random key;

issuing a get master password command if a master password is required;

issuing a set master password command if a master password is required;

storing the encrypted key; and

setting a crypto-engine provision flag as ready.

13. The method of claim 12 wherein if a managed mode of the SSDS is set, the encrypted key is stored in a managed server, wherein if the managed mode of SSDS is not set the encrypted key is stored in a USB token.

14. The method of claim 13 wherein the crypto-engine can be disabled.

15. A computer readable medium containing program instructions for configuring a virtual storage processor, the program instructions:

setting the virtual storage processor in virtual storage mode;

aggregating the virtual storage based on a physical storage device list;

establishing a virtual storage device list;

building a physical to logical address table by the virtual storage processor based upon the device list; and

setting the status of virtual storage processor to ready.

16. A computer readable medium containing program instructions for configuring a crypto-engine in a Solid State Disk System SSDS comprising:

issuing a set crypto-mode command;

issuing a set maximum number of attempts command;

issuing a get encrypted key command and providing a random key;

issuing a get master password command if a master password is required;

issuing a set master password command if a master password is required;

storing the encrypted key; and

setting a crypto-engine provision flag as ready.

17. The computer readable medium containing program instructions of claim 16 wherein if a managed mode of the SSDS is set, the encrypted key is stored in a managed server, wherein if the managed mode of SSDS is not set the encrypted key is stored in a USB token.

18. The computer readable medium containing program instructions of claim 17 wherein the crypto-engine can be disabled.