GBCS 16.2 / 0x8F4D
Device's own Digital Signing Certificate replacement succeeded
Cross-specification evidence
Technical requirement relationships
The source clauses below explicitly relate this alert to equipment behaviour. Confidence and evidence labels show how each relationship was established.
Alert touchpoint
5 clauses · 5 linked records- CHTS 4.5.1.10Exact evidence
1 direct clause reference
- Replace CHF Security Credentials
Evidence: gbcs_device_alert_extract_16.2.json · 16.2 · row 64 · reference 4.5.1.10
- SMETS 4.5.3.18Exact evidence
1 direct clause reference
- Replace GSME Security Credentials
GSMEEvidence: gbcs_device_alert_extract_16.2.json · 16.2 · row 64 · reference 4.5.3.18
- CHTS 4.5.4.8Exact evidence
1 direct clause reference
- Replace GPF Security Credentials
Evidence: gbcs_device_alert_extract_16.2.json · 16.2 · row 64 · reference 4.5.4.8
- SMETS 5.6.3.20Exact evidence
1 direct clause reference
- Replace ESME Security Credentials
ESMEEvidence: gbcs_device_alert_extract_16.2.json · 16.2 · row 64 · reference 5.6.3.20
- SMETS 9.5.2.11Exact evidence
1 direct clause reference
- Replace SAPC Security Credentials
SAPCEvidence: gbcs_device_alert_extract_16.2.json · 16.2 · row 64 · reference 9.5.2.11
Device Specific Details
- GSME
- N/A
- ESME
- N/A
- CHF
- N/A
- GPF
- N/A
Message Patterns and Examples
This row is not a WAN Alert, so it is never transmitted to the DSP or to a Known Remote Party and has no delivery pattern. It is recorded in a Device log and read through the corresponding log-read Service Request.