FACILITATING DYNAMIC END-TO-END INTEGRITY FOR DATA REPOSITORIES IN AN ON-DEMAND SERVICES ENVIRONMENT

• US 20160080368A1
• Filed: 09/12/2014
• Published: 03/17/2016
• Est. Priority Date: 09/12/2014
• Status: Active Grant

• Current Assignee: Salesforce.com, Inc.
• Original Assignee: Salesforce.com, Inc.
• Inventors: HAMACHER, CLAYTEN, STEELE, Matthew, SOLANKI, PATHIK ASHOK, Schechtman, Matthew B., HEURICH, SHILOH CORY, Siebenlist, Frank, Elgamal, Taher
• Granted Patent: US 10,491,398 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/12 Applying verification of the received information cryptographic mechanisms or cryptographic arrangements for data integrity or data verification H04L9/32
• CPC Class Codes: H04L 9/3247 involving digital signatures

Abstract

In accordance with embodiments, there are provided mechanisms and methods for facilitating dynamic end-to-end integrity for data repositories in an on-demand services environment in an on-demand services environment in a multi-tenant environment according to one embodiment. In one embodiment and by way of example, a method includes receiving, by and incorporating into a database system, a content file and metadata to be submitted to a data repository of the database system. The content file may include content, where the metadata includes identifying data associated with at least one of the content and a user associated with the content. The method may further include verifying, by the database system, the identifying data of the metadata. The verification of the identifying data represents authentication of at least one of the user and the content. The method may further include submitting, by the database system, the content file and the metadata to the data repository, upon authentication of at least one of the user and the content via successful verification of the identifying data.

Claims

1. A database system-implemented method comprising:

receiving, by and incorporating into a database system, a content file and metadata to be submitted to a data repository of the database system, wherein the content file includes content, and wherein the metadata includes identifying data associated with at least one of the content and a user associated with the content;

verifying, by the database system, the identifying data of the metadata, wherein the verification of the identifying data represents authentication of at least one of the user and the content; and

submitting, by the database system, the content file and the metadata to the data repository, upon authentication of at least one of the user and the content via successful verification of the identifying data.

2. The method of claim 1, wherein the identifying data comprises a signature associated with the user, wherein the signature is verified to identify and authenticate the user, and wherein the signature is generated using cryptographic keys and assigned to the metadata at a client computing device.

3. The method of claim 1, wherein the identifying data comprises a fingerprint associated with the content, wherein the fingerprint is verified to identify and authenticate the content, and wherein the fingerprint is generated using hash values and the content and assigned to the metadata at the client computing device.

4. The method of claim 1, wherein metadata further comprises authorship data associated with the user being an author of the content, wherein the authorship data includes user credential data having one or more of a name of the user, an employee number of the user, and a birth date of the user.

5. The method of claim 1, wherein the metadata further comprises a timestamp associated with the content, wherein the timestamp is generated and associated with the content via a third-party computing device, wherein the content is generated at the client computing device.

6. The method of claim 1, wherein the metadata serves as an attribute to the content file, wherein upon submission to the repository, the metadata remains associated with the content file, wherein the metadata is generated at the client computing device.

7. An apparatus comprising:

deception/reception logic to receive a content file and metadata to be submitted to a data repository, wherein the content file includes content, and wherein the metadata includes identifying data associated with at least one of the content and a user associated with the content;

verification engine to verify the identifying data of the metadata, wherein the verification of the identifying data represents authentication of at least one of the user and the content; and

submission logic to submit the content file and the metadata to the data repository, upon authentication of at least one of the user and the content via successful verification of the identifying data.

8. The apparatus of claim 7, wherein the identifying data comprises a signature associated with the user, wherein the signature is verified to identify and authenticate the user, and wherein the signature is generated using cryptographic keys and assigned to the metadata at a client computing device.

9. The apparatus of claim 7, wherein the identifying data comprises a fingerprint associated with the content, wherein the fingerprint is verified to identify and authenticate the content, and wherein the fingerprint is generated using hash values and the content and assigned to the metadata at the client computing device.

10. The apparatus of claim 7, wherein metadata further comprises authorship data associated with the user being an author of the content, wherein the authorship data includes user credential data having one or more of a name of the user, an employee number of the user, and a birth date of the user.

11. The apparatus of claim 7, wherein the metadata further comprises a timestamp associated with the content, wherein the timestamp is generated and associated with the content via a third-party computing device, wherein the content is generated at the client computing device.

12. The apparatus of claim 7, wherein the metadata serves as an attribute to the content file, wherein upon submission to the repository, the metadata remains associated with the content file, wherein the metadata is generated at the client computing device.

13. A machine-readable medium comprising a plurality of instructions which, when executed by a processing device, cause the processing device to perform one or more operations comprising:

receiving a content file and metadata to be submitted to a data repository, wherein the content file includes content, and wherein the metadata includes identifying data associated with at least one of the content and a user associated with the content;

verifying the identifying data of the metadata, wherein the verification of the identifying data represents authentication of at least one of the user and the content; and

submitting the content file and the metadata to the data repository, upon authentication of at least one of the user and the content via successful verification of the identifying data.

14. The machine-readable medium of claim 13, wherein the identifying data comprises a signature associated with the user, wherein the signature is verified to identify and authenticate the user, and wherein the signature is generated using cryptographic keys and assigned to the metadata at a client computing device.

15. The machine-readable medium of claim 13, wherein the identifying data comprises a fingerprint associated with the content, wherein the fingerprint is verified to identify and authenticate the content, and wherein the fingerprint is generated using hash values and the content and assigned to the metadata at the client computing device.

16. The machine-readable medium of claim 13, wherein metadata further comprises authorship data associated with the user being an author of the content, wherein the authorship data includes user credential data having one or more of a name of the user, an employee number of the user, and a birth date of the user.

17. The machine-readable medium of claim 13, wherein the metadata further comprises a timestamp associated with the content, wherein the timestamp is generated and associated with the content via a third-party computing device, wherein the content is generated at the client computing device.

18. The machine-readable medium of claim 13, wherein the metadata serves as an attribute to the content file, wherein upon submission to the repository, the metadata remains associated with the content file, wherein the metadata is generated at the client computing device.