11 Saas Data Isolation Evidence Pack

SaaS Data Isolation Evidence Pack Skill

Use When

• Use when proving tenant isolation across identity, application, database, storage, cache, queue, analytics, support, and backup boundaries. Use evidence-pack-builder for generic packaging and DPA/privacy-doc-set for processing obligations.

Do Not Use When

• Do not use for single-tenant or internal-only systems.
• Do not use this skill to fabricate missing project facts, legal conclusions, test results, approvals, or certification claims.

Required Inputs

Capability and permission boundaries

Default to read-only. Read and search access to the supplied artefacts are required. Editing is limited to an explicitly authorised requested draft or project files. Execute validation only when authorised; publishing, signature, certification, production mutation, destructive action, spending, and risk acceptance require explicit authority.

Degraded Mode

When files, tools, network, rendering, fonts, execution, or evidence are unavailable, return the narrowest useful qualified draft or finding set. Name every unavailable check and its consequence; an unassessed check is never a pass. Preserve evidence already gathered and provide the exact next verification step.

Decision Rules

Workflow

1. Confirm the requested artefact, audience, scope, decision owner, and applicable baseline or version. Work read-only by default; source mutation, publication, signature, certification, production change, or risk acceptance requires explicit authority.
2. Inspect every required input and record missing, stale, conflicting, or inaccessible evidence. Stop claims that depend on an unresolved required input.
3. Apply the Decision Rules, then execute the existing Core Instructions below in order; preserve project terminology and trace each material statement to its source.
4. Test the draft against the output acceptance conditions and domain quality standards. If a check cannot run, mark it not assessed and never convert it into a pass.
5. On failure, recover by preserving completed evidence, identifying the narrowest corrective action and owner, and rerunning only the affected checks before handoff.
6. Produce the named artefact and evidence record; publish, sign, certify, mutate production, or accept risk only under explicit authority.

Outputs

Evidence Produced

Quality Standards

• Every claimed isolation mechanism shall have a named evidence artefact (test result, code review, infra config snapshot, audit log).
• Use deterministic acceptance conditions and preserve traceability from source to decision and output.
• Separate facts, inferences, assumptions, and approvals; never present one as another.
• Apply 28-anti-ai-slop during authoring and 29-ai-slop-audit at major checkpoints and release.

Anti-Patterns

• Producing SaaS Data Isolation Evidence Pack from assumptions instead of named project sources. Fix: Cite the source or mark the item unverified.
• Treating a missing or inaccessible check as passed. Fix: Mark it not assessed, state impact, and block dependent claims.
• Using vague gates such as adequate, secure, or user-friendly. Fix: Replace each with an observable criterion, threshold, and evidence source.
• Copying a generic template without product, control, role, version, or jurisdiction detail. Fix: Ground every section in the supplied context and remove unused boilerplate.
• Publishing, signing, certifying, changing production, or accepting risk without authority. Fix: Prepare a draft and route the decision to the accountable owner.
• Listing evidence without provenance or an acceptance result. Fix: Record source, period, integrity check, mapping, and pass/fail/not-assessed status.

Worked Example

Example: if provenance, integrity, period, or control mapping is absent, quarantine the item and record the gap. Record the evidence and result in the validation record; this avoids misleading or tampered evidence.

References

• Generation logic: load when creating the complete artefact.
• Skill notes: consult for local examples and invocation context.
• Repository operating rules: apply the engine's routing, evidence, and release gates.

Overview

Auditors, enterprise procurement, and regulators ask "prove tenants are isolated." This skill produces the pack that answers — for every layer of the architecture — with named, attachable, time-stamped evidence.

Core Instructions

Step 1: Inventory tenancy patterns

For each microservice list its pattern (silo / pool / mixed / pod / VPC-per-tenant) and the layers requiring evidence.

Step 2: Enumerate isolation enforcement per layer

For each layer × pattern combination list the mechanism in place:

Step 3: List test artefacts

Required tests, each producing evidence:

• Negative-path test: request without tenant context → 401/403, audit entry.
• Tampered-context test: forged tenant_id claim → rejected.
• Cross-tenant fuzz test: tenant A query attempts to access tenant B rows → blocked, audit entry.
• Noisy-neighbor test: tenant A saturates → SLO impact on tenant B ≤ NFR threshold.
• Log-access test: tenant A's CSM cannot view tenant B's logs.
• Hard-delete verification: post-delete query returns 0 rows across all stores.

Step 4: Map to control frameworks

Step 5: Assemble the pack

Data_Isolation_Evidence_Pack.md with sections: 1) Scope (services, regions, period), 2) Tenancy Pattern Inventory, 3) Layered Isolation Mechanisms, 4) Evidence Index, 5) Test Results Summary, 6) Control Framework Mapping, 7) Open Gaps & Remediation, 8) Attestation (sign-off).

Attach all artefacts under evidence/.

Step 6: Refresh cadence

State the cadence: every test refreshed at least quarterly; pack republished annually or on major architecture change.

Standards

• SOC 2 (Trust Services Criteria CC6, CC7).
• ISO/IEC 27001 (A.9, A.13, A.18).
• GDPR Art.32, Art.17, Art.20.
• DPPA 2019 (Uganda), POPIA (South Africa).

Resources

• logic.prompt, README.md, references/saas-data-isolation-evidence-pack-template.md.