Abstract: A method and solid-state storage device are disclosed for validating erasure status of data blocks on a solid-state drive. The method includes assigning each data block of a plurality of data blocks on the solid-state drive, a block identifier and an erasure status, the block identifier being system data, user data, or unmapped data, and the erasure status being erased or not erased.

Abstract: A method for backing up data includes: receiving, by a driver in a host controller of a data storage device, an indication of a threatening event identifying one or more data files in the data storage device; delaying, by the driver, the threatening event; and backing up, by the driver, the one or more data files in the data storage device, prior to allowing the threatening event.

Abstract: A method for backing up data includes: receiving, by a driver in a host controller of a data storage device, an indication of a threatening event identifying one or more data files in the data storage device; delaying, by the driver, the threatening event; and backing up, by the driver, the one or more data files in the data storage device, prior to allowing the threatening event.

Abstract: A method and solid-state storage device are disclosed for validating erasure status of data blocks on a solid-state drive. The method includes assigning each data block of a plurality of data blocks on the solid-state drive, a block identifier and an erasure status, the block identifier being system data, user data, or unmapped data, and the erasure status being erased or not erased.

Abstract: A method for backing up data includes: receiving, by a driver in a host controller of a data storage device, an indication of a threatening event identifying one or more data files in the data storage device; delaying, by the driver, the threatening event; and backing up, by the driver, the one or more data files in the data storage device, prior to allowing the threatening event.

Abstract: A method for backing up data includes: receiving, by a driver in a host controller of a data storage device, an indication of a threatening event identifying one or more data files in the data storage device; delaying, by the driver, the threatening event; and backing up, by the driver, the one or more data files in the data storage device, prior to allowing the threatening event.

Abstract: A method of verifying erasure of data from a data storage device, the method including retrieving a first metadata portion associated with a first block of data included in the plurality of blocks of data; determining, based on the retrieved first metadata portion, a current content classification associated with the first block of data and a current erasure state associated with the first block of data; and determining an erasure status associated with the first block of data based on the current content classification associated with the first block of data and the current erasure state associated with the first block of data.

Abstract: A method for controlling access to data storage based on application rights dictating usage ability of a user includes: receiving, by a first application of a computing device, a data access request from a second application of the computing device, the data access request including a user identifier, namespace identifier, application identifier associated with the second application, and data command; verifying data access authorization for a user of the second application and for the second application program based on a first permission stored in an application-application rights table associated with the user identifier, application identifier, the data command; verifying data access authorization for the first application based on a second permission stored in an application-storage rights table associated with the namespace identifier and data command; executing the data command to read from or write data to a data storage interfaced with the computing device associated with the namespace identifier.

Abstract: A method for emergency data destruction includes: identifying, by a data identification module, one or more data files for emergency destruction stored in one or more data storage devices; identifying, by the data identification module, at least one file system utilized by the one or more data storage devices; overwriting, by a data generation module, a header of each of the one or more data files, wherein the header of each of the one or more data files is identified based on the at least one file system; truncating, by a data modification module, a file size of each of the one or more data files; and deleting, by a data destruction module, each of the one or more data files, wherein the overwriting and truncating steps are performed prior to deletion of each of the one or more data files.

Abstract: A method for backing up data includes: receiving, by a driver in a host controller of a data storage device, an indication of a threatening event identifying one or more data files in the data storage device; delaying, by the driver, the threatening event; and backing up, by the driver, the one or more data files in the data storage device, prior to allowing the threatening event.

Abstract: A method for backing up data includes: receiving, by a driver in a host controller of a data storage device, an indication of a threatening event identifying one or more data files in the data storage device; delaying, by the driver, the threatening event; and backing up, by the driver, the one or more data files in the data storage device, prior to allowing the threatening event.