Acceptance Test Checklist
Falsifiable proof for Steal‑mode evaluations. If any acceptance item fails, pause GTM and fix before proceeding.
Version: 2025-10-30
Execute the 7-day proof
Quick navigation:
1. Scope and Preconditions
- Sites in scope agreed in writing (the pilot: 30 days, up to 3 sites)
- 7‑day export preconditions published to the customer:
- Up to 100 sites in the promise window (phased above 100)
- Agent installed on a host that can reach the EU endpoint over HTTPS (443)
- Outbound egress to EU endpoints permitted (443/TLS)
- Baseline config delivered on Day 0 (site list, IP ranges, credentials, contacts)
- Stakeholders confirmed for sign‑off: CIO/IT Ops lead and DPO
- Residency requirement confirmed: EU‑only hosting
Out of scope: bespoke features, non‑standard protocols (BACnet/Modbus), remote actions, advanced anomaly detection.
2. Test Environment and Roles
- Three test sites chosen, each with a host that can run the agent
- Local maintainer on site to unplug WAN safely
- Video capture tool ready for unplug demo
- Time source synchronized (NTP) on agents and servers
3. Artifacts to Produce (required for pass)
- Evidence export per site with a reproducible hash
- Hash‑chained, tamper‑evident continuity log that shows offline → backfill
- List of enrolled agents including asset history and export lineage
- Reproducible export hash for the evidence pack
- SBOM and signed build attestation
- EU hosting attestation and data‑flow diagram
- DPA and DPIA: being rewritten, not issued yet
4. Step‑by‑Step Evaluation Script
Day 1 — Install and Baseline
- Install agent on 3 sites; verify heartbeat visible in dashboard
- Confirm each agent is enrolled; record agent IDs
- Verify RBAC roles created and audit log recording admin actions
Day 3 — Continuity (Unplug) Test
See the test results
Read our own outage test records: Continuity_Test_Records_v3.pdf.
- Select one site; start screen/video recording of dashboard + physical action
- Yank WAN for 30 minutes (or block egress at firewall); let the host keep running during the outage
- Restore WAN; verify the buffer drains to zero and the outage is recorded in the continuity log with its buffered count
- Repeat unplug for 60 minutes on site B
- Repeat unplug for 120 minutes on site C
Day 5 — Evidence Export
- Generate evidence export (PDF/CSV + lineage); record export timestamp
- Compute reproducible hash and capture it:
# Option Asha256sum export.csv > export.csv.sha256# Option B (OpenSSL)openssl dgst -sha256 export.csv | tee export.csv.sha256
- Re‑export for same time window; verify identical hash
Day 7 — Debrief and Sign‑off
- Walk through artifact checklist with stakeholders
- Capture acceptance decision; if fail, open corrective ticket and schedule retest
5. Acceptance Criteria (must all pass)
Continuity and Backfill
- Offline buffer holds data for each unplug window (30/60/120 minutes)
- Backfill completes: the agent buffer returns to zero after reconnect and the continuity log records the outage with its buffered count
- Ingest lag returns to normal after reconnection
Evidence Export
- Each site has control‑mapped export with lineage fields (who/when/where collected)
- Export hash reproducibility confirmed
Security and Compliance
- RBAC enforced; least‑privilege user demonstrates read‑only view
- Audit log is append‑only and hash‑chained; delete/edit is impossible and tamper‑evident
- SBOM and signed build attestation shared
- EU hosting attestation; DPIA template: being rewritten, not issued yet
- Telemetry fields reviewed; agent ID chosen without personal data
Resource Budgets (Agent)
- CPU, RAM, disk, and egress measured under test load and written down (we publish no ceilings)
- Uninstall path documented and tested on one host
6. Evidence Collection Template
- Video: 3‑minute unplug demo showing offline → backfill and continuity window
- Screenshots: continuity log before/after; host charts during outage
- Files: evidence‑pack.zip, evidence‑pack.zip.sha256, SBOM, attestation.json
- Notes: site IDs, host name, OS, agent version, timestamps, operators involved
7. Sign‑off
Customer
Name and role: _________________________
Date and time: _________________________
Decision: pass fail conditional
Vendor
Name and role: _________________________
Date and time: _________________________
Notes and exceptions
Related Resources
Cross-reference with our known limits and documentation: