03 / Target sectors and environments
Omnimesh is being specified for applications where transport-path exposure, concentrated dependencies or disruption could carry material operational consequence. Its initial research and future-evaluation focus is CNI, defence and military.
Initial target sectors
CNI, defence and military define the initial research and future-evaluation focus. Each context still requires its own threat model, integration boundary and evidence threshold.
Initial focus
For organisations examining whether transport-path concentration, observability or disruption risk could affect essential services.
Evaluation requirement
Define the service consequence, threat model and evaluation criteria.
Initial focus
For organisations examining transport behaviour and exposure against a defined assurance requirement.
Evaluation requirement
Define the assurance requirement, system boundary and relevant evidence threshold.
Initial focus
For qualified stakeholders examining communications transport under capable observation or disruption.
Evaluation requirement
Limit discussion to qualified stakeholders and a defined observation or disruption model.
Operating environments
Evaluation must account for what moves, what is controlled, what can fail and what an adversary may be able to observe.
Established dependency
Applications operating within established sites or infrastructure.
Changing endpoints
Applications whose endpoints, locations or connectivity conditions may change.
Constrained connectivity
Applications operating where infrastructure access or available connectivity may be constrained.
Defined threat pressure
Contexts in which capable observation, disruption or dependency exploitation forms part of the threat model, including battlefield-relevant communications settings.
Suitability must be established separately for each application integration, network condition, adversary model, performance requirement and operational constraint.
Applicability boundary
A meaningful evaluation begins only when the application, transport concern, operating conditions and required evidence can be defined.
A sector label alone does not establish technical or operational fit.
The application can support the required integration.
A transport-level threat or resilience concern has been identified.
Network conditions and operational constraints are defined.
Performance, reliability and failure behaviour can be tested.
Security, safety, assurance and procurement requirements are understood.
Evidence supports the proposed level of use.
Stakeholder questions
Senior decision-makers can begin with consequence and maturity. Technical evaluators can continue into system boundaries, assumptions, integration requirements and evidence status.
Senior decision-maker
Material consequence, exposure concentration, evaluation cost and a credible next decision.
CISO or security leader
Threat model, relationship to the current stack, operating implications and the assurance route.
Network or security architect
Placement, ownership, interoperability, failure behaviour, performance and evidence status.
Government or CNI evaluator
Precise maturity, organisational controls, product evidence, limitations and procurement boundaries.
Next step
Begin with a non-sensitive outline of the application environment, transport concern and assurance objective. We will confirm whether it is in scope, what information is needed and the appropriate next step.
UK-developed