Sensitive information cloud service

Patent metadata

Field	Value
Publication number	US-2016359828-A1
Application number	US-201514729531-A
Country	US
Kind code	A1
Filing date	Jun 3, 2015
Priority date	Jun 3, 2015
Publication date	Dec 8, 2016
Grant date	—

Abstract

In an example embodiment, login credentials are received from a user. These login credentials are validated. Sensitive information is received from the user. The sensitive information is then stored in a cloud-based database. One or more access limitations are established for the sensitive information. A request for the sensitive information is received, from a first third party entity, via an application program interface (API) distributed to a plurality of third party entities. It is then determined if providing access to the sensitive information to the first third party entity would violate the one or more access limitations for the sensitive information. In response to a determination that the providing access to the sensitive information to the first third party entity would not violate the one or more access limitations for the sensitive information, the sensitive information is transmitted to the first third party entity.

First claim

What is claimed is:

1 . A method comprising:
receiving login credentials of a user from a user device; validating the login credentials; receiving sensitive information from the user device, the sensitive information including details different from the login credentials; storing the sensitive information in a cloud-based database; establishing one or more access limitations for the sensitive information; receiving a request for the sensitive information, from a first third party entity, via an application program interface (API) accessible by a plurality of third party entities; determining if providing access to the sensitive information to the first third party entity would violate the one or more access limitations for the sensitive information; and in response to a determination that the providing access to the sensitive information to the first third party entity would not violate the one or more access limitations for the sensitive information, transmitting the sensitive information to the first third party entity.

2 . The method of claim 1 , wherein the one or more access limitations include a limit on a number of accesses of the sensitive information within a set period of time, and the method further comprises tracking the number of accesses of the sensitive information by the first third party entity.

3 . The method of claim 1 , further comprising tracking accesses of the sensitive information and presenting information about the accesses to the user via a dashboard.

4 . The method of claim 3 , wherein the dashboard includes a breakdown of which sensitive information was accessed by which third party entity and the frequency of such accesses.

5 . The method of claim 4 , wherein the dashboard further includes a mechanism for the user to set the one or more access limitations.

6 . The method of claim 4 , wherein the sensitive information is one portion of sensitive information provided by the user, the one portion corresponding to one category of sensitive information, and wherein the dashboard further includes a breakdown of a plurality of different portions of the sensitive information and which of those different portions were accessed by which third party entity.

7 . The method of claim 1 , wherein the storing the sensitive information includes storing the sensitive information in a cloud-based in-memory database management system.

8 . The method of claim 1 , further comprising receiving payment from the first third party entity in exchange for the transmitting of the sensitive information to the first third party entity.

9 . A system comprising:
a sensitive information management component executable by one or more processors and configured to receive login credentials of a user from a user device; a sensitive information identity provider module configured to validate the login credentials; a sensitive information create, update, and delete (CRUD) module; a sensitive information cloud platform; the sensitive information management component further configured to receive sensitive information from the user device, the sensitive information including details different from the login credentials, and to transmit the sensitive information to the sensitive information cloud platform via the sensitive information CRUD module; a primary database; the sensitive information cloud platform configured to store the sensitive information in the primary database; an API accessible by a plurality of third party entities; a sensitive information usage metering module; and the sensitive information management component further configured to establish, via the sensitive information usage metering module, one or more access limitations for the sensitive information; receive a request for the sensitive information, from a first third party entity, via the API; determine, using the sensitive information usage metering module, whether providing access to the sensitive information to the first third party entity would violate the one or more access limitations for the sensitive information; and in response to a determination that the providing access to the sensitive information to the first third party entity would not violate the one or more access limitations for the sensitive information, retrieve the sensitive information via the sensitive information cloud platform and transmit the sensitive information to the first third party entity.

10 . The system of claim 9 , further comprising a user interface accessible by the user to communicate the login credentials and the sensitive information.

11 . The system of claim 10 , wherein the sensitive information usage metering module is further configured to track accesses of the sensitive information and wherein the user interface includes a dashboard presenting information about the accesses to the user.

12 . The system of claim 11 , wherein the dashboard includes a breakdown of which sensitive information was accessed by which third party entity and the frequency of such accesses.

13 . The system of claim 12 , wherein the dashboard further includes a mechanism for the user to set the one or more access limitations.

14 . The system of claim 11 , wherein the sensitive information is one portion of sensitive information provided by the user, the one portion corresponding to one category of sensitive information, and wherein the dashboard further includes a breakdown of a plurality of different portions of the sensitive information and which of those different portions were accessed by which third party entity.

15 . The system of claim 9 , wherein the one or more access limitations include a limit on a number of accesses of the sensitive information within a set period of time, and the sensitive information usage metering module is further configured to track the number of accesses of the sensitive information by the first third party entity.

16 . A non-transitory machine-readable storage medium comprising instructions which, when implemented by one or more machines, cause the one or more machines to perform operations comprising:
receiving login credentials of a user from a user device; validating the login credentials; receiving sensitive information from the user device, the sensitive information including details different from the login credentials; storing the sensitive information in a cloud-based database; establishing one or more access limitations for the sensitive information; receiving a request for the sensitive information, from a first third party entity, via an application program interface (API) accessible by a plurality of third party entities; determining if providing access to the sensitive information to the first third party entity would violate the one or more access limitations for the sensitive information; and in response to a determination that the providing access to the sensitive information to the first third party entity would not violate the one or more access limitations for the sensitive information, transmitting the sensitive information to the first third party entity.

17 . The non-transitory machine-readable storage medium of claim 16 , further comprising tracking accesses of the sensitive information and presenting information about the accesses to the user via a dashboard.

18 . The non-transitory machine-readable storage medium of claim 17 , wherein the dashboard includes a breakdown of which sensitive information was accessed by which third party entity and the frequency of such accesses.

19 . The no

Assignees

• Sap Se

Inventors

• Thormaehlen Frederik

Classifications

• H04L63/102 Primary

  Entity profiles · CPC title

• H04L63/08 Primary

  for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32) · CPC title

• H04W12/02

  Protecting privacy or anonymity, e.g. protecting personally identifiable information [PII] · CPC title