Compliance, with the
evidence attached.

Organization or infrastructure responsibility

Verified in sourceRun records identify selected application activity; they are not an inventory of every asset, data flow or subprocessor.

Your evidenceMaintain system boundaries, data-flow diagrams, processing purposes and an accountable asset inventory.

Basis for this mappingZ06 S01 S03 S06 S08 S09 S10 S11 S12 S14 S15 S16 S18

Organization or infrastructure responsibility

Verified in sourceRuntime policy configuration does not appoint security, privacy or AI-governance officers.

Your evidenceAssign owners, escalation routes and management oversight; appoint privacy roles where required.

Basis for this mappingZ05 S01 S03 S08 S09 S10 S11 S12 S14 S16 S18

Organization or infrastructure responsibility

Verified in sourceAn action’s configured risk label is not an organizational risk assessment.

Your evidenceRecord threats, impact, likelihood, accepted residual risks and the treatment plan.

Basis for this mappingZ05 S01 S03 S07 S08 S09 S10 S11 S12 S14 S16 S18

Organization or infrastructure responsibility

Verified in sourceExecutable policies help apply decisions; policy approval, training and workforce compliance require separate evidence.

Your evidenceKeep approved policies, training records, attendance and periodic reviews.

Basis for this mappingZ05 S01 S03 S08 S09 S10 S11 S12 S14 S16 S18

Organization or infrastructure responsibility

Verified in sourceUsing a model provider or storage adapter does not establish contractual protections.

Your evidenceAssess suppliers and keep the applicable BAA, processing agreement, security terms, subprocessor and exit records.

Basis for this mappingZ07 S01 S04 S09 S10 S11 S12 S14 S15 S16 S18

Organization or infrastructure responsibility

Verified in sourcePersonal-data APIs do not determine whether collection, use or disclosure is lawful.

Your evidenceDocument the applicable basis or permission and issue accurate notices; obtain consent where required.

Basis for this mappingZ03 S04 S06 S15 S16 S17

Integration or configuration needed

Verified in sourceDashboard hooks consume a host-established user. Z8 does not supply an enterprise identity provider or MFA service.

Your evidenceIntegrate identity, MFA where required, session controls and authentication logs.

Basis for this mappingZ04 S01 S03 S07 S09 S10 S11 S14 S16 S17 S19

Integration or configuration needed

Verified in sourceDashboard scope and tool-policy checks provide enforcement points; host resolvers and application endpoints define effective access.

Your evidenceSet narrow roles, enforce authorization on every data/action path and test denied access.

Basis for this mappingZ04 Z05 S01 S03 S07 S08 S09 S10 S11 S12 S14 S16 S17 S19

Integration or configuration needed

Verified in sourceTenant-qualified resources and dashboard app-scope checks support separation; they are not an OS or network isolation boundary.

Your evidenceTest cross-tenant access in your application, storage adapters and identity resolver.

Basis for this mappingZ03 Z04 S01 S03 S07 S09 S10 S11 S14 S16 S19

Integration or configuration needed

Verified in sourceConfigured approval gates can block action execution. The emitting endpoint must verify who is allowed to approve.

Your evidenceEnforce independent approvers, review standing grants and retain approval records.

Basis for this mappingZ05 S01 S08 S10 S11 S12 S18

Integration or configuration needed

Verified in sourceDashboard scope is re-resolved periodically, but a resolver using stale authority cannot revoke access reliably.

Your evidenceConnect a live authority source, revoke credentials and grants, and retain access-review evidence.

Basis for this mappingZ04 S01 S03 S07 S09 S10 S11 S14 S16 S19

Organization or infrastructure responsibility

Verified in sourceApplication scope checks do not govern root users, cloud consoles, storage administrators or emergency access.

Your evidenceReview privileged entitlements, protect break-glass access and record administrative activity.

Basis for this mappingZ04 S01 S03 S09 S10 S11 S14 S19

Integration or configuration needed

Verified in sourceThe writer seals selected signals. The chain must be started, connected and given a coverage policy.

Your evidenceInclude all in-scope actions and access events; test omissions and failure handling. Marco Civil access logs need their own schema.

Basis for this mappingZ01 S01 S03 S07 S08 S09 S10 S11 S12 S14 S16 S17 S19

Built-in capability

Verified in sourceSealed blocks bind their fields and previous hash using SHA-256; verification detects modifications within the checked chain.

Your evidenceProtect the verifier and trusted comparison material. A hash chain alone cannot prevent a privileged attacker rewriting all copies.

Basis for this mappingZ01 S01 S03 S07 S08 S10 S11 S14 S16 S17 S19

Built-in capability

Verified in sourceBlocks carry sequence, event and stream identifiers, causation/correlation identifiers and a timestamp.

Your evidencePopulate actor and business context safely; manage clock synchronization separately. Ordering is per writer.

Basis for this mappingZ01 S01 S03 S08 S10 S11 S12 S14 S19

Built-in capability

Verified in sourceThe proof API demonstrates inclusion of a selected event in the current window’s Merkle root.

Your evidenceRetain a trusted root and define the covered interval. This is one possible integrity-evidence mechanism, not a mandated algorithm.

Basis for this mappingZ01 S01 S03 S08 S10 S11 S14 S19

Built-in capability

Verified in sourceExported bundles can be verified independently of a running Z8 instance; source tests exercise tampered blocks, roots and anchors.

Your evidenceSupply the bundle’s bounds and retained anchors. A current export covers the hot window, not automatically the whole audit period.

Basis for this mappingZ01 S01 S03 S08 S10 S11 S12 S14 S19

Integration or configuration needed

Verified in sourceAn HTTP sink publishes roots; optional HMAC authenticates the request when a secret is supplied.

Your evidenceUse an independently controlled sink, secure transport, monitored delivery and retained receipts. No trusted timestamp certification is implied.

Basis for this mappingZ01 Z02 S01 S03 S08 S10 S11 S14 S19

Integration or configuration needed

Verified in sourceWith mirror configured, blocks are persisted before acceptance and reloaded on startup. Without it, the chain is process state.

Your evidenceConfigure durable storage, redundancy and recovery. Prove retention for the entire required period.

Basis for this mappingZ01 Z02 S01 S03 S08 S10 S11 S14 S17 S19

Integration or configuration needed

Verified in sourceThe file adapter rejects overwrite and makes files read-only; privileged filesystem access can still defeat that boundary.

Your evidenceChoose independently enforced retention/WORM storage where needed and restrict deletion privileges.

Basis for this mappingZ02 S01 S03 S10 S11 S14 S17 S19

Built-in capability

Verified in sourceThe vault API stores mutable personal-data records separately from the compliance chain.

Your evidenceRoute sensitive payloads to the vault and inspect metadata for identifiers. Separation alone is not anonymization.

Basis for this mappingZ03 S01 S04 S07 S11 S15 S16 S17

Built-in capability

Verified in sourceCommitment helpers hash canonical payloads with a random witness held separately.

Your evidenceKeep witnesses and payloads off-chain; assess re-identification through identifiers, backups and other data. No automatic GDPR exemption is claimed.

Basis for this mappingZ03 S01 S07 S11 S15 S16

Integration or configuration needed

Verified in sourceSanitizers and pattern checks exist. The audit PII scanner defaults to email detection; the AI PII guard defaults to report.

Your evidenceConfigure masking/blocking and domain-specific patterns, test bypasses and minimize collection at source.

Basis for this mappingZ03 Z07 S01 S04 S07 S08 S11 S12 S14 S15 S16 S19

Integration or configuration needed

Verified in sourceerase_subject removes the subject’s vault files. It does not erase every application store, backup or provider copy.

Your evidenceVerify identity, assess exceptions and propagate deletion across all relevant systems with recorded outcomes.

Basis for this mappingZ03 S06 S15 S16

Integration or configuration needed

Verified in sourceDecommissioning tombstones the tenant and sweeps configured resources; the result includes per-step errors.

Your evidenceName application-owned event stores, inspect failures and handle the vault, external systems and backups separately.

Basis for this mappingZ03 S01 S06 S11 S15 S16

Integration or configuration needed

Verified in sourceThe cold-store pruner accepts an age limit; the default is never to prune. It must be invoked or scheduled.

Your evidenceSet purpose-specific periods, run and monitor pruning, and cover every copy. Access-log duties do not authorize keeping all personal data forever.

Basis for this mappingZ02 S01 S03 S06 S08 S11 S14 S15 S16 S17 S18

Built-in capability

Verified in sourcePruner.run skips deletion when a hold is active or its state cannot be established; hold changes are durably recorded.

Your evidenceAuthorize holds and releases, define their legal scope and prevent callers bypassing the hold-aware pruning entry point.

Basis for this mappingZ02 S01 S06 S11 S15 S16 S17

Organization or infrastructure responsibility

Verified in sourceAudit exports are not complete individual-access responses or portable copies of all personal data.

Your evidenceBuild verified requests, data retrieval, correction, applicable portability and response tracking across all processors.

Basis for this mappingZ03 S04 S06 S15 S16

Organization or infrastructure responsibility

Verified in sourceAn action policy is not a consent register, consumer opt-out interface or Global Privacy Control implementation.

Your evidenceImplement applicable preferences, withdrawals and sale/sharing opt-outs; enforce them downstream.

Basis for this mappingZ05 S04 S06 S15 S16 S17

Organization or infrastructure responsibility

Verified in sourceAn HTTP anchor adapter does not enforce TLS across the complete application, cluster, data stores and provider network.

Your evidenceConfigure and test TLS, certificate validation and protected internal transport throughout the deployment.

Basis for this mappingZ02 S01 S03 S07 S09 S10 S11 S14 S16 S19

Organization or infrastructure responsibility

Verified in sourceThe reviewed file vault writes data with owner-only permissions; it does not encrypt those files itself.

Your evidenceChoose encrypted storage and backups, protect keys and assess application-level encryption where needed.

Basis for this mappingZ02 Z03 S01 S03 S07 S09 S10 S11 S14 S16 S19

Organization or infrastructure responsibility

Verified in sourceThe reference secret adapter holds credentials in ETS; it is not a KMS, HSM or key lifecycle service.

Your evidenceIntegrate secret management, separation of duties, rotation, revocation and key recovery procedures.

Basis for this mappingZ07 S01 S03 S07 S09 S10 S11 S14 S16 S19

Organization or infrastructure responsibility

Verified in sourceDashboard access rules do not configure firewalls, host hardening, network segmentation or malware protection.

Your evidenceEnforce network boundaries, hardened configurations, endpoint protection and physical safeguards.

Basis for this mappingZ04 S01 S03 S07 S09 S10 S11 S14 S16 S19

Integration or configuration needed

Verified in sourceServed dashboards reject identified development security defaults unless an explicit insecure override is enabled.

Your evidenceControl overrides, configure the host securely and continuously check configuration drift.

Basis for this mappingZ04 S01 S03 S09 S10 S11 S14 S19

Integration or configuration needed

Verified in sourceZ8 publishes a vulnerability-reporting and supported-version policy. This does not establish the customer’s patch status.

Your evidenceInventory deployed versions, scan your stack, triage findings, apply fixes and retain remediation records.

Basis for this mappingZ07 S01 S03 S07 S09 S10 S11 S14 S16 S19

Organization or infrastructure responsibility

Verified in sourceLocal storage adapters do not constrain every model provider, telemetry destination or backup location.

Your evidenceMap all destinations and applicable contractual/transfer safeguards; enforce region and egress choices.

Basis for this mappingZ03 S04 S06 S10 S11 S15 S16 S17 S18

Integration or configuration needed

Verified in sourceChain verification and pruning telemetry provide signals; neither is a staffed detection and response function.

Your evidenceConnect alerts to an owned response queue and demonstrate triage and follow-through.

Basis for this mappingZ01 Z02 S01 S03 S07 S08 S09 S10 S11 S12 S14 S16 S18

Integration or configuration needed

Verified in sourceSelected audit records can support investigation when retained; source review does not prove incident readiness.

Your evidenceExercise a response plan, preserve evidence and document scope, containment and recovery decisions.

Basis for this mappingZ01 S01 S03 S07 S08 S09 S10 S11 S12 S14 S20 S18

Organization or infrastructure responsibility

Verified in sourceAudit capture does not decide reportability or notify a regulator or affected individual.

Your evidenceMaintain jurisdiction-specific triggers, clocks, owners and notification records; assess each incident promptly.

Basis for this mappingZ01 S05 S07 S08 S09 S10 S20

Integration or configuration needed

Verified in sourceDurable mirror rehydration supports audit recovery. A mirror on the same failure domain is not an independent backup.

Your evidenceBack up application data, vaults and configuration; test restoration and reconcile the recovered evidence.

Basis for this mappingZ01 Z02 S01 S03 S07 S09 S10 S11 S14 S16 S19

Organization or infrastructure responsibility

Verified in sourceAudit persistence alone does not establish service recovery time or acceptable data loss.

Your evidenceSet recovery objectives, test disruption scenarios and retain exercise results and corrective actions.

Basis for this mappingZ02 S01 S03 S09 S10 S11 S14 S18

Organization or infrastructure responsibility

Verified in sourceRuntime action labels do not classify a system legally or assess effects on people.

Your evidenceRecord intended use, affected groups, risk classification and the required privacy/AI impact assessments.

Basis for this mappingZ05 S06 S08 S12 S16

Integration or configuration needed

Verified in sourceRuns can pause for input and selected actions can await approval; these mechanisms need application integration.

Your evidenceGive qualified reviewers authority, context and a usable override or stop path; test real intervention.

Basis for this mappingZ05 Z06 S06 S08 S12 S16

Integration or configuration needed

Verified in sourceRun APIs record model labels, turns and tool calls when the application submits them.

Your evidenceCapture model/version and configuration provenance plus the business decision. A transcript does not prove internal model reasoning.

Basis for this mappingZ06 S01 S08 S12

Integration or configuration needed

Verified in sourceTool-policy filtering and ordered guardrails provide configurable enforcement points, including block and mask verdicts.

Your evidenceWire them into every execution path, choose restrictive policies and test unsafe requests and bypasses.

Basis for this mappingZ05 Z07 S01 S08 S11 S12

Integration or configuration needed

Verified in sourceAn opt-in budget plugin can reject requests over a configured spend limit; its default cost cap is unset.

Your evidenceConfigure limits and failure behavior, supply pricing/usage data and assess service-level resource exhaustion separately.

Basis for this mappingZ06 S01 S08 S10 S12

Organization or infrastructure responsibility

Verified in sourceRun history supports investigations but is not evidence of representative testing, fairness or model accuracy.

Your evidenceMaintain evaluation datasets, acceptance criteria, affected-group analysis and monitoring with remediation.

Basis for this mappingZ06 S06 S08 S12 S16

Organization or infrastructure responsibility

Verified in sourceAn agent approval gate does not govern the entire software/model release process.

Your evidenceRetain reviewed changes, tests, approved releases, validation evidence and rollback procedures.

Basis for this mappingZ05 S01 S03 S08 S09 S10 S11 S12 S14 S18

Organization or infrastructure responsibility

Verified in sourceNo independent audit report, certification or deployment assessment was supplied for this review.

Your evidenceCommission the assessment applicable to your scope. SOC 2 is a CPA attestation; ISO certification and payment validation have separate processes.

Basis for this mappingZ01 S01 S02 S03 S08 S09 S10 S11 S12 S14 S18

Integration or configuration needed

Verified in sourceZ8 can retain selected technical evidence with durable storage. A current window export cannot prove sustained operation by itself.

Your evidenceFor Type I, evidence the specified date; for Type II, the specified period. Add access reviews, tickets, exercises and management reviews.

Basis for this mappingZ01 Z02 S01 S02 S03 S08 S09 S10 S11 S12 S14 S18