View Issue Details

IDProjectCategoryView StatusLast Update
000952010000-002: SecuritySpecpublic2024-04-17 15:44
Reporterdziegler Assigned Torandyarmstrong  
PrioritynormalSeverityfeatureReproducibilityN/A
Status acknowledgedResolutionopen 
Summary0009520: Update SecurityPolicy [ECC-B] – ECC-nistP256 Encryption Algorithm
Description

The current implementation of SecurityPolicy [ECC-B] – ECC-nistP256 relies on AES128-CBC for encryption, as outlined in the specification. However, AES128-CBC should be considered for "legacy" systems only according to (H2020-ICT-2014 – Project 645421, D5.4, ECRYPT-CSA, 02/2018; available at https://www.ecrypt.eu.org/csa/documents/D5.4-FinalAlgKeySizeProt.pdf) , signaling the need for an update to more modern encryption variants.

The report highlights the necessity of transitioning to more robust encryption algorithms, such as AES-128-GCM, for enhanced security and resilience against evolving threats.

To address this concern and ensure the security of OPC UA implementations, it is proposed to update SecurityPolicy [ECC-B] – ECC-nistP256 to utilize AES-128-GCM instead of AES-128-CBC. This transition will align OPC UA with contemporary security practices and provide a stronger defense against potential vulnerabilities.

TagsSecurity
Commit Version
Fix Due Date

Activities

randyarmstrong

2024-04-17 15:44

administrator   ~0021133

Agreed that adding GCM profiles is best for the long term.
Need resources to do prototyping and propose any spec changes.
This is best handled by the FLC WG.

Issue History

Date Modified Username Field Change
2024-04-15 12:56 dziegler New Issue
2024-04-15 12:56 dziegler Tag Attached: Security
2024-04-17 15:44 randyarmstrong Assigned To => randyarmstrong
2024-04-17 15:44 randyarmstrong Status new => acknowledged
2024-04-17 15:44 randyarmstrong Note Added: 0021133