Cross-domain data access
A cross-domain data access service enables data access across two or more computing domains, such as, for example, transient access by a public device to data held in a private cloud. In particular, the cross-domain data access service can identify a data subset from within a secure datastore of a first computing domain. The cross-domain data access service can replicate the data subset within a transient datastore that is segregated from the secured datastore. The cross-domain data access service can implement a data access policy so as to enable a client device from a second domain to access the transient datastore.
1. A method comprising:
identifying, by a computing system comprising one or more computing devices and based on a data description, a data subset from a secured data set stored in a secured datastore associated with a first computing domain, the data subset comprising a proper subset of the secured data set;
generating, by the computing system, a replicated data subset in a transient datastore that is segregated from the secured datastore, the replicated data subset in the transient datastore being a replica of the data subset from the secured data set stored in the secured datastore;
enabling, by the computing system, a client device associated with a second computing domain to access the replicated data subset in the transient datastore according to a data access policy, the data access policy identifying the client device and identifying access rights of the client device with respect to the replicated data subset, and identifying an expiration condition upon the occurrence of which access to the replicated data subset by the client device is to be terminated;
determining, by the computing system, that the expiration condition specified by the data access policy has occurred; and
in response to determining, by the computing system, that the expiration condition specified by the data access policy has occurred, terminating, by the computing system, access to the replicated data subset in the transient datastore.
2. The method of claim 1 , wherein the transient datastore is physically segregated from the secured datastore.
3. The method of claim 1 , wherein the transient datastore is logically segregated from the secured datastore.
4. The method of claim 1 , further comprising:
automatically synchronizing, by the computing system, the replicated data subset in the transient datastore with the data subset in the secured datastore, wherein automatically synchronizing comprises replicating one or more changes to the data subset in the secured datastore into the replicated data subset in the transient datastore.
5. The method of claim 1 , further comprising:
automatically synchronizing, by the computing system, the replicated data subset in the transient datastore with the data subset in the secured datastore, wherein automatically synchronizing comprises establishing a synchronization connector from the secured datastore to the transient datastore.
6. The method of claim 1 , wherein the first computing domain comprises a private domain and the second computing domain comprises a public domain.
7. The method of claim 1 , wherein enabling, by the computing system, the client device to access the replicated data subset comprises:
receiving, by the computing system and from the client device, a request to access the data subset in the secured datastore or the replicated data subset in a transient datastore;
evaluating, by the computing system, the data access policy to determine whether the request satisfies the data access policy; and
when the request satisfies the data access policy, enabling, by the computing system, the client device to access the replicated data subset from the transient datastore.
8. The method of claim 1 , wherein:
the data access policy specifies a set of one or more acceptable access interfaces for the replicated data subset; and
enabling, by the computing system, the client device to access the replicated data subset comprises enabling, by the computing system, the client device to access the replicated data subset via only one of the acceptable access interfaces.
9. The method of claim 1 , wherein enabling, by the computing system, the client device to access the replicated data subset comprises enabling, by the computing system, the client device to access the replicated data subset via a publish/subscribe mechanism.
10. The method of claim 1 , further comprising:
receiving, by the computing system, one or more encryption requirements for the replicated data subset specified by the client device;
wherein generating, by the computing system, the replicated data subset in the transient datastore comprises encrypting, by the computing system, the replicated data subset in accordance with the one or more encryption requirements specified by client device.
11. The method of claim 1 , further comprising:
importing, by the computing system, one or more data elements from the second computing domain into the transient datastore.
12. The method of claim 1 , further comprising:
receiving, by the computing system, one or more requested edits to the replicated data subset from the client device;
evaluating, by the computing system, the data access policy to determine whether edits to the replicated data subset from the client device are permitted; and
when edits to the replicated data subset from the client device are permitted, editing, by the computing system, the replicated data subset according to the one or more requested edits.
13. The method of claim 1 , wherein terminating, by the computing system, access to the replicated data subset in the transient datastore comprises destroying, by the computing system, the transient datastore.
14. The method of claim 1 , wherein determining, by the computing system, that the expiration condition specified by the data access policy has occurred comprises:
determining, by the computing system, that a period of availability for the transient datastore has reached a predetermined end time specified by the data access policy;
determining, by the computing system, that a number of access requests from the client device to the transient datastore has reached a predetermined maximum number of access requests specified by the data access policy; or
determining, by the computing system, that a volume of data accessed from the transient datastore by the client device has reached a predetermined maximum volume of data specified by the data access policy.
15. The method of claim 1 , wherein identifying, by the computing system based on the data description, the data subset from the secured data set comprises identifying, by the computing system based on the data description, a set of user logs associated with a user of the first computing domain.
16. The method of claim 1 , wherein the data description and the data access policy are specified by an administrator of the first computing domain.
17. A computer system, comprising:
one or more computing devices to:
identify, based on a data description, a data subset from a secured data set stored in a secured datastore associated with a first computing domain, the data subset comprising a proper subset of the secured data set;
generate a replicated data subset in a transient datastore that is segregated from the secured datastore, the replicated data subset in the transient datastore being a replica of the data subset from the secured data set stored in the secured datastore;
enable a client device associated with a second computing domain to access the replicated data subset in the transient datastore according to a data access policy, the data access policy identifying the client device and identifying access rights of the client device with respect to the replicated data subset, and identifying an expiration condition upon the occurrence of which access to the replicated data subset by the client device is to be terminated;
determine that the expiration condition specified by the data access policy has occurred; and
in response to determination that the expiration condition specified by the data access policy has occurred, terminate access to the replicated data subset in the transient datastore.
18. The computer system of claim 17 , wherein the transient datastore is one or both of: physically segregated from the secured datastore and logically segregated from the secured datastore.
19. The computer system of claim 17 , wherein the one or more computing devices are further to:
automatically synchronize the replicated data subset in the transient datastore with the data subset in the secured datastore,
wherein to automatically synchronize the replicated data subset in the transient datastore with the data subset in the secured datastore, the one or more computing devices are to one or both of:
establish a synchronization connector from the secured datastore to the transient datastore; and
replicate one or more changes to the data subset in the secured datastore into the replicated data subset in the transient datastore.
20. A non-transitory computer-readable storage medium that includes executable instructions to cause one or more processor devices to:
identify, based on a data description, a data subset from a secured data set stored in a secured datastore associated with a first computing domain, the data subset comprising a proper subset of the secured data set;
generate a replicated data subset in a transient datastore that is segregated from the secured datastore, the replicated data subset in the transient datastore being a replica of the data subset from the secured data set stored in the secured datastore;
enable a client device associated with a second computing domain to access the replicated data subset in the transient datastore according to a data access policy, the data access policy identifying the client device and identifying access rights of the client device with respect to the replicated data subset, and identifying an expiration condition upon the occurrence of which access to the replicated data subset by the client device is to be terminated;
determine that the expiration condition specified by the data access policy has occurred; and
in response to determination that the expiration condition specified by the data access policy has occurred, terminate access to the replicated data subset in the transient datastore.