Purpose and scope
Agree which evidence is needed, where it can be collected and who is permitted to use it.
Security & deployment
Work within your
operating boundaries.
Connected, local and air-gapped environments need different deployment arrangements. We agree the evidence, collection methods and trust boundaries with your team so the SignalFront capability fits the environment it supports.
Start with the trust boundaries.
Bounded collection
Use approved methods and privileges appropriate to the environment. Account for fragile, isolated or restricted systems.
Controlled evidence
Agree access, transfer, retention and handover arrangements before collecting sensitive material.
Connected, local and air-gapped architecture.
Your environment · authorised source boundaries
Existing systemsAuthorised digital sources
SignalFront appliance
Collection and local evidence handling.
Place appliances within the required trust zones. Bind sources, credentials and targets to their authorised appliance.
Outbound HTTPSAppliance initiates
TCP 443
TCP 443
Cloud sources
Cloud services & APIs
The platform connects directly to supported cloud sources.
Collection runs on the platform, within the agreed source permissions and scope.
Direct cloud connectionSource data collected by the platform
SignalFront Platform
Offline evidence intakeFiles, records, inspections & operating knowledge
Shared Reality
Evidence, identity, relationships, provenance and time.
Domain reasoning and service context support separate operational and cyber risk assessments.
Consequence → Governed action → Verification
The platform collects directly from supported cloud sources. Appliances initiate outbound HTTPS connections for collection that requires local access or custody. Appliance management requires no inbound management port or standing reverse tunnel.
Your environment · evidence and reasoning remain local
Existing systemsAuthorised digital sources
SignalFront appliance
Collection and local evidence handling.
Place appliances within the required trust zones. Bind sources, credentials and targets to their authorised appliance.
Local platform & domain capabilities
Offline evidence intakeFiles, records, inspections & operating knowledge
Shared Reality
Evidence, identity, relationships, provenance and time.
Domain reasoning and service context support separate operational and cyber risk assessments.
Consequence → Governed action → Verification
Air-gap boundary
No live platform connection crosses this boundary. Any approved transfer uses controlled, signed and versioned evidence or result packages.
Local and air-gapped architecture retains the same evidence, identity, Shared Reality and domain reasoning semantics. Online sources can be collected inside the local environment. Offline records and human evidence enter through controlled intake within the same boundary.
Deployment architecture. Available sources, functions and deployment profiles are agreed for your environment. Collection method and deployment connectivity are separate choices.
A recommendation and permission to act are separate decisions.
Keep collection authority, assessment responsibility and change authority explicit. A finding can inform a decision without granting permission to modify the environment.
Bring the constraints into the first conversation.
We’ll use them to shape the evidence scope and deployment approach.