CISO Procurement & DPA Exemption Pack
Statutory legal justification, regulatory doctrine, and security questionnaire answers demonstrating why ZTDS-compliant architectures are legally exempt from Data Processing Agreements (DPA) under GDPR Article 28.
1. Executive Summary & Core Architectural Principle
100% Client-Side UtilitySoftware conforming to the Zero-Trust Data Sanitization (ZTDS RFC v1.0) specification operates strictly as a pure client-side computational utility. Because conforming software executes de-identification strictly within volatile client RAM before outbound network socket serialization, exactly zero (0.00) bytes of cleartext sensitive data are transmitted to or processed by external vendor servers.
Under established international data protection jurisprudence, software that processes data locally on client hardware without transmitting data to the software vendor is architecturally positioned outside the "data processor" definition when all 4 ZTDS invariants are satisfied. Consequently, ZTDS-conforming architectures provide an architectural basis for DPA/BAA scope exclusion analysis under GDPR Article 28, HIPAA BAA frameworks, and third-party subprocessor risk liability.
2. Statutory Grounds for Exemption & Regulatory Safe Harbors
Article 28 applies only when an external entity processes personal data on behalf of a controller. Under European Data Protection Board (EDPB) Guidelines 07/2020, providers of pure client-side software utilities that never access or receive personal data do NOT qualify as processors. Zero data custody = zero DPA required.
Software conforming to ZTDS executes strictly inside volatile client RAM without cloud egress to vendor servers. Under CJEU Case C-582/14 (Breyer) and EDPB Guidelines 07/2020, the software vendor never obtains custody or means of identification, and is legally excluded from Data Processor status under GDPR Article 28.
When raw PII is ingested into high-dimensional vector databases, data cannot be erased without total re-indexing ($100k+ cost). ZTDS ensures only surrogate tokens enter RAG embeddings, preventing irreversible vector poisoning and guaranteeing automated Right to Erasure compliance.
By deterministically excluding all 18 PHI identifiers locally in volatile RAM before network egress, outbound prompts qualify as de-identified health information under 45 CFR § 164.514(b). The downstream AI model provider never receives PHI, eliminating mandatory BAA requirements.
3. Statutory Regulatory Penalty Ceilings & Risk Mitigation
Model Custom Exposure in CISO Calculator →| Jurisdiction & Regulatory Statute | Statutory Maximum Penalty Ceiling | ZTDS Invariant Safe Harbor Defense |
|---|---|---|
|
EU GDPR Article 83(5) Cross-Border Data Transfer / Processor Breach |
Up to €20,000,000 or 4% of Global Annual Turnover | Raw PII never traverses network boundary (ΔEgress = 0.00 B). No cross-border personal data transfer occurs under Chapter V. |
|
EU Artificial Intelligence Act (Article 99) High-Risk AI Data Governance & Transparency |
Up to €15,000,000 or 3% of Global Annual Turnover | Surrogate tokens satisfy transparency and training data governance requirements without exposing proprietary records to LLM retainment. |
|
US HIPAA HITECH (45 CFR Part 160) Tier 4 Uncorrected Willful Neglect |
$2,067,813 Statutory Annual Cap per Violation Category | Strict Safe Harbor 18-element de-identification executed before egress; outbound prompts contain zero PHI, nullifying breach notification triggers. |
|
US Federal Rule of Evidence 502(b) Attorney-Client Privilege & Work Product |
Subject-Matter Privilege Waiver in Commercial Litigation | Deterministic reversible masking ensures unprivileged third parties (LLM vendors) never receive unmasked work product, preventing inadvertent waiver. |
|
US GLBA & SEC Item 106 Financial Customer NPI & Cyber Disclosures |
Regulatory Enforcement & $7,500/record Statutory Damages | Financial institution NPI and cardholder data isolated to volatile workstation RAM; zero egress to AI inference infrastructure. |
4. Subprocessor Chain Overhead Elimination ($25,000 / Vendor / Year)
By disengaging GDPR Article 28, enterprises eliminate recurring third-party vendor review costs:
Eliminates outside legal counsel hours negotiating custom Data Processing Agreements, Standard Contractual Clauses, and liability indemnities.
Eliminates annual Third-Party Risk Management questionnaires, cloud vendor penetration test reviews, and recurring SIG Lite evaluations.
Removes external cloud proxies from the enterprise SOC 2 Type II subprocessor audit inventory (CC6.7), reducing external auditor billable scope.
5. Architectural Liability Comparison
| Evaluation Dimension | Legacy Cloud DLP / API Proxy | ZTDS Client Engine (RFC v1.0) |
|---|---|---|
| Execution Perimeter | Multi-tenant vendor cloud (AWS/GCP) | Local volatile workstation / VPC RAM |
| Cleartext Socket Egress | Mandatory (raw data travels over WAN) | ΔEgress = 0.00 bytes prior to masking |
| Subprocessor Liability Chain | Creates new subprocessor under GDPR Art. 28 | Zero subprocessors added (utility exemption) |
| Added Network Latency | +350ms to +800ms per LLM prompt | <0.8ms local synchronous execution |
| Token Masking Quality | Destructive static [REDACTED] strings | Bijective contextual surrogate tokens |
| Offline Resilience | Fails completely if vendor cloud is down | 100% operational in Airplane Mode / air-gapped |
6. Enterprise Security Questionnaire Responses (SIG Lite / CAIQ v4 / VSAQ)
Q: Where is customer prompt data hosted or stored?
A: Nowhere. Cleartext data and token maps reside strictly in volatile RAM. No data is ever written to disk, databases, cookies, or cloud storage.
Q: What data egresses to vendor servers during sanitization?
A: Exactly 0.00 bytes. The sanitization engine is self-contained in WebAssembly/TypeScript. No telemetry, analytics, or socket communication exists.
Q: Does the vendor have custody or access to customer encryption keys?
A: No. Masking tables and session keys are derived strictly in client RAM. The vendor maintains zero key escrow and zero remote access.
Q: How does collaborative unmasking work across enterprise teams?
A: Token maps are encrypted client-side using Argon2id and XChaCha20-Poly1305. Central relays act as blind zero-knowledge conduits.
Q: What third-party subprocessors have access to customer data?
A: Zero. Zero subprocessors are involved in data processing, providing an architectural basis for DPA/BAA scope exclusion analysis.
Q: How can our security team verify zero egress independently?
A: Run the 5-Step Airplane Mode protocol in DevTools or execute npx ztds-audit --dir ./src to generate a verifiable cryptographic audit hash.
7. On-Premise Air-Gapped Source Code License Agreement
Customer receives a non-exclusive, non-transferable license to compile, inspect, and execute the ZTDS engine source code strictly within internal, air-gapped networks, microservices, and private cloud VPCs.
Customer may embed the engine into backend microservices, RAG embedding pipelines, internal agentic loops (LangChain, CrewAI), and employee workstations.
Customer is authorized to deploy the engine in 100% disconnected, SCIF, or classified environments with zero telemetry, phone-home checks, or licensing heartbeats required.
License validation operates via offline Ed25519 cryptographic tokens with built-in 60-day operational grace periods and sub-millisecond in-memory verification.
Architectural Comparison: The ZTDS Method vs. Legacy Cloud DLP
Objective architectural evaluation, perimeter boundaries, and latency benchmarks comparing the client-side ZTDS Method against Microsoft Purview, Nightfall AI, BigID, and Cloud API proxies.
Microsoft Purview, Nightfall AI, BigID, AWS Macie, and Google Cloud Sensitive Data Protection (DLP) are registered trademarks of their respective proprietors. Comparative analyses are strictly architectural, evaluating local in-memory execution boundaries against cloud network proxy topologies based on publicly available vendor documentation as of Q3 2026:
- Microsoft Purview: Endpoint & Exchange Information Protection Architecture (docs.microsoft.com/purview)
- Google Cloud DLP: Sensitive Data Protection API latency characteristics and volumetric inspection pricing (cloud.google.com/dlp)
- AWS Macie: S3 Data Security & Automated Discovery topology (aws.amazon.com/macie)
- Nightfall AI: Cloud API proxy webhook & SaaS integration patterns (docs.nightfall.ai)
Microsoft Purview (Information Protection & Data Loss Prevention)
The Architectural Vulnerability
Purview was architected for document classification (Office 365, SharePoint, Exchange) and network gateway egress blocking. It relies on static file inspection or coarse network packet inspection. In dynamic AI applications, data moves as volatile JSON string buffers in streaming API calls. Purview cannot inspect, tokenize, and synchronously de-tokenize dynamic payload streams in real time (<1.2ms) without breaking application performance and model reasoning.
CISO Objection Handling Playbook
[ACCOUNT_TOKEN_1]. The model successfully reasons over the context, and your local client restores the real number in the UI. You achieve 100% compliance without halting business operations."