Evidence Vault

Proof you can hand to an assessor — with the history intact.

Every control result in AssurIQ rests on evidence: a collector observation, a connector read, an uploaded artifact or a recorded attestation. The Evidence Vault keeps that evidence with its provenance, its integrity hash and its full history, and maps it to every control and framework it supports.

Evidence Vault · AIQ-END-004 · historyAppend-only · nothing overwritten
  1. Aug 04Evidence GapNo evidence on file
    Control created from HIPAA pack mapping
  2. Aug 06PartialCollector · endpoint census
    3 of 41 workstations still on unsupported OS
  3. Aug 19PartialManual upload · lifecycle plan
    Replacement schedule attached, exception requested
  4. Aug 27PassCollector · endpoint census
    All endpoints on supported OS · confidence 94
Provenance
Collector · connector · manual
Integrity
Hashed, timestamped
Maps to
HIPAA · NIST CSF · Insurance
Provenance

Every record says where it came from and how much to trust it.

Collector evidence

Observations from the AssurIQ Collector — topology snapshots, service inventories, configuration reads — timestamped and tied to the collector instance that produced them.

Connector evidence

Identity, cloud, backup, EDR and PSA data pulled through API connectors, recorded with the connector, tenant and time of read.

Manual & attested evidence

Uploaded policies, vendor questionnaires, training records and attestations — clearly labelled as manual, with a reviewer and expiry.

Integrity

Artifacts are hashed at intake. Reports and snapshots reference the hash, so an assessor can confirm nothing changed after the fact.

Append-only history

New evidence never overwrites old. The vault shows the sequence: what was true, when it changed, and what changed it.

Scoped auditor access

Auditor and assessor logins are read-only, scoped to a customer and framework, and time-limited. Access is logged.
Evidence timeline

A control that went Partial and came back tells a better story than one that was always green.

Assessors are rarely impressed by a perfect record. They are reassured by an honest one: the gap was seen, the fix was made, the control was re-verified, and the evidence for every step is here.

  • Per-control timeline of state changes and the evidence behind each
  • Evidence quality drives assurance confidence, not just presence
  • Expiring manual evidence lowers confidence before it lowers the state
How assurance confidence is calculated
Evidence Vault · AIQ-END-004 · historyAppend-only · nothing overwritten
  1. Aug 04Evidence GapNo evidence on file
    Control created from HIPAA pack mapping
  2. Aug 06PartialCollector · endpoint census
    3 of 41 workstations still on unsupported OS
  3. Aug 19PartialManual upload · lifecycle plan
    Replacement schedule attached, exception requested
  4. Aug 27PassCollector · endpoint census
    All endpoints on supported OS · confidence 94
Provenance
Collector · connector · manual
Integrity
Hashed, timestamped
Maps to
HIPAA · NIST CSF · Insurance
Reuse

Collect once. Prove everywhere.

Because evidence attaches to universal controls rather than to framework line items, the same tested-restore record satisfies HIPAA contingency planning, the insurance baseline and the NIST CSF recovery function in one step.

  • One artifact supports one control, mapped to every framework requirement it satisfies
  • Evidence gaps listed per framework so collection is targeted
  • Bulk requests to customers for the manual pieces that remain
Evidence-first compliance
Compliance · Universal controls · Brightpath Dental7 controls · 3 frameworks mapped
ControlState
AIQ-IAM-002
MFA enforced for privileged cloud identities
Fail
AIQ-NET-011
Internet-facing services free of known-exploited CVEs
Fail
AIQ-END-004
Endpoints run supported operating systems
Partial
AIQ-BCK-001
Backups tested for restore within policy window
Evidence Gap
AIQ-NET-003
Guest / IoT traffic segmented from corporate VLANs
Pass
StatesPassPartialFailEvidence GapN/AExceptionEvidence Gap means proof is missing — it is not a failure.
Assessor packs

Snapshots with evidence attached, not just percentages.

Report Studio builds assessor packs directly from the vault, so what leadership approved and what the assessor receives are the same evidence set.

  • Point-in-time freeze of controls, states, confidence and artifacts
  • Shareable with expiring auditor access instead of email attachments
  • What changed since the previous snapshot, in plain language
Report Studio · Executive Assurance Brief · Q3Snapshot · point-in-time, auditor-shareable
Framework readiness (evidence-backed)
FTC Safeguards78% · 6 evidence gaps
NIST CSF 2.064% · 11 evidence gaps
Cyber Insurance Baseline83% · 2 evidence gaps
What changed since last quarter
  • Evidence gaps reduced 14 → 6; backup restore proof still open
  • Privileged MFA moved PARTIAL → PASS and held for 61 days
  • 1 approved exception expires in 41 days
  • Collector coverage 97% of known subnets
Readiness figures describe evidence coverage. They are not a compliance certification.
Data minimization

Evidence of controls, not copies of customer data.

AssurIQ collects configuration state, metadata and proof of safeguards. It is not designed to ingest customer documents, patient records or deal files. Where documentation credentials must be stored, values are encrypted and only decrypted server-side, with every reveal logged.

  • Metadata, configuration and security state over content
  • Row-level tenant isolation on every evidence record
  • Encrypted secret values, server-side reveal, audit log
  • Retention policies per tenant

AssurIQ provides continuous assurance, readiness, evidence, risk and remediation support. It does not certify an organization as compliant, a passing dashboard is not a legal determination, and AssurIQ does not make breach-notification decisions. Framework mappings use original AssurIQ summaries, not reproduced standard text.

Next step

Manage the endpoint. Understand the infrastructure. Prove the controls.

Explore the connected platform, or talk with the AssurIQ team about a controlled Windows RMM pilot. No production data is required to explore the fictional sandbox.