SMETS requirement clause

5.7.4.18 — ESME Security Credentials

3 technical records havebeen identified at this reference: 3 Section 20 items and 0 explicit clause references. The links below describe documented interfaces and observable effects; they do not assert compliance with the source requirement.

ESMESRV touchpoint
3

Atomic items

Section 20 objects, attributes or methods at this source reference.

3

Documented touchpoints

Typed relationships supported by source mapping rows.

1

Linked SRVs

Unique retained services reached through exact control rows.

0

Linked alerts

Explicit requirement-to-alert references.

SMETS5.7.4.18 · item DeviceSecurityCredentials.methodInput: keyUsage

DeviceSecurityCredentials - keyUsage

SRV touchpoint

The key usage of the certificate requested

Object
DeviceSecurityCredentials
Attribute / method
methodInput: keyUsage
Interface disposition
E
Category
Method Input
Section 20 meaning
The key usage of the certificate requested

Documented touchpoints

Evidence:source paragraph 1469, 1470Section 20 row 1256

SMETS5.7.4.18 · item DeviceSecurityCredentials.methodOutput: certificate

DeviceSecurityCredentials - certificate

SRV touchpoint

The certificate returned

Object
DeviceSecurityCredentials
Attribute / method
methodOutput: certificate
Interface disposition
E
Category
Method Output
Section 20 meaning
The certificate returned

Documented touchpoints

Evidence:source paragraph 1469, 1470Section 20 row 1257

SMETS5.7.4.18 · item DeviceSecurityCredentials.method: provideSecurityCredentials

DeviceSecurityCredentials - provideSecurityCredentials

SRV touchpoint

Processing is as required in the GBCS in section 13 which will result in the device storing the data in DeviceSecurityCredentials(DigitalSigning).value, if all checks are passed

Object
DeviceSecurityCredentials
Attribute / method
method: provideSecurityCredentials
Interface disposition
E
Category
Method
Section 20 meaning
Processing is as required in the GBCS in section 13 which will result in the device storing the data in DeviceSecurityCredentials(DigitalSigning).value, if all checks are passed

Documented touchpoints

Evidence:source paragraph 1469, 1470Section 20 row 1270

How to read this page

Evidence is kept at record level

A source clause can contain several separately mapped Section 20 items and an explicit alert reference. One item may be read by an SRV, another updated by a different service, and another have only an Alert or local-HAN path. Accordingly, the clause summary does not collapse those distinctions into a single covered or uncovered result.