Chaining, triggering, and enforcing entitlements
Embodiments are directed to techniques for enforcing entitlements used by data privacy pipelines. When a data consumer requests to trigger a pipeline that relies on an entitlement, an enforcement mechanism may operate to verify the data consumer's triggering of the pipeline will satisfy the entitlements. A rules engine may access all root entities of the pipeline that require an entitlement, load all contracts and/or corresponding pipelines that reference one of the root entities, and search for one valid access path through the loaded contracts/pipelines. If multiple contracts and/or multiple access paths allow access to a particular root entity, various conflict rules may be configured to choose which contract and access path to use. If all root entities have a valid access path, the constrained environment may execute the requested pipeline using the identified access path for each root entity.
1. A data trustee environment comprising:
one or more computer storage media storing computer-useable instructions that, when used by one or more computing devices, cause the one or more computing devices to perform operations comprising:
receiving a request from a data consumer to trigger a data privacy pipeline required to execute within a data trustee environment;
identifying all root entities of the data privacy pipeline requiring an entitlement from a grantor that is not a participant to the data privacy pipeline;
loading contracts that govern access to the root entities within the data trustee environment;
for each root entity of the root entities, searching the contracts to identify a valid access path pursuant to an associated one of the contracts with which the data privacy pipeline can use the root entity while fulfilling constraints defined by the associated contract and applicable upon accessing the root entity, and while fulfilling policies defined by the associated contract and applicable to computations of the data privacy pipeline that are downstream from the root entity; and
based on each of the root entities having an identified valid access path pursuant to an identified associated one of the contracts, triggering execution of the data privacy pipeline within the data trustee environment using the identified valid access path and the associated identify contract to access each of the root entities, without exposing the root entities.
2. The data trustee environment of claim 1 , wherein identifying all root entities of the data privacy pipeline requiring an entitlement comprises accessing a digitized representation of the data privacy pipeline having an associated list, property, or metadata identifying the root entities.
3. The data trustee environment of claim 1 , the operations further comprising, prior to searching the contracts to identify a valid access path for each root entity, filtering out a set of the contracts that do not grant access to the data consumer based on an identity of the data consumer.
4. The data trustee environment of claim 1 , wherein searching the contracts for each root entity comprises, for each contract of the contracts governing access to the root entity:
identifying a potential access path having all computational steps that would be required to execute in the data trustee environment in order to trigger the data privacy pipeline in the data trustee environment using the contract to access the root entity; and
determining whether the potential access path would fulfill constraints defined by the contract and applicable upon accessing the root entity, and would fulfill policies defined by the contract and applicable to a set of the computational steps that are downstream from the root entity.
5. The data trustee environment of claim 1 , wherein searching the contracts for each root entity comprises, for each contract of the contracts governing access to the root entity:
identifying a potential access path having all computational steps that would be required to execute in the data trustee environment in order to trigger the data privacy pipeline in the data trustee environment using the contract to access the root entity; and
verifying the computational steps of the potential access path would satisfy applicable constraints and policies, without executing the computational steps.
6. The data trustee environment of claim 1 , wherein searching the contracts to identify a valid access path for each root entity comprises, evaluating computational steps of potential access paths without executing a first set of the computational steps, and conditionally executing a second set of the computational steps to evaluate a particular constraint or policy that is only capable of verification during runtime.
7. The data trustee environment of claim 1 , wherein searching the contracts to identify a valid access path for each root entity identifies a plurality of candidate contracts or a plurality of valid access paths for at least a first root entity of the root entities, the operations further comprising applying conflict rules to select one of the plurality of valid access paths as the identified valid access or select one of the plurality of candidate contracts as the identified associated contract for the first root entity.
8. One or more computer storage media storing computer-useable instructions that, when used by one or more computing devices, cause the one or more computing devices to perform operations comprising:
receiving a request from a data consumer to trigger a data privacy pipeline required to execute within a data trustee environment;
identifying all root entities of the data privacy pipeline requiring an entitlement from a grantor that is not a participant to the data privacy pipeline;
identifying a set of contracts governing access to the root entities within the data trustee environment and defining a valid access path for each of the root entities such that the data privacy pipeline can use the root entities while fulfilling constraints and policies defined by the set of contracts, the constraints applicable upon accessing the root entities, the policies applicable to computations of the data privacy pipeline that are downstream from the root entities; and
triggering execution of the data privacy pipeline within the data trustee environment using the identified set of the contracts to access the root entities, without exposing the root entities.
9. The one or more computer storage media of claim 8 , wherein identifying all root entities of the data privacy pipeline requiring an entitlement comprises accessing a digitized representation of the data privacy pipeline having an associated list, property, or metadata identifying the root entities.
10. The one or more computer storage media of claim 8 , the operations further comprising:
loading a plurality of contracts that govern access to the root entities within the data trustee environment;
filtering out a subset of the contracts that do not grant access to the data consumer based on an identity of the data consumer, leaving a remaining set of the contracts;
searching the remaining set of contracts to identify the set of contracts governing access to the root entities.
11. The one or more computer storage media of claim 8 , wherein identifying the set of contracts defining a valid access path for each of the root entities comprises, for each root entity and each contract governing access to the root entity:
identifying a potential access path having all computational steps that would be required to execute in the data trustee environment in order to trigger the data privacy pipeline in the data trustee environment using the contract to access the root entity; and
determining whether the potential access path would fulfill constraints defined by the contract and applicable upon accessing the root entity, and would fulfill policies defined by the contract and applicable to a set of the computational steps that are downstream from the root entity.
12. The one or more computer storage media of claim 8 , wherein identifying the set of contracts defining a valid access path for each of the root entities comprises, for each root entity and each contract governing access to the root entity:
identifying a potential access path having all computational steps that would be required to execute in the data trustee environment in order to trigger the data privacy pipeline in the data trustee environment using the contract to access the root entity; and
verifying the computational steps of the potential access path would satisfy applicable constraints and policies, without executing the computational steps.
13. The one or more computer storage media of claim 8 , wherein identifying the set of contracts defining a valid access path for each of the root entities comprises evaluating computational steps of potential access paths without executing a first set of the computational steps, and conditionally executing a second set of the computational steps to evaluate a particular constraint or policy that is only capable of verification during runtime.
14. The one or more computer storage media of claim 8 , wherein identifying the set of contracts defining a valid access path comprises, for at least a first root entity of the root entities:
identifying a plurality of candidate contracts or a plurality of valid access paths governing access to the first root entity; and
applying conflict rules to identify a single contract and a single valid access path for the first root entity based on at least one of the plurality of candidate contracts or the plurality of valid access paths.
15. A method comprising:
receiving a request from a data consumer, to trigger a data privacy pipeline required to execute within a constrained environment that is inaccessible to the data consumer, and to export from the constrained environment data generated by the data privacy pipeline;
determining that executing the data privacy pipeline within the constrained environment would satisfy an associated entitlement to use a root entity of the data privacy pipeline within the constrained environment, the associated entitlement specifying a constraint on accessing the root entity within the constrained environment and a policy on downstream computations within the constrained environment deriving from the root entity;
determining that the data consumer has permission to export the data from the constrained environment; and
triggering execution of the data privacy pipeline within the constrained environment using the root entity pursuant to the associated entitlement, without exposing the root entity.
16. The method of claim 15 , the method further comprising:
identifying all root entities of the data privacy pipeline requiring a corresponding entitlement from a grantor that is not a participant to the data privacy pipeline;
wherein determining that executing the data privacy pipeline within the constrained environment would satisfy the associated entitlement to use the root entity comprises searching contracts that govern access to the root entities within the constrained environment to identify a valid access path for each of the root entities.
17. The method of claim 15 , the method further comprising identifying all root entities of the data privacy pipeline requiring a corresponding entitlement from a grantor that is not a participant to the data privacy pipeline by accessing a digitized representation of the data privacy pipeline having an associated list, property, or metadata identifying the root entities.
18. The method of claim 15 , the method further comprising:
identifying all root entities of the data privacy pipeline requiring a corresponding entitlement from a grantor that is not a participant to the data privacy pipeline;
loading a plurality of contracts that govern access to the root entities within the constrained environment; and
filtering out a subset of the plurality of contracts that do not grant access to the data consumer based on an identity of the data consumer, leaving a remaining set of the contracts;
wherein determining that executing the data privacy pipeline within the constrained environment would satisfy the associated entitlement to use the root entity comprises searching the remaining set of contracts to identify a valid access path for the root entity.
19. The method of claim 15 , wherein determining that executing the data privacy pipeline within the constrained environment would satisfy the associated entitlement to use the root entity comprises, for each of a plurality of contracts governing access to the root entity within the constrained environment:
identifying a potential access path having all computational steps that would be required to execute in the constrained environment in order to trigger the data privacy pipeline in the constrained environment using the contract to access the root entity; and
determining whether the potential access path would fulfill constraints defined by the contract and applicable upon accessing the root entity, and would fulfill policies defined by the contract and applicable to a set of the computational steps that are downstream from the root entity.
20. The method of claim 15 , wherein determining that executing the data privacy pipeline within the constrained environment would satisfy the associated entitlement to use the root entity comprises, for each of a plurality of contracts governing access to the root entity within the constrained environment:
identifying a potential access path having all computational steps that would be required to execute in the constrained environment in order to trigger the data privacy pipeline in the constrained environment using the contract to access the root entity; and
verifying the computational steps of the potential access path would satisfy applicable constraints and policies, without executing the computational steps.