A record linking platform having a computer system with a processor, multiple databases each having records, such as private health information. Each of the multiple databases are not in direct communication with one another. A control center is in communication with the different entities, the control center configured to: generate a site configuration file, a key configuration file, and a broker configuration file. A keymaster configured to: receive the key configuration file, generate a hash key, and transmit the hash key to the databases. The databases configured to: receive the site configuration file and the hash key; process the records to generate evaluation records data that conform to a data model specified in the site configuration file; and encrypt the evaluation records using the hash key. An honest broker configured to: receive the broker configuration file and the encrypted evaluation records; and link the encrypted evaluation records without decrypting.

Systems and methods for managing provisioning of keys prior to a key rotation are provided. A license server generates a license that is associated with a renewal time. The renewal time is a time that is prior to a key rotation time, and triggers a receiver device to send a renewal request prior to the key rotation time. The renewal time may be a randomized time prior to the key rotation time that differs for different receiver devices. The license is transmitted to the receiver device. The license server then receives a renewal request from the receiver device that is triggered at the renewal time. The license server generates a next license that comprises a next key, whereby the next key is a decryption key for decrypting the encrypted signal after the key rotation time. The next license is transmitted to the receiver device prior to the key rotation time.

A computer system is configured for digital rights management for distributing and tracking downloadable proprietary source code defining a 3-D object and being usable to print the object on a 3D printer and protect the 3D object data from unauthorized printing. The computer system stores an inventory of proprietary source code corresponding to designs of a plurality of 3D objects, and enables a user to see the inventory of designs of the plurality of 3D objects in an online store, and permits the user to securely purchase use of the source code of a desired 3D object viewed therein. The computer system sends the proprietary source code defining the desired 3D object to a 3D printer, and controls printing of the desired 3D object made by the 3D printer to prevent further use of the source code when the purchased use in completed, using one of three different typologies.

A layered-infrastructure blockchain-based system for software license distribution includes a distributed cloud of blockchain full nodes. Each blockchain full node contains a blockchain data structure on which a complete set of license key transactions are recorded. The layered-infrastructure also includes a plurality of storage systems. Each respective storage system contains a blockchain light data structure on which only a subset of license key transactions associated with that respective storage system are recorded. A plurality of hosts connect to the plurality of storage systems. As the hosts connect to the storage systems, license key transactions are generated, such that the license key transactions that are recorded in the blockchain-based system for software license distribution are associated with the connection events between the plurality of hosts and the plurality of storage systems.

This disclosure describes systems and methods for protecting commercial off-the-shelf software program code from piracy. A software program may include an executable file having code and data. A platform may modify the executable file such that the data may be placed at a location in memory that is an arbitrary distance from the code. The platform may modify the executable file to include a separation header. The separation header may indicate that the data can be placed at an arbitrary distance in the memory from the code. The separation header may indicate that the code should be loaded into a hardware enclave and that the data should be loaded outside of the hardware enclave. The platform may encrypt the code and provide it to a computing device. The computing device may load the encrypted code into the hardware enclave but load the data into memory outside the hardware enclave.