Services Overview

We focus on an end-to-end approach, from auditing and mapping vulnerabilities and up to helping with the implementation of the most advanced security mechanisms to your chips’ firmware. As presented in the Threats (hyperlink to threats page) section, the attack surface is extensive, thus requiring a dedicated team up to date with the latest security guidelines in order not to miss a specific threat.
Due to the sensitive nature of security vulnerabilities, we usually work under strict mutual NDAs with our customers to ensure maximum safety and privacy
Minimal Hardware Access – Mapping any debugging interfaces left from development (such as JTAG, SPI, or I2C) and reducing the attack surface.

Lock Logical Access – Restricting access as much as possible to sensitive system functions/storage. Platform functionality (e.g. CSM, SMM_BWP, BLE, BIOSWE, SPI Memory Protection) must be correctly configured to not allow unauthorized access.

  • Implementing security mechanisms (such as DEP, ASLR and logical access restrictions)
  • Static Code Analysis
  • Searching for buffer overflows, integer overflows and code vulnerabilities.
  • Searching for logical vulnerabilities in the code.
  • Going through the development lifecycle and relying on stable development platforms.
  • Using technologies like memory protection units or I/O MMUs.

Firmware Tamper Detection – employing mechanisms to detect firmware tampering such as timing anomalies and state anomalies.

Secure Firmware Update – This is a well explored field from the world of BIOS firmware update mechanism which had multiple vulnerabilities over the years. Main elements – Digitally signing signatures, key store for public keys, stopping hot-patching etc.

Customer Validation Tools – an approach where you give the customers tools to validate the integrity of the current state of the firmware. This approach reduces significantly the response time in case of a vulnerability disclosure.

Removing Management Backdoors – often manufacturers leave backdoor functionality in the firmware for future control, or supply a connect-back functionality (often referred as “phone home” functionality) – these should be tested and validated thoroughly.

User Awareness Process
– Creating a process to inform end users about both security functionality, security incidents, and available security updates.

Secure Key Storage – Considering the use of TPM, SIM, SmartCards, or other HSMs for storing private keys.

Default Configuration Analysis – Analysis of the default configuration the chip with special focus on authentication and the update mechanism.

Data Encryption - At Rest & In Transit – employing encryption on often limited CPU power requires expertise but is feasible. Aside from protecting the data itself, unencrypted data will often revoke compliances, specifically with entities such as HIPAA.

Remote Wiping – Specifically for compliance with mobile devices, this feature is necessary. And although is contradictory to the “Removing Management Backdoors” sections, should be considered in non-mobile chips as well.