2.2 How Our Products Can Help

The ATECC608 is a technology enabler that provides IACS product suppliers with the means to satisfy the component requirements mandated by ISA/IEC 62443-4-2. Below is a list of cryptographic features and security protection of the ATECC608 that will be later mapped against the ISA/IEC 62443 specification.

Table NamingFeatures
SHA256SHA-256 & HMAC Hash including off-chip context save/restore.
Secure Key StorageJIL High secure storage for up to 16 keys, certificates or data.
ECDSAECDSA: FIPS186-3 Elliptic Curve Digital Signature (Sign/verify).
ECDH ECDH: FIPS SP800-56A Elliptic Curve Diffie-Hellman.
ECCP256 NIST Standard P256 Elliptic Curve Support.
PRF/HDKF Turnkey PRF/HKDF Calculation for TLS 1.2 & 1.3.
Ephemeral Key Ephemeral Key Generation and Key Agreement in SRAM.
Message Encryption Small Message Encryption with Keys Entirely Protected.
AEC128/GCM AES-128: Encrypt/Decrypt, Galois Field Multiply for GCM.
RNG Internal High-Quality NIST SP 800-90A/B/C Random Number Generator (RNG).
Key Rotation

Private Key Rotation and public key attestation are effectively possible and pre-configured in the ATECC608 TrustFLEX for convenience

Public Key Rotation is also effectively possible and and pre-configured in the ATECC608 TrustFLEX for convenience. It will be an essential feature for late stage key provisioning.

Tamper Protection Physical Tamper and Side Channel Attack Protection.
Secure Key Provisioning Microchip in-house Secure Key Provisioning leveraging HSM network and Late Stage Provisioning possible.
Secure Boot ECC-P256 ECDSA Verify for Signature Verification.
Key Disable The secure element has the capability to Disable Key following logic conditions defined by the developer.
Secure Key ProvisioningMicrochip in-house Secure Key Provisioning service allows customers to leverage our factory equipped with Hardware Secure Module (HSM) and isolate cryptographic keys from third party manufacturers. Late Stage Provisioning is possible (contact Microchip).

The ISA/IEC 62443 is calling for “secure key storage” or protection of the cryptographic keys. This is not a vague term in security but rather a specific feature the silicon is designed with. A secure key storage or the act of protecting keys consists of implementing a physical secure boundary wherein both the crypto-operations and cryptographic keys live. If keys and algorithms are not in that same secure boundary, the keys will be exposed at some point during transactions. This is where the essence of secure elements like the ATECC608 start to bring their contribution to a successful certification. Secure elements are secure key storage devices tested against the Joint Interpretation Library (JIL) rating scale from the Common Criteria practices to evaluate its robustness to protect keys.

Following the value of secure key storage, loading keys in such a device location following a secure manufacturing process comes up immediately as the next question. Microchip has factories equipped with a network of managed hardware security modules (HSM) that enable our customers to leverage our secure key provisioning service. By onboarding the secure element with this service, customers follow a controlled secret key exchange process that binds the credentials securely stored in the device to their own chain of trust or their client’s chain of trust without exposing the various cryptographic keys to any third party such as contract manufacturers. In complementary fashion, Microchip’s secure element can enable late-stage provisioning when an end-customer desires to activate the cryptographic keys late in the provisioning process.

The table below refers to the component requirements defined in ISA/IEC 62443-4-2, and provides indications on how the ATECC608 can act as a technology enabler to help the client’s product meet each of the requirements. The Security Level (SL) is specified for each CR and Cryptographic feature listed in the table below.

The ISA/IEC 62443 standard defines the requirements for four types of components:

  • Embedded Devices (EDR)
  • Software Applications (SAR)
  • Host Devices (HDR)
  • Network Devices (NDR).

Those component requirements that apply to all types of components are marked as “CR”, while the other requirements are marked according to the component type that they apply to (respectively: EDR, SAR, HDR, NDR).

When reading the table below, keep in mind the RE is associated to the CR of the same base paragraph. For example, “CR 1.1 RE(1) Unique identification and authentication” is part of the “CR1.1 Human user identification and authentication”.

Functional RequirementAssociated Requirements:
Component Requirement (CR)Component Requirement Enhancement (RE)SAR EDR HDR HDR Requirements SAR EDR HDR HDR EnhancementsTitle

NIST SP 800-90A/B/C
(RNG)

ECC-P256

ECDSA P256 FIPS186-3
(Sign/verify)

ECDH FIPS SP800-56A

Ephemeral key and key
agreement in SRAM

PRF/HKDF for
TLS 1.2 & 1.3

SHA-256 & HMAC
with save/restore

AES-128: GCM,
Encrypt/Decrypt

Message encryption with
protected keys

JIL High secure
key storage

Tamper protectionKey rotationKey disableSecurebootSecure key provisioningFeatures and Usage
CR. 1.1 Human User Identification and Authentication 1 Hash functionality combined with the secure key storage capabilities enable robust management of integrity checks on password files.
CR 1.1 RE (1) Unique Identification and Authentication 2 Hash functionality combined with the secure key storage capabilities enable robust management of integrity checks on password files.
CR 1.2 Software Process and Device Identification and Authentication 2222 22 2JIL High Secure storage of keys and certificates, and digital signature verification and generation capabilities enable secure identification and authentication.
CR 1.2 RE(1) Unique Identification and Authentication 3333 33 3JIL High Secure storage of keys and certificates, and digital signature verification and generation capabilities enable secure identification and authentication.
CR 1.5 Authenticator Management 11 111111 1Cryptographic key generation and secure storage capabilities enable robust initialization and lifecycle management for keys via hardware.
CR 1.5 RE(1) Hardware Security for Authenticators 33 333333 3Cryptographic key generation and secure storage capabilities enable robust initialization and lifecycle management for keys via hardware.
CR 2.4 SAR 2.4 EDR 2.4 HDR 2.4 NDR 2.4 Mobile Code 111 11 1111 1Hash functionality and secure storage capabilities enable robust management of integrity checks on code and data.
SAR 2.4 RE(1) EDR 2.4 RE(1) HDR 2.4 RE(1) NDR2.4 RE(1)Mobile Code Authenticity Check 2222 2222 2Secure storage of keys and certificates, and digital signature verification and generation capabilities enable authentication of code and data.
CR2.12 Non-Repudiation1111 1 Hash functionality and secure storage capabilities enable robust management of integrity checks on audit information. Secure storage of keys and certificates, and digital signature verification and generation capabilities enable authentication of audit information.
CR2.12 CR2.12 RE(1) Non-Repudiation for All Users4444 4 Hash functionality and secure storage capabilities enable robust management of integrity checks on audit information. Secure storage of keys and certificates, and digital signature verification and generation capabilities enable authentication of audit information.
CR3.1 Communication Integrity 1 Secure storage of keys and certificates, and digital signature verification and generation capabilities enable assurance of integrity and authenticity of transmitted information. Cryptographic engines for standard symmetric-key and asymmetric-key algorithms and for hashing enable support of common communication cypher suites.
CR3.1CR3.1 RE(1) Communication Authentication 2222 2 222222 2Networking key management support enables support for standard cryptographic communication protocols such as TLS.
CR3.4 Software and Information Integrity 1 1111 1Hash functionality and secure storage capabilities enable robust management of integrity checks on code and data.
CR3.4 CR3.4 RE(1) Authenticity of Software and Information 222 2222 2Secure storage of keys and certificates, and digital signature verification and generation capabilities enable authentication of code and data.
CR3.8 Session Integrity 2 22 22 Networking key management support and the internal RNG provide the capability to generate robust unique session identifiers.
CR3.10 EDRE3.10.1, HD RE3.10.1, ND RE3.10.1 Update Authenticity and Integrity 222 222222222Secure storage of keys and certificates, digital signature verification and generation capabilities, HW support for asymmetric and symmetric algorithms and for hashing functions enable authentication and integrity verification of SW updates.
CR3.12 EDR3.12 HDR3.12 NDR3.12 Provisioning Product Supplier Roots of Trust 2222 2Secure storage capabilities are available for protecting product supplier roots of trust.
CR3.13 EDR3.13 HDR3.13 NDR3.13 Provisioning Asset Owner Roots of Trust 2222 2Secure storage capabilities are available for protecting asset owner roots of trust.
CR3.14 EDR3.14 HDR3.14 NDR3.14 Integrity of Boot Process 11 1 Secure boot support is provided through internal signature validation mechanisms and secure storage of digests/signatures.
CR3.14 EDRE3.14.1, HDRE3.14.1, NDRE3.14.1 Authenticity of the Boot Process 22 2 Secure boot support is provided through internal signature validation mechanisms and secure storage of digests/signatures.
CR4.1 Information Confidentiality 111 11 1111 1Secure encrypted storage is directly provided for up to 16 keys, certificates or data. Additionally, HW support for symmetric algorithms and key storage capabilities enable encryption of externally stored data.
CR4.3 Use of Cryptography 111 11 Secure encrypted storage is directly provided for up to 16 keys, certificates or data. Additionally, HW support for symmetric algorithms and key storage capabilities enable encryption of externally stored data.
CR4.3CR7.3 RE(1) Backup Integrity Verification 2 2222 2Hash functionality and secure storage capabilities enable robust management of integrity checks on backup data.
CR7.4 Control System Recovery and Reconstitution 1 1111 1Hash functionality and secure storage capabilities enable robust management of integrity checks on backup data.

Index Value :      1 = SL1        2 = SL2       3 = SL3      4 = SL4