vc-wallet-trust

Audit verifier trust controls for credential acceptance workflows.

Updated May 11, 2026
One-click install
npx skills add https://github.com/blamejs/exceptd-skills --skill vc-wallet-trust
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vc-wallet-trust
Source: https://github.com/blamejs/exceptd-skills/tree/main/skills/vc-wallet-trust
Command: npx skills add https://github.com/blamejs/exceptd-skills --skill vc-wallet-trust

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Existing identity and compliance frameworks (NIST 800-53, ISO 27001, NIS2) were designed for traditional network-centric authentication and lack controls for verifiable credential and digital wallet trust verification. This leaves verifiers vulnerable to accepting forged, revoked, or replayed credentials from unanchored issuers, unread status lists, or unbound presentations, creating unaddressed security gaps for EUDI wallet, mobile driving licence, and other VC use cases.

Core Features & Use Cases

  • Threat & Compliance Gap Mapping: Maps verifier trust failures to MITRE ATT&CK TTPs (T1556, T1550, T1606) and CWE weaknesses, and flags insufficient controls in NIST, ISO, NIS2, and UK CAF frameworks.
  • Step-by-Step Verifier Audit Procedure: Provides a repeatable 6-step process to audit every credential acceptance path for missing trust checks, including issuer anchor pinning, revocation enforcement, nonce/audience binding, and algorithm allowlisting.
  • Use Case: For teams rolling out EUDI wallet or ISO 18013-5 mobile driving licence acceptance, this skill identifies exploitable gaps that let attackers bypass credential verification to gain unauthorized access to age-gated services, payments, or identity systems.

Quick Start

Use the vc-wallet-trust skill to audit your digital wallet verifier's trust controls for SD-JWT-VC, OID4VP, and mdoc credential acceptance paths to identify forged, revoked, or replayed credential risks.

Frequently Asked Questions about vc-wallet-trust

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

FAQPage Schema
How do I audit verifiable credential trust controls for an EUDI wallet verifier?

This skill audits verifier trust controls for EUDI wallet and mdoc workflows by mapping security gaps to MITRE ATT&CK TTPs, identifying missing issuer anchor pinning, revocation enforcement, and presentation binding to block forged, revoked, and replayed credential attacks.

What security gaps affect SD-JWT-VC and OID4VP presentation acceptance?

Security gaps in SD-JWT-VC and OID4VP acceptance include missing trust anchor pinning, unread revocation status lists, and unbound presentations, which allow attackers to bypass credential verification and gain unauthorized access to age-gated services or identity systems.

How to map MITRE ATT&CK TTPs to digital wallet verifier vulnerabilities?

Map digital wallet verifier vulnerabilities by correlating trust failures like unanchored issuers and unbound presentations to MITRE ATT&CK TTPs such as T1556, T1550, and T1606, alongside CWE weaknesses, to identify exploitable credential verification bypasses.

Does NIST 800-53 or ISO 27001 cover mobile driving licence verification controls?

Traditional frameworks like NIST 800-53 and ISO 27001 lack specific controls for mobile driving licence trust verification, requiring targeted audits for issuer anchor pinning and revocation enforcement to satisfy identity control compliance requirements.

What is the best way to prevent replayed verifiable credential attacks in mdoc verification?

The best way to prevent replayed verifiable credential attacks in mdoc verification is enforcing nonce and audience presentation binding during the verifier audit procedure to ensure the credential presentation is cryptographically bound to the specific transaction session.

When should I use a dedicated trust verification audit for NIS2 compliance?

You need a dedicated trust verification audit for NIS2 compliance when implementing EUDI wallet or SD-JWT-VC acceptance, as traditional network-centric identity controls fail to address forged, revoked, or replayed credential risks from unanchored issuers.