Team D39 · 2026 MTC Innovation Challenge
Cross-System Digital Trust Infrastructure
Digital trust breaks down at the boundaries between systems, and connectivity providers already sit across those boundaries. Their opportunity is not to replace the security built into email, banking, devices or telecom networks, but to connect those trust signals into a consistent identity, verification and policy layer for high-consequence interactions. It uses verified organizations, local on-device risk detection and role-based controls, and keeps raw communications on customer devices wherever possible.
- 1
Connect trust signals
Bring together identity, authentication, device, network and risk signals from systems the customer already uses, without pretending the provider owns those systems.
- 2
Verify origin + risk
Combine positive identity signals from verified organizations with local, on-device fraud detection and trusted confirmation paths for consequential interactions.
- 3
Apply trust policy
Use one cross-channel policy layer to decide what reaches each user, how it is put in context, and which actions that user may take next.
Why a connectivity provider
The provider's advantage is not privileged access to message content. It is the ability to provide a neutral trust layer across fragmented systems, channels and customer environments.
- Orchestrator, not inspector: connect trust signals from email, identity, device, voice/mobile, banking/SaaS and security partners rather than duplicating their native defenses.
- One customer-facing control plane: common policies, administration, billing, support and escalation across channels that otherwise expose separate trust experiences.
- Protection follows the user: endpoint and app components carry the trust layer onto home Wi-Fi, cellular or another network. Gateways are one deployment surface, not the premise of the product.
- Provider assets that matter: an existing SMB relationship and account identity, managed gateways and devices, connectivity and voice/mobile bundles, distribution, support, and the ability to convene partners.
Make privacy visible, not just a claim
Local inference is an enabling trust feature. Protection can work where sensitive data already lives, while sharing raw communications for model improvement is a separate, explicit choice.
- Privacy controls state exactly what may leave the customer environment, for what purpose, and for how long.
- Each event can show a privacy receipt: what was processed locally, which minimized signals left the device, and what was retained.
- If an admin opens an event whose content was excluded by policy: "Content unavailable. Your organization chose not to collect or share this communication."
- Customers may opt selected events into model training without making content sharing a condition of protection.
Trust console for privileged admins
A portal shows risk events, verified-source status, quarantines, blocked actions, approvals, overrides, trusted-callback outcomes, policy changes and audit history, but never creates a backdoor around the customer's own privacy settings.
Verified organization + identity network
Corporate and institutional partners register authenticated domains, numbers, accounts or other communication origins. The customer sees a familiar verified-source signal: proof of origin, not a guarantee that the content is safe or an endorsement of the sender.
- Customer value: positive authentication answers "is this really my bank / vendor / insurer?" and complements anomaly-based fraud detection.
- Partner value: less impersonation, a smaller fraud-driven support burden and less customer confusion, plus a trusted route for legitimate outreach.
- Business value: enrollment, API/SDK or authenticated-communications fees create a second revenue stream, and each new participant makes the service more useful for customers.
Control plane = delivery + action permissions
The trust layer does more than label communications. It can enforce different treatment based on risk, user role and business policy.
- Delivery and context: deliver normally, attach trust context, warn, quarantine for review, route to a trusted channel, or suppress a high-confidence scam.
- Available actions: disable reply, links, attachments, forwarding, data export or bank-detail changes; require step-up authentication, a second approver, a trusted callback or a timed hold.
- Role examples: a C-suite leader may see almost everything with warnings; an AP clerk may see a suspicious invoice but be unable to change payment details alone; a junior employee may have links and replies disabled on a likely impersonation attempt.
SMB-first wedge + infrastructure flywheel
Start with high-consequence moments where a cross-system trust decision is worth paying for: vendor and payment-detail changes, unusual invoices, executive impersonation, credential and privilege changes, and sensitive-data requests.
- A premium managed-trust subscription or bundle establishes the customer side of the network.
- Verified-organization participation strengthens identity coverage and creates partner-side revenue, making the service more useful as the ecosystem grows.
- Over time, extend the same trust infrastructure to consumers across broadband, mobile, voice, devices and out-of-home interactions.
Mentor pressure-test: questions we're answering
- Q1
What minimum set of cross-system trust signals is enough to prove the infrastructure thesis?
Working on it. See the plan.
- Q2
Which capabilities should the provider own versus obtain from email, identity, banking, OS, security and carrier partners?
Working on it. See the plan.
- Q3
What makes the provider the credible neutral orchestrator rather than Microsoft, an identity vendor or a security platform?
Working on it. See the plan.