<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[DLMS Security Suite 1 vs Suite 2: ECDSA, ECDH, AES-GCM-256 and Key Agreement]]></title><description><![CDATA[<h3>Evolution of DLMS Cryptographic Security Suites</h3>
<p dir="auto">As smart grid cybersecurity requirements increase (e.g. BSI TR-03109 in Germany and IEC 62056-5-3 Ed. 3), systems are migrating from Security Suite 0 to Suite 1 and Suite 2.</p>
<h4>Comparison Matrix</h4>
<table class="table table-bordered table-striped">
<thead>
<tr>
<th style="text-align:left">Feature</th>
<th style="text-align:left">Suite 0</th>
<th style="text-align:left">Suite 1</th>
<th style="text-align:left">Suite 2</th>
</tr>
</thead>
<tbody>
<tr>
<td style="text-align:left"><strong>Symmetric Cipher</strong></td>
<td style="text-align:left">AES-GCM-128</td>
<td style="text-align:left">AES-GCM-128</td>
<td style="text-align:left">AES-GCM-256</td>
</tr>
<tr>
<td style="text-align:left"><strong>Key Wrap</strong></td>
<td style="text-align:left">AES-Key-Wrap-128</td>
<td style="text-align:left">AES-Key-Wrap-128</td>
<td style="text-align:left">AES-Key-Wrap-256</td>
</tr>
<tr>
<td style="text-align:left"><strong>Digital Signature</strong></td>
<td style="text-align:left">None / GMAC</td>
<td style="text-align:left">ECDSA P-256 / SHA-256</td>
<td style="text-align:left">ECDSA P-384 / SHA-384</td>
</tr>
<tr>
<td style="text-align:left"><strong>Key Agreement</strong></td>
<td style="text-align:left">Pre-shared Master Key</td>
<td style="text-align:left">ECDH (Ephemeral-Unified)</td>
<td style="text-align:left">ECDH (P-384)</td>
</tr>
<tr>
<td style="text-align:left"><strong>Hash Algorithm</strong></td>
<td style="text-align:left">GMAC</td>
<td style="text-align:left">SHA-256</td>
<td style="text-align:left">SHA-384</td>
</tr>
</tbody>
</table>
<p dir="auto">Suite 1 introduces public-key certificates (X.509 v3) directly into the meter, enabling digital signatures on meter billing records for legal non-repudiation.</p>
]]></description><link>https://dlms.sharur.org/topic/17/dlms-security-suite-1-vs-suite-2-ecdsa-ecdh-aes-gcm-256-and-key-agreement</link><generator>RSS for Node</generator><lastBuildDate>Fri, 16 Oct 2026 19:50:09 GMT</lastBuildDate><atom:link href="https://dlms.sharur.org/topic/17.rss" rel="self" type="application/rss+xml"/><pubDate>Sat, 22 Aug 2026 12:33:13 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to DLMS Security Suite 1 vs Suite 2: ECDSA, ECDH, AES-GCM-256 and Key Agreement on Sat, 22 Aug 2026 12:33:14 GMT]]></title><description><![CDATA[<p dir="auto">In Suite 1/2, certificate management requires COSEM Class 115 (<code>Certificate Management</code>). The HES can remotely query the meter's TLS/ECDSA root and leaf certificates, check revocation status via CRL, and renew credentials before expiration.</p>
]]></description><link>https://dlms.sharur.org/post/35</link><guid isPermaLink="true">https://dlms.sharur.org/post/35</guid><dc:creator><![CDATA[marcus_vance]]></dc:creator><pubDate>Sat, 22 Aug 2026 12:33:14 GMT</pubDate></item></channel></rss>