GDPR Art. 28 sub-processor verification
Replace quarterly DDQ spreadsheets with continuous, signed attestations from each sub-processor. Auto-alert when the chain changes.
KYE Protocol™ is an open identity, attestation and trust standard for AI vendors, data processors and software suppliers. Verifiable controls. Machine-readable evidence. Real-time supply-chain risk.
Stop chasing SIG/CAIQ spreadsheets. Stop hoping vendors update their DPAs. Subscribe to a vendor's posture.
Sister specification to the Compliance-to-Architecture Framework™. Published by ReguNav™.
Procurement sends a 200-question SIG. Security sends a CAIQ. Privacy sends a GDPR Art. 28 questionnaire. Six weeks later, the vendor returns three PDFs that nobody re-reads when their posture changes.
By the time a sub-processor changes, an SLA lapses, or a model is fine-tuned on new data, your DDQ artefacts are stale — and you're the last to know.
KYE Protocol turns this into a subscription, not a snapshot.
Establish the entity's verifiable identifier (DID, domain, organisation number, registry id).
KYE Protocol gives every entity in your AI, data and software supply chain a single verifiable identifier — and a continuously-updated attestation graph hanging off it.
Real workflows that compress today's weeks-long DDQ cycles into automated subscriptions.
Replace quarterly DDQ spreadsheets with continuous, signed attestations from each sub-processor. Auto-alert when the chain changes.
Before deploying a high-risk AI system from a third-party provider, fetch their Annex IV documentation, FRIA, conformity assessment in one machine-readable bundle.
Financial entities maintain the regulator-mandated register automatically — KYE attestations populate the fields the supervisor checks.
Customers stop sending SIG / CAIQ. They subscribe to the vendor's KYE feed; new responses arrive when the vendor's posture changes.
Every AI system carries a signed manifest of its foundation model, training data, fine-tunes, tokenizer, guardrails — discoverable + verifiable at deploy time.
Procurement systems block POs to vendors below a trust-score threshold. Procurement's job becomes policy authoring, not document chasing.
Every attestation type maps to W3C Verifiable Credentials. Hover any chip to see the issuer + verifier roles.
Open spec — Apache-2.0. Patent-grant scope is limited to spec implementations; the commercial KYE registry + verifier engine ships in ReguNav™.
DID + DNS + organisation-number resolution. Backwards-compatible with did:web, did:plc, and existing GLEIF + ENS lookups.
W3C Verifiable Credentials JSON-LD with EIP-1271 / Ed25519 signatures. Replayable + revocable.
JSON-Schema for every attestation type — SOC 2, ISO 27001, GDPR Art. 28, EU AI Act Annex IV, FRIA, AIBOM, and 12 more.
Open scoring formula combining completeness, freshness, attestation strength, and incident decay. Forks free to override.
WebSub-compatible feed of attestation changes. Customers subscribe; vendors push when posture changes.
Public KYE registry at the entity's identifier surface — auditors + customers + regulators all read from the same source.
Apache-2.0. Open repository. Implementations welcome.
KYE Protocol™, v0.1 (2026). Regunav Inc. https://kyeprotocol.com