Digital identity and attribute providers in the UK now operate under a statutory scheme, and a provider that wants to be on the government register, use the trust mark or receive data from public authorities has to be certified against a published rulebook. Part 2 of the Data (Use and Access) Act 2025 puts the digital verification services (DVS) trust framework, the DVS register, the trust mark and an information gateway on a legal footing. Version 1.0 of the framework was finalised on 9 June 2026. This guide explains who the scheme covers, the rules by role, the timeline and transition from the earlier gamma (0.4) version, what the Act allows the government to do when providers fall short, and how to prepare. It is for security, identity and compliance leads at identity providers, orchestrators, wallet providers and the relying parties that use them. Status checked on 27 October 2026.
Key takeaways
- Statute, framework, register. The Act (sections 27 to 55) creates the framework (s.28), supplementary codes (s.29), the register (s.32), the trust mark (s.50) and a power for public authorities to share data with registered providers (s.45).
- Certification is the gate. Registration requires a valid certificate from an accredited conformity assessment body (s.33); certificates are generally valid for three years with audits in between.
- Version 1.0 replaces gamma over time. Framework 1.0 takes effect when the first body is accredited to certify against it, no earlier than 1 September 2026; gamma (0.4) certificates stop counting 27 months after that.
- Removal, not fines. Part 2 enforces through refusal, removal from the register for up to two years, information notices and injunctions against misuse of the trust mark, rather than monetary penalties.
- Machine and agent use is the next test. Orchestrators, APIs and agents that consume identities and attributes must check register status and carry assurance levels, so non-human integration design is part of compliance.
Scope: who and what is covered
Section 27 defines digital verification services as verification services provided at the request of an individual by means of the internet. The scheme is built around a register: Part 2 governs which services can be registered, what they must do to stay there, and what registration unlocks. Part 2 itself contains no criminal offence for offering an unregistered service, so the practical driver is market access: relying parties, government schemes and immigration checks (s.55 amends immigration legislation so orders can refer to registered persons) can require registered services.
| Role (framework 1.0) | What it does | Core rule set |
|---|---|---|
| Identity Service Provider (IDSP) | Proves and verifies a person's identity | Section 5: map the service to GPG 45 "How to check someone's identity"; share strength, validity, activity history, fraud and verification scores with relying parties; agree target confidence levels |
| Attribute Service Provider (ASP) | Creates, binds and shares attributes such as age or address | Section 6: follow the attributes guidance "How to create, bind and share attributes"; assess and share attribute quality; check the recipient's right to see the attribute |
| Holder Service Provider (HSP) | Stores identities and attributes for the user, for example a wallet or account | Section 7: GPG 44 authenticators, disclosure of protection levels per transaction, account lifecycle and closure rules |
| Orchestration Service Provider (OSP) | Routes requests between relying parties and other DVS | Section 8: confirm orchestrated services are on the register; cache update policy and agreed cache freshness |
| Component Service Provider (CSP) | Provides a part of a GPG 45 or GPG 44 process, such as document validation | Section 9: follow the matching IDSP or authenticator rules and return coded failure modes |
Under section 0.f, a service may hold OSP certification alongside other roles, but component certification cannot be held concurrently with other roles. For the US equivalent of the assurance model see the NIST SP 800-63 Digital Identity Guidelines Guide.
Key obligations
Obligations in the Act
| Section | Provision | What it means for a provider |
|---|---|---|
| s.28, s.31 | Secretary of State publishes the framework after consulting the Information Commission; reviews at least every 12 months | Expect revisions; certificates against older versions can be phased out |
| s.29, s.30 | Supplementary codes; withdrawal takes effect at least 21 days after publication | Sector rules (recorded as supplementary notes, ss.36 and 37) need separate certification |
| s.33 | Registration of an applicant with a valid certificate from an accredited conformity assessment body, a proper application and any fee | Accredited certification is a hard precondition |
| s.34 | Refusal for national security or non-compliance, after notice and representations; reapplication bar up to two years | Probity and ownership matter, not just controls |
| s.39 | Application and continuing registration fees by regulations; unpaid fees recoverable as a civil debt | Budget recurring fees |
| s.40, s.42 | Duty to remove a provider or service if the certificate lapses, services stop, or on request | Let a certificate expire and you leave the register |
| s.41 | Power to remove for non-compliance, failure to answer a s.51 notice, or national security; bar up to two years | Respond to information notices fully and on time |
| s.45 to s.49 | Public authorities may disclose information to a registered person at the individual's request; onward disclosure limits for revenue data, with offences in ss.46 to 48; a code of practice | Gateway data needs strict purpose limitation. Sections 45 to 47 were marked prospective when checked |
| s.50 | Designated trust mark usable only by registered persons for registered services; enforced by injunction | Use the mark only on certified, registered services |
| s.51 | Written information notices to accredited bodies and registered persons, with privilege protections | Keep evidence ready for production |
Rules for all providers in framework 1.0
- Inclusion and accessibility (10.1, 10.2): comply with the Equality Act 2010, submit an inclusion monitoring report at least annually, allow users to retake failed checks where fraud is not suspected, and meet WCAG 2.2 AA or EN 301 549 V3.2.1 for private sector user-facing services.
- User understanding (10.3): confirm and record that users understand how their data is shared; holder services reconfirm when processing or purpose changes, or after 14 months.
- Probity (11.1): no misrepresentation of certification or implied government endorsement; evidence of director suitability, sanctions screening and absence of relevant convictions; declare relevant ICO investigations; consider National Security and Investment Act 2021 obligations.
- People (11.3): vet and train staff, control access to sensitive data, appoint a Senior Responsible Officer and notify OfDIA and the certifying body of material changes within 48 hours.
- Information security (11.5, 11.6): an information management system and an ISMS based on ISO/IEC 27001 or equivalent; Cyber Essentials or Cyber Essentials Plus is recommended but optional. See the ISO 27001 Certification Guide.
- Risk (11.7): a framework based on ISO/IEC 27005 or ISO 31000, a published risk appetite statement, and assessment of what happens if a supplier DVS loses certification.
- Records (11.8): record what the service did to create, manage, share or use an identity or attribute in line with UK GDPR Article 30, with a disposal statement and access logging on records.
- Data protection and fraud (12.3, 12.4): encryption at rest and in transit, tested safeguards, a plan to tell people about a breach; monitoring for impersonation, synthetic identities, account takeover and document fraud across channels.
Role specific rules worth knowing
- Expired documents (5.2): do not use expired documents where in-date ones would do; if expired passports are accepted, only up to 12 months after expiry.
- Dormant identities (7.3.d): an identity unused for 14 months must be rechecked to the same or higher confidence before reuse.
- Account changes (7.3.1): notify users through more than one channel and authenticate the user before changing contact details, a direct control against account takeover.
- Account closure (7.3.b): close accounts on user request, evidenced fraud or death, with limited estate exceptions.
Timeline and current status
| Date | Event | Source |
|---|---|---|
| 2025 | Data (Use and Access) Act 2025 (c. 18) receives Royal Assent; ss.39, 52 and 55 in force for specified purposes | legislation.gov.uk |
| 1 December 2025 | Most of Part 2 in force (S.I. 2025/1213) | legislation.gov.uk |
| 3 March 2026 | Framework 1.0 pre-release published for business readiness | GOV.UK |
| 9 June 2026 | Framework 1.0 final release; gamma (0.4) also listed as current | GOV.UK |
| No earlier than 1 September 2026 | Framework 1.0 takes effect when the first conformity assessment body is accredited against it | Framework 0.a |
| 30 September 2026 | References in ss.28, 29, 31 and 49 updated to the Information Commission (S.I. 2026/386) | legislation.gov.uk |
| 1.0 start + 15 months | Last point for an existing gamma holder to apply for further gamma certification | Framework 0.c |
| 1.0 start + 27 months | Gamma certificates stop counting | Framework 0.d |
The exact 1.0 start date depends on accreditation, so check the GOV.UK collection and the OfDIA register guidance before planning. The government must report on the operation of Part 2 within 12 months of s.28 coming into force (s.53).
Enforcement and penalties
Part 2 does not set fines. Its levers are administrative and civil:
- Refusal (s.34) and removal (s.41): for non-compliance with the framework, failure to comply with an information notice, or national security, each with notice, representations and a possible two year bar.
- Mandatory removal (s.40, s.42 to s.44): when certificates lapse or services stop.
- Trust mark misuse (s.50): enforceable by injunction (interdict in Scotland).
- Revenue data offences (ss.46 to 48): wrongful onward disclosure of HMRC, Welsh Revenue Authority or Revenue Scotland information obtained through the gateway.
- Certificate suspension or revocation: by the conformity assessment body under the framework.
Separately, providers process personal data and remain subject to UK data protection law and the Information Commission, which the framework expects them to declare investigations from.
What it means for AI agents and non-human identities
The framework regulates services for people, but most of the traffic is machine to machine: relying party APIs call orchestrators, orchestrators call identity and attribute services, wallets present credentials to verifiers. Those integrations are where compliance is won or lost.
- Register checks are automated: section 8 requires orchestrators to confirm services are on the register and to keep a cache update policy. Treat the register feed as a trust anchor, monitor its freshness and fail closed when a service drops off.
- Service credentials: client credentials, signing keys and mTLS certificates that let relying parties and components call each other are non-human identities. Inventory, rotate and scope them; see the Machine-to-Machine OAuth (Client Credentials) Guide.
- Assurance must travel: IDSPs and HSPs must disclose GPG 45 scores and GPG 44 protection levels. When an AI agent acts for a user with a verified attribute, the agent's request should carry that assurance, not a bare yes or no.
- Agents are not the individual: s.27 services are provided at an individual's request. An agent initiating checks needs a clear, recorded authorisation from that individual and must not be treated as the holder.
- Synthetic identities and deepfakes: fraud monitoring under 12.4 should include injected media and AI generated documents. See the Deepfake-Resistant Identity Verification Guide.
Compliance steps
- Choose roles. Decide which roles each service will certify for, remembering the CSP concurrency restriction.
- Gap assess against 1.0, not gamma. New certification against gamma is only possible in the two cases in section 0.c, so design to 1.0 now.
- Build the management system evidence. ISMS to ISO/IEC 27001 or equivalent, risk framework to ISO/IEC 27005 or ISO 31000, records policy and disposal statement, SRO appointment.
- Map to GPG 45 and GPG 44. Document how each check or authenticator maps, and how scores are exposed to relying parties.
- Close user facing gaps. Accessibility to WCAG 2.2 AA, retake routes, inclusion monitoring, understanding confirmations.
- Engage an accredited conformity assessment body. Book the assessment early, since 1.0 starts only when bodies are accredited.
- Register. Apply under s.33 with the certificate and fee; then apply for supplementary notes where a code applies.
- Operate. Run the 48 hour material change process, the annual inclusion report, audits during the three year certificate and readiness for s.51 notices.
Decision guidance
| Situation | Recommended path |
|---|---|
| Holding a gamma (0.4) certificate | Plan the uplift to 1.0 well before 27 months from 1.0 start; reapply within 15 months only if a bridging gamma certificate is needed |
| New entrant | Certify directly to 1.0 |
| Relying party (not a provider) | No certification needed; require registered providers in contracts and check register status in code |
| Small component supplier | Certify as CSP only, or operate under a certified provider's scope |
| Large group with many services | Certificates are per named service: maintain a service catalogue mapping service to role, certificate and expiry |
Detection and measurement
- Monitor: register cache age, certificate expiry dates per service, repeated evidence check failures, account recovery and contact detail changes, and API client activity per relying party.
- Metric: days to certificate expiry for every registered service (alert at 180).
- Metric: percentage of material changes notified within 48 hours.
- Metric: retake success rate and pass rates by demographic group from the inclusion report.
- Metric: percentage of service credentials with owner and rotation date.
- Metric: fraud detections per 10,000 checks by type (synthetic, impersonation, document).
Common failure patterns
- Using the trust mark beyond scope: the mark applies only to registered services, and misrepresenting certification breaches 11.1.
- Letting certificates lapse: s.40 removal is a duty, not a discretion.
- Stale register caches: an orchestrator trusting a removed service.
- Weak account change controls: changing a phone number or email without authentication enables takeover. See the Account Takeover Prevention Guide.
- Treating gateway data like any other data: onward disclosure of revenue data can be an offence.
Framework mapping
| Framework 1.0 area | NIST CSF 2.0 | NIST SP 800-53 Rev 5 |
|---|---|---|
| Identity proofing (s.5) | PR.AA-02 | IA-12 |
| Authenticators and holder accounts (s.7) | PR.AA-01, PR.AA-03 | IA-2, IA-5 |
| Staff vetting (11.3) | GV.RR-04 | PS-3 |
| Risk management (11.7) | GV.RM-01 | RA-3 |
| Supplier DVS reliance (11.7) | GV.SC-07 | SR-6 |
| Data protection (12.3) | PR.DS-01, PR.DS-02 | SC-28, SC-8 |
| Audit and certification | ID.IM-01 | CA-2 |
Practitioner checklist
- Confirm the current framework versions and 1.0 start date on GOV.UK.
- Record each service's role, certificate, certifying body and expiry.
- Map checks and authenticators to GPG 45 and GPG 44 and expose scores to relying parties.
- Run an ISO/IEC 27001 based ISMS and an ISO/IEC 27005 or ISO 31000 risk framework.
- Appoint the SRO and the 48 hour material change process.
- Meet WCAG 2.2 AA and publish complaints processes.
- Automate register checks with a cache freshness limit and fail closed.
- Inventory and rotate API credentials and signing keys used between DVS and relying parties.
- Prepare an evidence pack for s.51 information notices.
Standards and references
- legislation.gov.uk: Data (Use and Access) Act 2025, Part 2 Digital verification services
- GOV.UK: UK digital verification services trust framework (1.0)
- GOV.UK: UK digital verification services trust framework 1.0 full text
- Cabinet Office and GDS: GPG 45 How to prove and verify someone's identity
- GOV.UK: UK digital verification services trust framework collection
Related NHI Mgmt Group resources: NIST SP 800-63 Digital Identity Guidelines Guide · Identity Verification Buyer's Guide · NIST SP 800-63A-4 Identity Proofing (IAL) Guide. This guide summarises Part 2 of the Data (Use and Access) Act 2025 and the DVS trust framework 1.0 as checked on 27 October 2026 and is not legal advice.