· MagenTrust Research
Credential-bound continuous assurance: enforceable at runtime, auditable end to end, and anchored to the credential federal regulators just recognized.
Introducing credential-bound continuous assurance: enforceable at runtime, auditable end to end, and anchored to the credential federal regulators just recognized.
On September 9, 2026, FinCEN and the federal banking agencies confirmed that state-issued mobile driver's licenses and other government-issued verifiable digital credentials qualify as government-issued identification under the Customer Identification Program rule. For banks and credit unions, that settles a long-open question about who a customer is at account opening.
But the regulators were equally clear about what the guidance does not settle. Institutions retain responsibility for detecting fraud and maintaining a reasonable belief that the customer is who they claim to be. That obligation runs through the entire relationship, not just the moment a credential is presented.
A credential cannot prove who is acting at minute forty of a session. It cannot tell you whether an autonomous agent has taken over the workflow, or whether the human who unlocked the wallet is the same human authorizing the wire.
That is the gap MAGEN Anchor closes.
When a customer presents an ISO/IEC 18013-5 mDL or other verifiable digital credential at onboarding or login, MAGEN Anchor generates a session anchor: a salted cryptographic commitment to the presentation event. No credential data is copied, no PII is stored, and no biometric data is retained, consistent with MagenTrust's zero-PII architecture. The anchor is a reference, not a record.
From that point forward, every runtime decision (PASS, CHALLENGE, or INTERRUPT) is written as a signed, hash-chained entry in an append-only decision ledger deployed inside your perimeter. Each entry captures the timestamp, active policy version, confidence score band, action context, and outcome, and references the session anchor. Raw behavioral signals remain ephemeral and are never written to the ledger.
Enforcement is deterministic. A consequential action cannot execute without a current PASS bound to a valid anchor. For agentic workflows, MagenMCP serves as the enforcement point: when an LLM agent reaches a sensitive action, the anchor state is evaluated before the action proceeds. Inside a Human Exclusion Zone, the inverted policy (human signal equals INTERRUPT) logs to the same chain, so machine-only execution is provable, not just declared.
Auditors, examiners, and insurers can verify the ledger's signatures against the runtime's key and replay the chain: which credential event opened the session, which policy governed each decision, and which decision preceded each consequential action. Records are structured to map to CIP recordkeeping and BSA retention practices, with no data egress. The ledger never leaves your perimeter.
The mDL gives you a strong, regulator-recognized answer to "who is this customer?" at onboarding. MAGEN Anchor gives you a continuous, examinable answer to "who is acting now?" through the life of the relationship. The two work together; neither replaces the other.
The regulatory direction is clear. Cryptographic, credential-based identity is becoming the trusted primitive for financial services, and institutions are already scoping mDL acceptance into their verification programs.
MAGEN Anchor is not a competitor to that investment. It is the runtime complement: it extends the credential's assurance through the session and produces the evidentiary trail your compliance team needs to demonstrate that continuing obligations were met before every consequential action.
And because MagenTrust coverage is backed through a Lloyd's of London Coverholder, the decision ledger doubles as claims-grade evidence: a signed, tamper-evident record of exactly what the runtime verified and enforced before an incident.
MAGEN Anchor follows MagenTrust's standard rollout path, designed to build confidence before enforcement:
No changes to existing IAM or compliance tooling. No card readers, no second device, no PII, no stored biometrics. The MagenTrust engine runs on Google Cloud and is developed in partnership with the UTSA National Security Collaboration Center. Integrations include Verge Technologies' SentientDB, with public sector and regulated-buyer availability through Carahsoft via SentientDB.
The fastest way to evaluate MAGEN Anchor is a passive dry-run scan against a real workflow: account opening, wire authorization, or an agentic process you are planning to ship.