Abstract: Techniques for providing increased support for deduplication and compression of encrypted storage volumes. The techniques include receiving, at a storage virtual machine (VM), a data encryption key (DEK) associated with encrypted volume data, in which the DEK is wrapped in a key encryption key (KEK). The techniques include receiving, at the storage VM from a client virtual machine (VM), a write request specifying the encrypted volume data. The techniques include obtaining, by the storage VM, the KEK from a key management system (KMS) embedded on the storage VM. The techniques include unwrapping, by the storage VM, the DEK using the KEK, and decrypting, by an IO decryptor hosted by the storage VM, the encrypted volume data using the DEK. The techniques include performing, by the storage VM, data reduction operations on the decrypted volume data, and storing, by the storage VM, the data-reduced volume data on a storage array.

Abstract: A method, computer program product, and computing system for receiving content for securely transmitting from an initiator device across a fabric to a target device. The content may be encrypted with a predefined encryption key, thus defining encrypted content. The encrypted content may be encapsulated in a Non-volatile Memory Express (NVMe) Over Fabrics (NVMe-oF) command, thus defining an encapsulated NVMe-oF security command. The encapsulated NVMe-oF security command may be transmitted across the fabric to the target device.

Abstract: One example method includes continuously performing key related operations. Each data set in a storage system is encrypted with a different key. New keys are repeatedly introduced and new data is encrypted only with the newest or latest key. Data being rekeyed is re-encrypted with the latest key. By repeatedly introducing new keys and rekeying data sets associated with older keys, the overall key age of the system can be kept low and the data is less susceptible to being compromised.

Abstract: Described are techniques for storing data. A plurality of data portions and a corresponding token for each of the data portions are received. Each of said plurality of data portions is to be stored by one of a plurality of processes and each token has a corresponding token value. Each of the data portions is stored at a storage location on a device allocated for use by one of said plurality of processes. An entry is written in a log file in accordance with said storing of the data portion. The log file is a private log file of one of the plurality processes. An access structure used to access stored data portions is updated. The access structure is indexed by token values of the stored data portions. The updating of the access structure is performed in accordance with log entries from private log files of the plurality of processes.

Abstract: Described are techniques for processing a request to store data. The request to store data in accordance with a single instance storage technique is received. A schedule for storing the data in accordance with information included in the request is determined. Data for processing is requested in accordance with the single instance storage technique in accordance with the schedule.

Abstract: Described are techniques for managing an index structure used to access data portions. A token having a token value for a data portion is provided. An entry in said index structure for said data portion is provided. The index structure is accessed using said token value as a key to determine said entry in said index structure for said data portion. The entry is allocated to have a location in accordance with said token value.