Using a secure enclave to satisfy retention and expungement requirements with respect to private data
A secure enclave may be used to satisfy privacy requirements and audit requirements. Code may be loaded into the secure enclave. The code may generate a predefined report based on data and added noise. The pre-defined report may be subject to audit requirements. The data may be subject to the privacy requirements. The secure enclave may generate an encryption key and a decryption key based on the code. Only the secure enclave may have access to the decryption key. And the secure enclave may allow only a verified copy of the code to access the decryption key. With the added noise, the report may satisfy a pre-defined differential privacy guarantee. Encrypting the code and ensuring that the report satisfies the differential privacy guarantee may satisfy the privacy requirements. Retaining the report, the code, the secure enclave, and the encrypted data may satisfy the audit requirements.
1. A method comprising:
receiving data, wherein the data comprises personal information of one or more individuals and is subject to privacy requirements;
encrypting the data to generate encrypted data, wherein only a secure enclave can decrypt the encrypted data;
storing the encrypted data in memory;
generating, by the secure enclave, a private synopsis, wherein the generating the private synopsis comprises:
adding, by the secure enclave, noise to the encrypted data; and
aggregating, by the secure enclave, the encrypted data and the noise to create a first summary of the data, wherein the private synopsis comprises the first summary of the data, the first summary of the data satisfies a differential privacy guarantee, and the differential privacy guarantee satisfies the privacy requirements;
generating a report from the private synopsis, wherein the report is subject to audit requirements and includes a second summary of the first summary and wherein the second summary is aggregated at a higher level than the first summary;
expunging the encrypted data; and
retaining, after expunging the encrypted data, the private synopsis, wherein the private synopsis, without the encrypted data, satisfies the audit requirements, wherein the audit requirements comprise an obligation to provide means for an independent auditor to verify a process used to generate the report, and wherein the obligation lasts for a defined length of time specified by the audit requirements.
2. The method of claim 1 , wherein the audit requirements are imposed by laws, regulations, or agreements.
3. The method of claim 1 , wherein the retaining the private synopsis comprises retaining the private synopsis for a first period of time and wherein a length of the first period of time is based on the audit requirements.
4. The method of claim 3 , wherein the expunging the encrypted data comprises expunging the encrypted data after a period of time, wherein a length of the period of time is based on the privacy requirements, and wherein the period of time is shorter than the first period of time.
5. The method of claim 1 , wherein a level of aggregation of the first summary is based on the audit requirements and the privacy requirements.
6. The method of claim 1 , wherein the data includes telemetry data generated by one or more computing devices.
7. The method of claim 1 , wherein a level of aggregation of the first summary is based on a desired accuracy, the privacy requirements, and the audit requirements.
8. The method of claim 1 , wherein the privacy requirements include obligations imposed by laws, regulations, and service agreements.