hlr-55-certificate-transparency

Name: hlr-55-certificate-transparency
Availability: InStock
Author: Sourcelab

Enforce EUDI Certificate Transparency requirements for access certificates and SCT verification.

Updated Mar 7, 2026

Search Tags:#security #compliance #eud #certificate transparency #access certificates #sct

Ready to run

npx skills add https://github.com/sourcelabbg/eudi-knowledge --skill hlr-55-certificate-transparency

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: hlr-55-certificate-transparency
Source: https://github.com/sourcelabbg/eudi-knowledge/tree/main/.ai/skills/hlr-55-certificate-transparency
Command: npx skills add https://github.com/sourcelabbg/eudi-knowledge --skill hlr-55-certificate-transparency

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the critical need for compliance with EUDI high-level requirements concerning Certificate Transparency (CT) for access certificates, ensuring secure and verifiable issuance and verification processes.

Core Features & Use Cases

CT Log Registration: Enforces the requirement for Access CAs to register issued access certificates in CT logs.
SCT Verification: Mandates that Wallet Units verify the presence and validity of Signed Certificate Timestamps (SCTs) during certificate verification.
Failure Handling: Defines clear procedures for handling access certificates that lack valid SCTs, aligning with broader authentication requirements.
Use Case: An Access CA needs to ensure all its issued access certificates are logged and verifiable. A Wallet Unit needs to confirm the integrity of an access certificate before accepting it for a presentation.

Quick Start

Use the hlr-55-certificate-transparency skill to verify that an access certificate includes a valid Signed Certificate Timestamp.

Frequently Asked Questions about hlr-55-certificate-transparency

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

What is Certificate Transparency compliance for EUDI access certificates?▼

Certificate Transparency compliance requires Access CAs to register issued access certificates in CT logs and include Signed Certificate Timestamps (SCTs) for verification by Wallet Units during issuance and presentation flows.

How do I verify a Signed Certificate Timestamp in an access certificate?▼

To verify an SCT, Wallet Units check the presence and validity of the Signed Certificate Timestamp within the access certificate during the verification process, rejecting certificates that lack valid SCTs according to normative requirements.

What happens if an access certificate lacks a valid SCT during EUDI presentation?▼

If an access certificate lacks a valid SCT during presentation, failure handling procedures are triggered, aligning with broader authentication requirements to securely reject the unverified certificate by the Wallet Unit.

Does my Access CA need to register access certificates in CT logs for EUDI compliance?▼

Yes, EUDI high-level requirements mandate that Access CAs register all issued access certificates in Certificate Transparency logs to ensure secure and verifiable issuance processes.

When do Wallet Units need to check SCTs during certificate issuance and presentation?▼

Wallet Units must verify Signed Certificate Timestamps during both certificate issuance and presentation flows to confirm the integrity of access certificates before accepting them for use.

What are the normative requirements for SCT verification in EUDI certificate management?▼

The normative requirements specify SHALL, SHOULD, and MAY obligations for SCT verification, governing how Access CAs log certificates and how Wallet Units validate timestamps to ensure secure certificate management.