Content security at service layer
Existing approaches to security within network, for instance oneM2M networks, are limited. For example, content might only be protected while the content is in transit between entities that trust each other. Here, the integrity and the confidentiality of content in an M2M network are protected. Such content may be “at rest,” such that the content is stored at a hosting node. Only authorized entities may store and retrieve the data that is stored at the hosting node, and the data may be protected from a confidentiality perspective and an integrity perspective.
1. An apparatus for a service supporting service capabilities through a set of Application Programming Interfaces (APIs), the service being provided as middleware between application protocols and a plurality of applications, the apparatus comprising circuitry configured to:
receive, from an entity hosting an application of the plurality of applications via at least one of the set of APIs, a first request to create one or more credentials for encrypting or integrity protecting application content when stored at rest on a first service entity of the service; and
send, based on the request and to the entity, the one or more credentials comprising a credential identifier obtained from a second service entity of the service,
wherein the entity is configured to send, to the service, a second request to create a resource that stores application content that is encrypted or integrity protected by the service, the resource being a uniquely addressable element in a Resource Oriented Architecture (ROA) having representation that can be manipulated via RESTful methods, the second request comprising the one or more credential identifiers for encrypting or integrity protecting the application content.
2. The apparatus as recited in claim 1 , wherein the one or more credentials comprise a master key for symmetric key confidentiality protection.
3. The apparatus as recited in claim 1 , wherein the second service entity corresponds to a trust enablement function.
4. The apparatus as recited in claim 3 , wherein a second entity hosting an application of the plurality of applications that is authorized to obtain the content can obtain the one or more credentials from the trust enablement function or the apparatus.
5. The apparatus as recited in claim 1 , wherein the first request is based on one or more security parameters associated with the application content.
6. The apparatus as recited in claim 1 , wherein the first service entity is a middleware entity located on top of network protocol stacks, wherein the middleware entity is in service layer for IoT services.
7. The apparatus as recited in claim 6 , wherein the service layer is defined according to ETSI/oneM2M standards.
8. A method for a service supporting service capabilities through a set of Application Programming Interfaces (APIs), the service being provided as middleware between application protocols and a plurality of applications, the method comprising:
receiving, from an entity hosting an application of the plurality of applications via at least one of the set of APIs, a first request to create one or more credentials for encrypting or integrity protecting application content when stored at rest on a first service entity of the service; and
sending, based on the request and to the entity, the one or more credentials comprising a credential identifier obtained from a second service entity of the service,
wherein the entity is configured to send, to the service, a second request to create a resource that stores application content that is encrypted or integrity protected by the service, the resource being a uniquely addressable element in a Resource Oriented Architecture (ROA) having representation that can be manipulated via RESTful methods, the second request comprising the one or more credential identifiers for encrypting or integrity protecting the application content.
9. The method as recited in claim 8 , wherein the one or more credentials comprise a master key for symmetric key confidentiality protection.
10. The method as recited in claim 8 , wherein the first request is based on one or more security parameters associated with the application content.
11. The method as recited in claim 8 , wherein the first service entity is a middleware entity located on top of network protocol stacks, wherein the middleware entity is in service layer for IoT services.
12. The method as recited in claim 11 , wherein the service layer is defined according to ETSI/oneM2M standards.
13. The method as recited in claim 8 , wherein the second service entity corresponds to a trust enablement function.
14. The method as recited in claim 13 , wherein a second entity hosting an application of the plurality of applications that is authorized to obtain the content can obtain the one or more credentials from the trust enablement function or the apparatus.
15. An apparatus comprising circuitry configured to:
send, to a service supporting service capabilities through a set of Application Programming Interfaces (APIs), the service being provided as middleware between application protocols and a plurality of applications, the apparatus, a first request to create one or more credentials for encrypting or integrity protecting application content when stored at rest on a first service entity in the service;
receive, based on the request and from the service, the one or more credentials comprising a credential identifier obtained from a second service entity of the service; and
send, to the service, a second request to create a resource that stores application content that is encrypted or integrity protected by the service, the resource being a uniquely addressable element in a Resource Oriented Architecture (ROA) having representation that can be manipulated via RESTful methods, the second request comprising the one or more credential identifiers for encrypting or integrity protecting the application content.
16. The apparatus as recited in claim 15 , wherein the one or more credentials comprise a master key for symmetric key confidentiality protection.
17. The apparatus as recited in claim 15 , wherein the second service entity corresponds to a trust enablement function.
18. The apparatus as recited in claim 17 , wherein a second entity hosting an application of the plurality of applications that is authorized to obtain the content can obtain the one or more credentials from the trust enablement function or the apparatus.
19. The apparatus as recited in claim 15 , wherein the first service entity is a middleware entity located on top of network protocol stacks, wherein the middleware entity is in service layer for IoT services.
20. The apparatus as recited in claim 19 , wherein the service layer is defined according to ETSI/oneM2M standards.