CHTS requirement clause

4.6.2.4 — GPF Security Credentials

12 technical records havebeen identified at this reference: 12 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.

GPFMixed touchpointsSRV touchpoint
12

Atomic items

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

16

Documented touchpoints

Typed relationships supported by source mapping rows.

2

Linked SRVs

Unique retained services reached through exact control rows.

0

Linked alerts

Explicit requirement-to-alert references.

CHTS4.6.2.4 · item PublicKeySecurityCredentialsStore.method: provideCredentialsDetails

PublicKeySecurityCredentialsStore - provideCredentialsDetails

SRV touchpoint

The method used to read details of the Remote Party Security Credentials currently held on a Device.

Object
PublicKeySecurityCredentialsStore
Attribute / method
method: provideCredentialsDetails
Interface disposition
E
Category
Method
Section 20 meaning
The method used to read details of the Remote Party Security Credentials currently held on a Device.

Documented touchpoints

Evidence:source paragraph 476, 477Section 20 row 1254

CHTS4.6.2.4 · item PublicKeySecurityCredentialsStore.methodInput: authorisingRemotePartyIdentifier

PublicKeySecurityCredentialsStore - authorisingRemotePartyIdentifier

Mixed touchpoints

Identifies the Trust Anchor Cell containing the Public Key to be used in authenticating this Command.

Object
PublicKeySecurityCredentialsStore
Attribute / method
methodInput: authorisingRemotePartyIdentifier
Interface disposition
E
Category
Method Input
Section 20 meaning
Identifies the Trust Anchor Cell containing the Public Key to be used in authenticating this Command.

Documented touchpoints

Evidence:source paragraph 476, 477Section 20 row 1255

CHTS4.6.2.4 · 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 476, 477Section 20 row 1256

CHTS4.6.2.4 · 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 476, 477Section 20 row 1257

CHTS4.6.2.4 · 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 476, 477Section 20 row 1270

CHTS4.6.2.4 · item PublicKeySecurityCredentialsStore.methodInput: remotePartyRoleDetailRequired[1..6].remotePartyRole

PublicKeySecurityCredentialsStore - remotePartyRoleDetailRequired remotePartyRole

SRV touchpoint

The list of RemotePartyRoles for which details are required

Object
PublicKeySecurityCredentialsStore
Attribute / method
methodInput: remotePartyRoleDetailRequired[1..6].remotePartyRole
Interface disposition
E
Category
Method Input
Section 20 meaning
The list of RemotePartyRoles for which details are required

Documented touchpoints

Evidence:source paragraph 476, 477Section 20 row 1847

CHTS4.6.2.4 · item PublicKeySecurityCredentialsStore.methodOutput: remotePartyRoleDetailRequired[1..6].remotePartyRole

PublicKeySecurityCredentialsStore - remotePartyRoleDetailRequired remotePartyRole

Mixed touchpoints

The remotePartyRole to which this part of the response / alert relates

Object
PublicKeySecurityCredentialsStore
Attribute / method
methodOutput: remotePartyRoleDetailRequired[1..6].remotePartyRole
Interface disposition
E
Category
Method Output
Section 20 meaning
The remotePartyRole to which this part of the response / alert relates

Documented touchpoints

Evidence:source paragraph 476, 477Section 20 row 1848

CHTS4.6.2.4 · item PublicKeySecurityCredentialsStore.methodOutput: remotePartyRoleDetailRequired[1..6].trustAnchorCell[1..3].keyUsage

PublicKeySecurityCredentialsStore - remotePartyRoleDetailRequired trustAnchorCell keyUsage

Mixed touchpoints

The key usage of the public key in this trust anchor cell

Object
PublicKeySecurityCredentialsStore
Attribute / method
methodOutput: remotePartyRoleDetailRequired[1..6].trustAnchorCell[1..3].keyUsage
Interface disposition
E
Category
Method Output
Section 20 meaning
The key usage of the public key in this trust anchor cell

Documented touchpoints

Evidence:source paragraph 476, 477Section 20 row 1849

CHTS4.6.2.4 · item PublicKeySecurityCredentialsStore.methodOutput: remotePartyRoleDetailRequired[1..6].trustAnchorCell[1..3].cellUsage

PublicKeySecurityCredentialsStore - remotePartyRoleDetailRequired trustAnchorCell cellUsage

Mixed touchpoints

Whether this cell is used for prepayment top ups only or used more widely

Object
PublicKeySecurityCredentialsStore
Attribute / method
methodOutput: remotePartyRoleDetailRequired[1..6].trustAnchorCell[1..3].cellUsage
Interface disposition
E
Category
Method Output
Section 20 meaning
Whether this cell is used for prepayment top ups only or used more widely

Documented touchpoints

Evidence:source paragraph 476, 477Section 20 row 1850

CHTS4.6.2.4 · item PublicKeySecurityCredentialsStore.methodOutput: remotePartyRoleDetailRequired[1..6].trustAnchorCell[1..3].remotePartyIdentifier

PublicKeySecurityCredentialsStore - remotePartyRoleDetailRequired trustAnchorCell remotePartyIdentifier

SRV touchpoint

The Entity Identifier of the Remote Party to which the Public Key in this Trust Anchor Cell relates.

Object
PublicKeySecurityCredentialsStore
Attribute / method
methodOutput: remotePartyRoleDetailRequired[1..6].trustAnchorCell[1..3].remotePartyIdentifier
Interface disposition
E
Category
Method Output
Section 20 meaning
The Entity Identifier of the Remote Party to which the Public Key in this Trust Anchor Cell relates.

Documented touchpoints

Evidence:source paragraph 476, 477Section 20 row 1851

CHTS4.6.2.4 · item PublicKeySecurityCredentialsStore.methodOutput: remotePartyRoleDetailRequired[1..6].trustAnchorCell[1..3].publicKeyIdentifier

PublicKeySecurityCredentialsStore - remotePartyRoleDetailRequired trustAnchorCell publicKeyIdentifier

SRV touchpoint

The SHA-1 hash of the public key held in this Trust Anchor cell

Object
PublicKeySecurityCredentialsStore
Attribute / method
methodOutput: remotePartyRoleDetailRequired[1..6].trustAnchorCell[1..3].publicKeyIdentifier
Interface disposition
E
Category
Method Output
Section 20 meaning
The SHA-1 hash of the public key held in this Trust Anchor cell

Documented touchpoints

Evidence:source paragraph 476, 477Section 20 row 1852

CHTS4.6.2.4 · item PublicKeySecurityCredentialsStore.methodOutput: remotePartyRoleDetailRequired[1..6].updateCredentialsExecutionCounter

PublicKeySecurityCredentialsStore - remotePartyRoleDetailRequired updateCredentialsExecutionCounter

SRV touchpoint

The current value of the Device's Execution Counter for this RemoteParty's use of the Update Security Credentials Command

Object
PublicKeySecurityCredentialsStore
Attribute / method
methodOutput: remotePartyRoleDetailRequired[1..6].updateCredentialsExecutionCounter
Interface disposition
E
Category
Method Output
Section 20 meaning
The current value of the Device's Execution Counter for this RemoteParty's use of the Update Security Credentials Command

Documented touchpoints

Evidence:source paragraph 476, 477Section 20 row 1857

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.