Search
5 result(s) for SecureElement
-
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding3.1.18 SecureElementSecureElement a hardware component that protects Private Keys from unauthorized access and disclosure
-
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboardingupdate firmware after onboarding in the OwnerOperator's system. A Device should have SecureElement storage used for security sensitive elements such as Private Keys . This storage cannot be backed
-
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding4.3.6 DecommissioningOwnerOperator may wish to prevent the Device from being used again by removing/destroying the SecureElement or some other method to physically disable the Device
-
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding5.1 Device Identitysame keypair as the IDevID Certificate . The Private Key should be placed in SecureElement storage on the Device . The ProductInstanceUri should also be affixed to the Device in a form ... IDevID and LDevID Certificates depend on the Manufacturer , however, Devices should provide a SecureElement storage (for an example, see ISO/IEC 11889 ) to ensure the associated Private Keys cannot be copied
-
OPC-30300 – Using Generic Trust Anchor (GTA) API with OPC UA - Part 1: Generic Trust Anchor (GTA) API Profile for OPC UA3.2.4 SecureElement (SE)SecureElement (SE) component capable of securely hosting functionalities, or confidential and cryptographic data, or both in accordance with well-defined rules and security requirements Note 1 to entry: A typical ... solution for a SecureElement is a one chip microcontroller. Note 2 to entry: Cryptographic keys are an example of confidential and cryptographic data. Note 3 to entry: A SecureElement