CoreLockrTM is a Security Enforcement Supervisor. CoreLockr’s primary function is to provide a separation between application logic and hardware resources thereby providing a greater degree of security. CoreLockrTM also makes it easy to deploy Cryptography modules by abstracting away all the complexity involved in deploying them. Another benefit of CoreLockrTM is delivered by its optional Policy Query Module which makes devices responsive to externally hosted policy definitions.
What platforms and modules does CoreLockr™ support?
CoreLockrTM supports microcontrollers, microprocessors and a variety of peripherals. Supported platforms include:
Microcontrollers based on ARM® Cortex-M and chips implementing the MIPS microAptive.
Microprocessor based on ARM® Cortex®-A based chips architecture.
Cryptography modules: CoreLockrTM also supports Atmel® Corporation’s ATECC508A, ATAES132 and ATECC108A line of cryptographic chips. More information about these products can be found here.
Other peripherals such as sensors that may be part of your product design are easily “registered” with CoreLockrTM and can be exposed via APIs. CoreLockrTM is extensible and new APIs and service functions can easily be added.
Who should use CoreLockr™?
Anyone building IoT and embedded devices can use and benefit from using CoreLockrTM. CoreLockrTM makes it easy to secure your device whether that device is being used as an industrial control or for smart cities or even wearables. Sequitur also provides services to help you with your design and implementation of CoreLockrTM. Call us!
What kind of secure applications can I develop with CoreLockr™?
There is no restriction on the kind of applications that can be built using CoreLockrTM.
How does CoreLockr™ simplify my application development?
CoreLockrTM implements an abstraction layer and service model. A simple registration mechanism allows registering your on-board hardware components with CoreLockrTM. CoreLockrTM exposes those capabilities as easy to consume software services so that you, as a developer, don’t need to worry about the underlying hardware implementation. This not only saves a lot of time during initial development, but also decreases migration costs when you decide to upgrade the hardware.
Is CoreLockr™ an OS?
CoreLockrTM is not an OS although it does share some characteristics of an OS—such as providing separation of resources.
Do I need an RTOS or an OS in order to use CoreLockr™?
No, you do not need any kind of OS. CoreLockrTM is OS agnostic. CoreLockrTM can be deployed on bare metal.
I already use an RTOS. Why should I use CoreLockr™?
An RTOS is a good solution if you need real-time capabilities. Using an RTOS however does not necessarily mean your device is secure or manageable. While some RTOS enable memory management and provide some degree of separation of resources, it doesn’t necessarily secure your device or your application. They don’t address the complexity of deploying security hardware and deploying crypto modules which can be an arduous process requiring you to understand pin-muxing and configurations. CoreLockrTM is optimized for simplifying security component deployment and for enforcing security. RTOSs provide a very rudimentary level of manageability.
How do I get CoreLockr™?
We are working with chip makers who will make CoreLockrTM available as part of their board support packages (BSP). At present, this is the only way to obtain CoreLockrTM.
Still have questions?
Contact us and we will get back to you as soon as possible