EU Digital Identity Wallet security pre-evaluation.

Building an EU Digital Identity (EUDI) Wallet? Its certification is issued by an accredited body, against attackers with high capability. We find the vulnerabilities and test it that way first, so you reach that evaluation ready.

Under eIDAS 2 (Regulation (EU) 2024/1183), every Member State must offer an EU Digital Identity (EUDI) Wallet, often called the eIDAS wallet. Implementing Regulation (EU) 2024/2981 sets how wallet solutions are certified, with the cybersecurity part anchored to the EUCC scheme and aimed at a high level of assurance.

Wallet solutions must be certified by accredited conformity-assessment bodies designated under the Member State schemes. vulnit is not such a body, so we do not certify your wallet.

What we do is the work before that: a pre-evaluation of the wallet app. We find the vulnerabilities and test it against attackers with high attack potential, the level the certification expects, so you reach the accredited body with them fixed rather than discovered during the evaluation, where they would cost you time.

A wallet holds a person's identity and the credentials they present to the world, so we attack it the way a high-capability attacker would. Depending on your solution, testing can cover:

  • Credential storage and key handling: how attestations and keys are protected, and the secure element, trusted execution or key store the wallet relies on.
  • Issuance and presentation flows: whether an attacker can obtain, clone, replay or forge a credential, or make the wallet present one it should not.
  • Device binding and attestation: whether the wallet instance and its keys can be moved to another device or impersonated.
  • Cryptography and the protections the wallet relies on, such as anti-tampering and runtime checks, tested against the high attack potential the certification uses.
  • Source code and implementation review: at the wallet's high assurance, the evaluation expects design and implementation analysis, so we include a code review alongside the black-box testing.
  1. Call: you tell us about your wallet, its assurance target and your certification date.
  2. Proposal: we set out the agreed scope, what we need from you, the schedule and a fixed price.
  3. Testing: vulnerability analysis and penetration testing against high attack potential, plus a code review at the wallet's assurance level. If we find something critical, we let you know right away.
  4. Report and review: we send you the report and go through it with your engineers.
  5. Retest: once you have fixed the vulnerabilities, we confirm they are resolved, so you reach the accredited body ready.

Technical report

States what we tested: the wallet app on each platform, the build and the flows in scope. Every finding includes evidence, reproduction steps, impact, a CVSS score and vector, CWE and, where they apply, OWASP MASWE references, and how to fix it.

Executive summary

Covers the scope and build tested, the results and the priorities, for management and non-technical readers.

Retest report

If you include the retest, we send a new version of the report with the status of each finding on the new build, before you submit your wallet to the accredited body.

Letter for your customers

On request, at no extra cost, we provide a signed letter with what we tested, the version, the date and the result, for your customers or auditors. After the retest, we update it with the new results.

We have been evaluators

Our team comes from security certification laboratories, with hands-on experience in Common Criteria, the Spanish LINCE scheme and mobile payment standards such as EMVCo SBMP. Wallet certification leans on EUCC, so we know how its vulnerability analysis and high attack potential are applied.

Specialists in mobile security

Our team contributes to OWASP Mobile Application Security, the main reference for testing mobile apps. OWASP recognized this work by naming vulnit an OWASP MAS Advocate.

We help you fix what we find

We explain how to fix each finding and, if you include the retest, check the fixes before you submit your wallet to the accredited body.

Meet the team
What is the EU Digital Identity Wallet?

The EUDI Wallet is a mobile app, introduced by eIDAS 2 (Regulation (EU) 2024/1183), that lets people store and present identity data and electronic attestations across the EU. Wallet solutions have to be certified before they are offered.

Do you certify my wallet?

No. Wallet solutions are certified by accredited conformity-assessment bodies designated under the Member State schemes, with the cybersecurity part anchored to EUCC. We are not such a body. We perform the pre-evaluation so you reach that process ready.

My app only uses a wallet, it is not the wallet. Do I need this?

Probably not. The certification burden falls on the wallet solution itself, not on a relying-party app that uses one. For a relying-party app, a standard mobile application penetration test is the right fit.

Do you need source code?

At the wallet's high assurance, the evaluation expects design and implementation analysis, so we include a source code review alongside the black-box testing. We agree the exact scope with you.

Do you test on physical devices?

When needed. On Android we mainly work with Chameleon, our analysis environment: it gives us deep visibility into what the wallet does in the operating system, and handles root, pinning and anti-instrumentation checks at the OS level by default. On iOS we test on physical devices.

What do you need from us?

The wallet builds, the target assurance and schemes you are certifying against, test accounts and access to the issuance and verification environments in scope, and the source code for the high-assurance review. The proposal sets out the details.

How do you handle confidentiality?

We agree confidentiality terms before you share builds, documentation or source code. We have a standard NDA, but if you prefer to use yours, we are happy to review it.

Tell us about your wallet and your certification date. We reply within one business day to arrange a scoping call.

Talk to our team

A necessary cookie remembers your choices for up to 180 days. Privacy policy.