Null Ventures / PRAE / Fictional example

See where your data goes.

A fictional system, evaluated by the PRAE engine. No real patient records, live cloud account or assessment of your application. About PRAE

Review each connection, the protection it requires, and the evidence that supports it.

Synthetic exerciseisolated-fixturepartial

Captured 2026-11-06T12:00:00Z · snapshot-before
Deployment deployment-before · 5 components · 3 data flows

1 not tested1 gaps6 inconclusive

Exports, logs and backups are unexamined. Dataset routing is owner-declared, not observed payload lineage. Configuration, runtime observations and owner declarations remain separate.

Connections and data journeys

Lines distinguish modeled data flows from other relationships. Red solid lines have a gap; amber dashed lines need evidence. Select any component with a pointer or keyboard.

! Gap– – Evidence neededOther lines: modeled relationship
Evidence needed · data_flow · returns_records · declaredGap · data_flow · returns_records · declaredEvidence needed · data_flow · returns_records · declareddeployment · hosted_on · declaredSynthetic user browserbrowserSynthetic user browserSynthetic HTTPS edgeload balancer! Connected gapSynthetic HTTPS edgeSynthetic PHP serviceapplication! Connected gapSynthetic PHP serviceSynthetic PostgreSQL stdatabaseSynthetic PostgreSQL storeAWS provider groupingproviderAWS provider grouping

Protection requirements

Node, connection and journey requirements with separate evidence states
Requirement and targetEvidence stateAction and verification
Journey authorization survives revocation and asynchronous work

Authorized synthetic patient record read

journey · fixture-team
Not tested

Configuration: inconclusive

Runtime: not_tested

Use synthetic identities to exercise allowed access, another tenant, and membership revoked between enqueue, processing and retrieval.

Evidence and retest

WORKFLOW_PERMISSION_EVIDENCE_REQUIRED

PAIRED_ALLOW_DENY_REVOCATION_TEST_REQUIRED

Preserve the original failure and identify the exact deployment. Retest the selected requirement with current, independently obtained evidence. Retain other unknown and untested paths.

ev-owner
Sensitive connection transport and peer identity

http

connection · fixture-team
Gap

Configuration: fail

Runtime: inconclusive

Review the named connection, termination point and approved peer model. Capture fresh deployment settings and an authorized runtime observation for this exact hop.

Evidence and retest

REQUIRED_TLS_MISSING

TLS_EVIDENCE_MISSING_STALE_OR_SOURCE_ONLY

Preserve the original failure and identify the exact deployment. Retest the selected requirement with current, independently obtained evidence. Retain other unknown and untested paths.

ev-config
Sensitive connection transport and peer identity

https

connection · fixture-team
Evidence needed

Configuration: pass

Runtime: inconclusive

Review the named connection, termination point and approved peer model. Capture fresh deployment settings and an authorized runtime observation for this exact hop.

Evidence and retest

SELECTED_TRANSPORT_AND_PEER_CRITERIA_MET

TLS_EVIDENCE_MISSING_STALE_OR_SOURCE_ONLY

Preserve the original failure and identify the exact deployment. Retest the selected requirement with current, independently obtained evidence. Retain other unknown and untested paths.

ev-config
Sensitive connection transport and peer identity

postgresql

connection · fixture-team
Evidence needed

Configuration: inconclusive

Runtime: inconclusive

Review the named connection, termination point and approved peer model. Capture fresh deployment settings and an authorized runtime observation for this exact hop.

Evidence and retest

TLS_EVIDENCE_MISSING_STALE_OR_SOURCE_ONLY

TLS_EVIDENCE_MISSING_STALE_OR_SOURCE_ONLY

Preserve the original failure and identify the exact deployment. Retest the selected requirement with current, independently obtained evidence. Retain other unknown and untested paths.

ev-config
Dataset recipients are authorized

Authorized synthetic patient record read

journey · fixture-team
Evidence needed

Configuration: inconclusive

Runtime: inconclusive

Review every declared or possible recipient for the selected dataset and journey. Remove the unapproved route or record an independently approved policy change, then test allowed and denied transfers.

Evidence and retest

RECIPIENT_ALLOWLIST_WITHIN_SELECTED_GRAPH

INDEPENDENT_DESTINATION_ENFORCEMENT_REQUIRED

Preserve the original failure and identify the exact deployment. Retest the selected requirement with current, independently obtained evidence. Retain other unknown and untested paths.

ev-owner
Copies have a reviewed retention procedure

Synthetic PostgreSQL store

node · fixture-team
Evidence needed

Configuration: inconclusive

Runtime: inconclusive

Document the retention and deletion procedure for this dataset, including exports, logs, replicas and backups; verify its execution with synthetic data.

Evidence and retest

RETENTION_UNSPECIFIED

PROTECTION_EVIDENCE_MISSING_OR_STALE

Preserve the original failure and identify the exact deployment. Retest the selected requirement with current, independently obtained evidence. Retain other unknown and untested paths.

No supporting observations
Persistent copies have independent protection evidence

Synthetic PostgreSQL store

node · fixture-team
Evidence needed

Configuration: inconclusive

Runtime: inconclusive

Review storage encryption, key access, role permissions, retention and recovery for this exact store. Network encryption does not establish storage protection.

Evidence and retest

PROTECTION_EVIDENCE_MISSING_OR_STALE

PROTECTION_EVIDENCE_MISSING_OR_STALE

Preserve the original failure and identify the exact deployment. Retest the selected requirement with current, independently obtained evidence. Retain other unknown and untested paths.

ev-config
Journey visibility is sufficient for the claimed conclusion

Authorized synthetic patient record read

journey · fixture-team
Evidence needed

Configuration: inconclusive

Runtime: inconclusive

Obtain the missing in-scope metadata and capture windows. Failed or sampled collection cannot establish absence of a route.

Evidence and retest

BOUNDED_OR_INCOMPLETE_VISIBILITY

SAMPLE_IS_NOT_COMPLETE_ACTIVITY

Preserve the original failure and identify the exact deployment. Retest the selected requirement with current, independently obtained evidence. Retain other unknown and untested paths.

ev-owner

Vigilance context

No canonical Vigilance evaluation is linked to this exact snapshot. Vulnerability and supplier applicability are unexamined in this view.

All components and relationships
ComponentKindOwnerObservation
Synthetic user browserbrowserfixture-teampresent
Synthetic HTTPS edgeload_balancerfixture-teampresent
Synthetic PHP serviceapplicationfixture-teampresent
Synthetic PostgreSQL storedatabasefixture-teampresent
AWS provider groupingproviderfixture-teampresent
FromToRelationshipBasis
Synthetic PostgreSQL storeSynthetic PHP servicedata_flowdeclared
Synthetic PHP serviceSynthetic HTTPS edgedata_flowdeclared
Synthetic HTTPS edgeSynthetic user browserdata_flowdeclared
Synthetic PHP serviceAWS provider groupingdeploymentdeclared

Public fictional example. No certification or independent assurance. The viewer cannot apply changes or approve findings.