Secure Data at Rest

A non-transitory, computer-readable medium storing instructions that, when executed by one or more processors, cause the one or more processors to:

• during a first time period in which a server provides a first mapping between user-specific cloaking sequence elements and hidden sequence elements, cloak target data at least by
• retrieving, from a database and using (i) a first set of one or more user-specific cloaking sequences and (ii) the first mapping, a first set of one or more hidden sequences, and
• generating cloaked target data at least by applying the target data and the first set of hidden sequences as inputs to a cloaking algorithm;
• store the cloaked target data in a persistent memory;
• during a second time period, occurring after the first time period, in which the server provides a different, second mapping between the user-specific cloaking sequence elements and the hidden sequence elements, re-cloak the cloaked target data at least by
• retrieving the cloaked target data from the persistent memory,
• again retrieving the first set of hidden sequences from the database,
• generating uncloaked target data at least by applying the cloaked target data and the first set of hidden sequences as inputs to an inverse of the cloaking algorithm,
• retrieving, from the database and using (i) the first set of user-specific cloaking sequences and (ii) the second mapping, a second set of one or more hidden sequences that is different than the first set of hidden sequences, and
• generating re-cloaked target data at least by applying the uncloaked target data and the second set of hidden sequences as inputs to the cloaking algorithm;
• and
• store the re-cloaked target data in the persistent memory.

A computing system comprising:

• one or more processors;
• a first memory storing target data;
• and
• a second memory storing instructions that, when executed by the one or more processors, cause the computing system to
• during a first time period in which a server provides a first mapping between user-specific cloaking sequence elements and hidden sequence elements, cloak the target data at least by
• retrieving, from a database and using (i) a first set of one or more user-specific cloaking sequences and (ii) the first mapping, a first set of one or more hidden sequences, and
• generating cloaked target data at least by applying the target data and the first set of hidden sequences as inputs to a cloaking algorithm,
• storing the cloaked target data in the first memory,
• during a second time period, occurring after the first time period, in which the server provides a different, second mapping between the user-specific cloaking sequence elements and the hidden sequence elements, re-cloak the cloaked target data at least by
• retrieving the cloaked target data from the first memory,
• again retrieving the first set of hidden sequences from the database,
• generating uncloaked target data at least by applying the cloaked target data and the first set of hidden sequences as inputs to an inverse of the cloaking algorithm,
• retrieving, from the database and using (i) the first set of user-specific cloaking sequences and (ii) the second mapping, a second set of one or more hidden sequences that is different than the first set of hidden sequences, and
• generating re-cloaked target data at least by applying the uncloaked target data and the second set of hidden sequences as inputs to the cloaking algorithm, and
• store the re-cloaked target data in the first memory.