Method and system for providing data security for micro-services across domains
A method at a network element for securely sharing services across domains, the method including receiving a request at the network element to add a first domain and an edge domain to a system; provisioning a public key of the network element to the first domain and the edge domain; receiving a public key of the first domain; populating, in the network element, a table with services provided by the first domain or the edge domain; populating, in the network element, a second table with applications installed at the first domain or edge domain and permissions for services for the applications; and controlling access to the services by the applications.
1. A method at a network element for securely sharing services across domains, the method comprising:
receiving a request at the network element to add a first domain and an edge domain to a system;
populating, in the network element, a table with services, the services being provided by the first domain or the edge domain;
populating, in the network element, a second table with applications installed at the first domain or edge domain and permissions corresponding to a subset of the services; and
controlling access to the services by the applications based on the permissions.
2. The method of claim 1 , wherein the controlling access comprises:
receiving a request from an application on the first domain, the request being signed by the first domain;
verifying the request; and
based on the verifying and based on the permissions for the application, providing at least one token for a service back to the first domain, the at least one token including an identifier for the service and a signature of the network element.
3. The method of claim 2 , wherein the token further includes an expiration time.
4. The method of claim 1 , wherein the controlling access comprises:
receiving a request from a domain bridge on the first domain, the request being signed by the first domain and including an application identifier;
verifying the request; and
based on the verifying and based on the permissions for an application associated with the application identifier, providing at least one token for a service back to the domain bridge, the at least one token including an identifier for the service and a signature of the network element.
5. The method of claim 1 , wherein the controlling access comprises:
receiving a request from the first domain to synchronize the second table; and
providing the second table to the first domain.
6. The method of claim 1 , wherein the table with services further includes delegation of permissions for at least one of the services.
7. The method of claim 1 , wherein the first domain and the edge domain belong to a vehicle, and wherein the network element is a fleet manager.
8. A network element for securely sharing services across domains, the network element comprising:
a processor; and
a communications subsystem,
wherein the network element is configured to:
receive a request at the network element to add a first domain and an edge domain to a system;
populate, in the network element, a table with services, the services being provided by the first domain or the edge domain;
populate, in the network element, a second table with applications installed at the first domain or edge domain and permissions corresponding to a subset of the services; and
control access to the services by the applications based on the permissions.
9. The network element of claim 8 , wherein the network element is configured to control access by:
receiving a request from an application on the first domain, the request being signed by the first domain;
verifying the request; and
based on the verifying and based on the permissions for the application, providing at least one token for a service back to the first domain, the at least one token including an identifier for the service and a signature of the network element.
10. The network element of claim 9 , wherein the token further includes an expiration time.
11. The network element of claim 8 , wherein the network element is configured to control access by:
receiving a request from a domain bridge on the first domain, the request being signed by the first domain and including an application identifier;
verifying the request; and
based on the verifying and based on the permissions for an application associated with the application identifier, providing at least one token for a service back to the domain bridge, the at least one token including an identifier for the service and a signature of the network element.
12. The network element of claim 8 , wherein the network element is configured to control access by:
receiving a request from the first domain to synchronize the second table; and
providing the second table to the first domain.
13. The network element of claim 8 , wherein the table with services further includes delegation of permissions for at least one of the services.
14. The network element of claim 8 , wherein the network element is configured to provision during manufacture of a computing device with the first domain and the edge domain.
15. The network element of claim 8 , wherein the network element is configured to provision when a computing device with the first domain and the edge domain is at a trusted service center.
16. The network element of claim 8 , wherein the first domain and the edge domain belong to a vehicle, and wherein the network element is a fleet manager.
17. A non-transitory computer readable medium for storing instruction code, which, when executed by a processor of a network element configured for securely sharing services across domains cause the network element to:
receive a request at the network element to add a first domain and an edge domain to a system;
provision a public key of the network element to the first domain and the edge domain;
receive a public key of the first domain;
populate, in the network element, a table with services, the services being provided by the first domain or the edge domain;
populate, in the network element, a second table with applications installed at the first domain or edge domain and permissions corresponding to a subset of the services; and
control access to the services by the applications based on the permissions.
18. The computer readable medium of claim 17 , wherein the instruction code further causes the network element to control access by:
receiving a request from an application on the first domain, the request being signed by the first domain;
verifying the request; and
based on the verifying and based on the permissions for services for the application, providing at least one token for a service back to the first domain, the at least one token including an identifier for the service and a signature of the network element.