Secure third-party document editing

Abstract

Systems and methods for secure third-party document editing are described. In some embodiments, a method may include tokenizing a file retrieved from a cloud storage provider (CSP); transmitting the tokenized file to a cloud editing provider (CEP); receiving a modified, tokenized file from the CEP; de-tokenizing the modified file; and enabling rendering of the de-tokenized, modified file. In other embodiments, a memory device may have program instructions stored thereon that, upon execution by a processor of an Information Handling System (IHS), cause the IHS to: provide a portal to a user executing a browser on a client device, wherein the portal includes an interface to a CSP and to a cloud editing provider (CDEP); and allow the user to access a document stored in the CSP and to edit the document using the CDEP via the browser.

The invention claimed is: 
     
       1. In an Information Handling System (IHS), a method comprising:
 retrieving an encrypted file from a cloud storage provider (CSP); 
 decrypting the encrypted file using a key identification stored in a file header; 
 tokenizing the decrypted file; 
 transmitting the tokenized file to a cloud editing provider (CEP); 
 receiving a modified, tokenized file from the CEP; 
 de-tokenizing the modified file; 
 enabling rendering of the de-tokenized, modified file. 
 
     
     
       2. The method of  claim 1 , wherein the file includes an electronic document. 
     
     
       3. The method of  claim 1 , wherein the file includes a raw data component and a formatting component, and wherein tokenizing the file includes tokenizing the raw data component but not the formatting component. 
     
     
       4. The method of  claim 3 , wherein tokenizing the file includes employing a one-time pad technique. 
     
     
       5. The method of  claim 3 , wherein tokenizing the file includes creating a tokenization seed and a stream of token values. 
     
     
       6. The method of  claim 5 , wherein tokenizing the file includes replacing the raw data component with the stream of token values. 
     
     
       7. The method of  claim 6 , wherein the modified, tokenized file received from the CEP includes one or more modifications to the raw data component, and wherein the modifications are performed by a user. 
     
     
       8. The method of  claim 7 , wherein de-tokenizing the file includes using the tokenization seed to de-tokenize the modified raw data component. 
     
     
       9. A hardware memory device having program instructions stored thereon that, upon execution by a processor of an Information Handling System (IHS), cause the IHS to:
 provide a portal to a user executing a browser on a client device, wherein the portal includes an interface to a cloud storage provider (CSP) and to a cloud document editing provider (CDEP); 
 allow the user to access a document stored in the CSP and to edit the document using the CDEP via the browser, wherein the document includes a plaintext portion and a formatting portion, and wherein the editing occurs without transmitting the plaintext portion to the CDEP; 
 allow the user to select the document using the browser; 
 retrieve the document from the CSP; 
 provide the document to the client device, wherein the browser is configured to render the document and to allow the user to edit the document via the portal 
 tokenize the document; 
 transmit the tokenized document to the CDEP; 
 receive an edit from a user manipulating the document in the browser; 
 transmit a tokenized version of the edit to the CDEP; and 
 receive a modified, tokenized document from the CDEP. 
 
     
     
       10. The hardware memory device of  claim 9 , wherein tokenizing the file includes tokenizing the plaintext portion but not the formatting portion. 
     
     
       11. The hardware memory device of  claim 10 , wherein tokenizing the file includes creating a tokenization seed and a stream of token values and replacing the plaintext portion with the stream of token values. 
     
     
       12. The hardware memory device of  claim 9 , wherein the program instructions, upon execution, further cause the IHS to:
 de-tokenize the modified document; and 
 provide the de-tokenized, modified document to the client device, wherein the browser is configured to render the de-tokenized, modified document. 
 
     
     
       13. An Information Handling System (IHS), comprising:
 a processor; and 
 a memory coupled to the processor, the memory having program instructions stored thereon that, upon execution by the processor, cause the IHS to:
 provide a portal to a user executing a browser on a client device, wherein the portal includes an interface to a cloud storage provider (CSP) and to a cloud document editing provider (CDEP); 
 allow the user to select a document using the browser; 
 retrieve the document from the CSP; 
 provide the document to the client device, wherein the browser is configured to render the document and to allow the user to edit the document via the portal; 
 tokenize the document, wherein tokenizing the document includes tokenizing a plaintext portion but not a formatting portion; 
 transmit the tokenized document to the CDEP; 
 receive an edit from a user manipulating the document in the browser; transmit a tokenized version of the edit to the CDEP; receive a modified, tokenized document from the CDEP; 
 de-tokenize the modified document; and 
 provide the de-tokenized, modified document to the client device, wherein the browser is configured to render the de-tokenized, modified document. 
 
 
     
     
       14. The IHS of  claim 13 , wherein tokenizing the document further includes creating a tokenization seed and a stream of token values. 
     
     
       15. The IHS of  claim 14 , wherein the program instructions, upon execution by the processor, further cause the IHS to replace the plaintext portion with the stream of token values. 
     
     
       16. In an Information Handling System (IHS), a method comprising:
 tokenizing a file retrieved from a cloud storage provider (CSP), wherein the file includes a raw data component and a formatting component, and wherein tokenizing the file includes tokenizing the raw data component but not the formatting component; 
 transmitting the tokenized file to a cloud editing provider (CEP); 
 receiving a modified, tokenized file from the CEP; 
 de-tokenizing the modified file; and 
 enabling rendering of the de-tokenized, modified file. 
 
     
     
       17. The method of  claim 16 , further comprising:
 retrieving the file from the CSP in encrypted form; and 
 decrypting the file using a key identification stored in a file header. 
 
     
     
       18. The method of  claim 16 , wherein tokenizing the file includes at least one of: employing a one-time pad technique, creating a tokenization seed and a stream of token values, or replacing the raw data component with the stream of token values. 
     
     
       19. The method of  claim 16 , wherein the modified, tokenized file received from the CEP includes one or more modifications to the raw data component, and wherein de-tokenizing the file includes using the tokenization seed to de-tokenize the modified raw data component.