Parsec, the Platform Abstraction for Security project provides a micro-service that maps easy to consume security APIs in the language of choice to security primitives found in various hardware. Parsec is an opensource project that is part of the Cloud Native Compute Foundation sandbox.
As developers aim to secure their applications by tying them to root of trust, they inherently tie the application to specific security primitives. This inhibits the ability to move the applications freely from one platform to the next. To address this challenge, Parsec abstracts the security root of trust and provides a common set of APIs to the developer. This ensures that the same application can move freely from one architecture to another.
The initial overhead of incorporating Parsec into your security framework will provide benefits by simplifying steps such as signing a payload or provisioning keys. Parsec has been designed to interface with the security backends exposing simple to use security APIs.
By leveraging Parsec, moving your design to a new chipset with a different security primitive does not impose a change in the security commands in your apps. Building your platform with the right Parsec provider library to match your security primitive ensures your security interface will continue to work.
Multi-tenancy at the edge
Many security primitives found in edge devices are designed to service one client. In some cases, developers might need to isolate information between applications and therefore require isolation at an application level. Parsec framework defines a mechanism to enable multitenancy security at the edge.
|Not answered||access secure generic timer||0 votes||62 views||0 replies||Started 7 days ago by armsss||Answer this|
|Not answered||How do branch instructions influence the performance of Cortex-A77?||0 votes||75 views||0 replies||Started 9 days ago by hyf_sysu||Answer this|
|Suggested answer||Getting Dummy character while receiving UART data,How to fix it ?||0 votes||449 views||2 replies||Latest 9 days ago by Jerome Decamps - 杜尚杰||Answer this|
|Suggested answer||Sht11 interfacing with lpc1758||0 votes||125 views||1 replies||Latest 13 days ago by Andy Neil||Answer this|
|Suggested answer||Arm Cortex A57 controller||0 votes||280 views||1 replies||Latest 15 days ago by Tyler_p||Answer this|
|Not answered||M7 to NIC-400 connectivity via AXIM||0 votes||82 views||0 replies||Started 19 days ago by Ramaswamy Vishwanath||Answer this|
|Not answered||access secure generic timer Started 7 days ago by armsss||0 replies 62 views|
|Not answered||How do branch instructions influence the performance of Cortex-A77? Started 9 days ago by hyf_sysu||0 replies 75 views|
|Suggested answer||Getting Dummy character while receiving UART data,How to fix it ? Latest 9 days ago by Jerome Decamps - 杜尚杰||2 replies 449 views|
|Suggested answer||Sht11 interfacing with lpc1758 Latest 13 days ago by Andy Neil||1 replies 125 views|
|Suggested answer||Arm Cortex A57 controller Latest 15 days ago by Tyler_p||1 replies 280 views|
|Not answered||M7 to NIC-400 connectivity via AXIM Started 19 days ago by Ramaswamy Vishwanath||0 replies 82 views|