This repository contains a target-agnostic Software Framework for the OPTIGA™ Trust M security solution. It is a base for other application notes.
Be aware that this software comes without any security claims and shall be used for evaluation purpose.
- High-end security controller
- Common Criteria Certified EAL6+ (high) hardware
- Turnkey solution
- Up to 10kB user memory
- PG-USON-10 package (3 x 3 mm)
- Temperature range (−40°C to +105°C)
- I2C interface with Shielded Connection (encrypted communication)
- Cryptographic support:
- ECC : NIST curves up to P-521, Brainpool r1 curve up to 512,
- RSA® up to 2048
- AES key up to 256 , HMAC up to SHA512
- TLS v1.2 PRF and HKDF up to SHA512
- Crypto ToolBox commands for SHA-256, ECC and RSA® Feature, AES, HMAC and Key derivation
- Configurable device security monitor, 4 Monotonic up counters
- Protected(integrity and confidentiality) update of data, key and metadata objects
- Hibernate for zero power consumption
- Lifetime for Industrial Automation and Infrastructure is 20 years and 15 years for other Application Profiles
| Features | Supported Curve/Algorithm | V1 | V3 |
|---|---|---|---|
| ECC | ECC NIST P256/384 | ✓ | ✓ |
| ECC NIST P521, ECC Brainpool P256/384/512 r1 | ✓ | ||
| RSA | RSA® 1024/2048 | ✓ | ✓ |
| Key Derivation | TLS v1.2 PRF SHA 256 | ✓ | ✓ |
| TLS v1.2 PRF SHA 384/512 | ✓ | ||
| HKDF SHA-256/384/512 | ✓ | ||
| AES | Key size - 128/192/256 (ECB, CBC, CBC-MAC, CMAC) | ✓ | |
| Random Generation | TRNG, DRNG, Pre-Master secret for RSA® Key exchange | ✓ | ✓ |
| HMAC | HMAC with SHA256/384/512 | ✓ | |
| Hash | SHA256 | ✓ | ✓ |
| Protected data (object) update (Integrity) | ECC NIST P256/384 RSA® 1024/2048 Signature scheme as ECDSA FIPS 186-3/RSA SSA PKCS#1 v1.5 without hashing |
✓ | ✓ |
| ECC NIST P521, ECC Brainpool P256/384/512 r1 Signature scheme as ECDSA FIPS 186-3/RSA SSA PKCS#1 v1.5 without hashing |
✓ | ||
| Protected Data/key/metadata update (Integrity and/or confidentiality) | ECC NIST P256/384/521 ECC Brainpool P256/384/512 r1 RSA® 1024/2048 Signature scheme as ECDSA FIPS 186-3/RSA SSA PKCS#1 v1.5 without hashing |
✓ |
There are three main provisioning options/confgiurations availble:
Note: All three configuration options have no effect on the corresponding features. For example, OPTIGA™ Trust M Express has the same features as OPTIGA™ Trust M V3, also the same API and hostcode can be used to work with all three solutions.
- OPTIGA™ Trust M V1/V3 - a provisioning configuration which comes as a standard for all shipped devices. Unless mentioned differently all OPTIGA™Trust M chips on the market have this configuration.
- OPTIGA™ Trust M Custom - a custom provisioning option done on demand upon reaching a MoQ. Fully customisable solution including Security Monitor Configuration
- Please get in touch with your local Infineon Sales Representative to get more information
- OPTIGA™ Trust M Express - a provisioning configuration which can be ordered standalone. This variant comes with three certificates/private keys pre-provisioned by Infineon. Certificates and communication secrets data can be downloaded through the CIRRENT™ Cloud ID
- OPTIGA™ Trust M MTR - a provisioning configuration which can be ordered standalone. This variant comes with three certificates/private keys pre-provisioned by Infineon. The first certificate and key are meant to be used for Matter Device Attestation. Certificates and communication secrets data can be downloaded through Kudelski keySTREAM.
| V1 | V3 | Express | MTR³ | |||||
|---|---|---|---|---|---|---|---|---|
| Certificate - Private Key |
Certificate - Private Key |
Certificate¹ - Private Key | Certificate¹ - Private Key | |||||
| Object IDs | E0E0 - E0F0 | E0E0 - E0F0 | E0E0 - E0F0 | E0E1 - E0F1 | E0E2 - E0FC | E0E0 - E0F0 | E0E1 - E0F1 | E0E2 - E0FC |
| PKI Top Level | ECC Root CA1 | ECC Root CA2 | ECC Root CA2 | ECC Root CA2 | RSA Root CA2 | ECC Root CA2 | ECC Root CA2 | RSA Root CA2 |
| PKI Intermediate Level | Int. CA 101 | Int. CA 300 | Int. CA 306 | Int. CA 306 | Int. CA 309 | Int. CA 306 | Int. CA 306 | Int. CA 309 |
| PKI Bottom Level: Key Algorithm | NIST P-256 | NIST P-256 | NIST P-256 | NIST P-256 | RSA2048 | NIST P-256 | NIST P-256 | RSA2048 |
| Possible to Readout | Yes | Yes | Yes | With PBS¹ | Yes | Yes | Yes | Yes |
| Possible to Update | Only Certificate | Only Certificate | Only Certificate with PBS¹ and Auth.Ref.¹ | Only Certificate with PBS¹ and Auth.Ref.¹ | Only Certificate with PBS¹ and Auth.Ref.¹ | Only Certificate: Always, if LcsO < Op, else with PBS¹ and Auth.Ref.¹ | Only Certificate with PBS¹ and Auth.Ref.¹ | Only Certificate with PBS¹ and Auth.Ref.¹ |
| Default Lifecycle State | Creation | Creation | Operational | Operational | Operational | Initialization | Operational | Operational |
| Common Name² | Static | Static | Unique | Unique | Unique | Unique | Unique | Unique |
¹ Certificate, Platform Binding Secret (PBS) and the Authorization Reference (Auth.Ref.) can be downloaded from CIRRENT™ Cloud ID (Express) or Kudelski keySTREAM (MTR) by claiming a Reel QR- or Bar- Code
² End Device Certificate Common Name has either the same value across all devices (Static), or has a chip-unique value (Unique)
³ It is expected from the Customer to perform "late-stage provisioning" on the OPTIGA™ Trust M MTR chips, i.e. to download the Matter Certificates (DAC/PAI) from Kudelski keySTREAM and inject into dedicated slots on the OPTIGA™ Trust M
In addition to the certificates and private keys each OPTIGA™ Trust M Express and OPTIGA™ Trust M MTR comes with a chip unique Platform Binding Secret¹ and an Authorization Reference¹. The latter are two unique per chip 64 bytes long data objects which serve the following purposes:
- Platform Binding Secret (PBS) used to establish a Shielded Connection between a Host MCU and OPTIGA™ Trust M. Should be transfered from the Cloud Service to the respective MCU to run a protected I2C connection; e.g. readout a protected Certificate located in the 0xE0E1 Object ID (see table above). For more details about Shielded Connection read here.
- Authorization Reference (Auth. Ref.). Used to update/change Certificate, PBS and the Authorization Reference itself. Similar to the PBS shall be tranfered to the Host MCU to be used. Find more details in the Solution Reference Manual
| OPTIGA™ Trust M Evaluation Kit | OPTIGA™ Trust IoT Security Development Kit | OPTIGA™ Trust M Shields in Combination with PSoC™ 62S2 Wi-Fi BT Pioneer Kit |
|---|---|---|
 |
 |
 |
Get started with the OPTIGA™ Trust M evaluation kit, with the OPTIGA™ Trust IoT Security Development kit or with any one of the available OPTIGA™ Trust M Shields (Shield2Go, Express Shield, MTR Shield) in combination with the PSoC™ 62S2 Wi-Fi BT Pioneer Kit using this Application Note.
- Get started guide
- ModusToolbox™ Code Examples
- Off-Chip TLS example (mbedTLS)
- Linux Command Line Interface
- Cloud:
- Zephyr OS driver
- Arduino library
- Personalize OPTIGA™ Trust
- Python package
- I2C Utilities
- See Trust M Crypt API and Trust M Util API to know more about CRYPT and UTIL modules
- Information about the OPTIGA™ Trust M Command Library (CMD) can be found in the Solution Reference Manual In the same document you can find explanation of all Object IDs (OIDs) available for users as well as detailed technical explanation for all features and envisioned use cases.
- Infineon I2C Protocol implementation details can be found here
- Platform Abstraction Layer (PAL) overview and Porting Guide are presented in the Wiki
For more information please refer to the Wiki page of this project
External links, open in the same tab.
-
Supply voltage VCC is max. 5.5 V, please refer to the OPTIGA™ Trust M datasheet for more details about maximum ratings
-
Ensure that no voltage applied to any of the pins exceeds the absolute maximum rating of VCC + 0.3 V
-
Pin out on top (head) is directly connected to the pins of the OPTIGA™ Trust M
-
If head is broken off, only one capacitor is connected to the OPTIGA™ Trust M
S2Go Security OPTIGA™ M Pinout
S2Go Security OPTIGA™ M Schematic
-
The product variant can be identified through the configuration LED.
-
The design of the Shield is for 3V3 VCC
-
Absolute max. rating of VCC is 5.5 V, please refer to the OPTIGA™ Trust M datasheet for more details about maximum ratings
-
Ensure that no voltage applied to any of the pins exceeds the absolute maximum rating of VCC + 0.3 V
-
Pin out of the shield is directly connected to the pins of the OPTIGA™ Trust M
OPTIGA™ Trust M [Variant] Shield Pinout
OPTIGA™ Trust M [Variant] Shield Schematic
- Initialisation hints (Wiki)
- Porting guide (Wiki)
- Crypto performance (Wiki)
- In which form does OPTIGA™return keys and signatures? (Wiki)
- Code Footprint (Wiki)
- Device Error Codes (Wiki)
- Protected Update for Data Objects
- Shielded Connection (Wiki)
- User API
- Hardware-Security: "Einfach (und) Sicher" (external link, opens in the same tab) in German, Slides in English
For high level description and some important excerpts from the documentation please refer to Wiki page
Other downloadable PDF documents can be found below:
- OPTIGA™ Trust M Datasheet v3.61 (PDF)
- OPTIGA™ Trust M Solution Reference Manual v3.60 (PDF)
- OPTIGA™ Trust M Keys and Certificates v3.10 (PDF)
- OPTIGA™ Trust Config Guide v2.20 (PDF)
- Infineon I2C protocol specification v2.03 (PDF)
If you are planning to integrate OPTIGA™ Trust M in your PCB design have a look at the recommendations found here (external, opens in the same tab).
Please read CONTRIBUTING.md for details on our code of conduct, and the process for submitting pull requests to us.
This project is licensed under the MIT License - see the LICENSE file for details
