YSTECH / Flagship Technology

SMITH

Secure Management System over Insecure Transmission Hubs

SMITH is a security architecture developed for distributed systems operating across communication environments that cannot necessarily be considered inherently trustworthy. Rather than relying on the transmission infrastructure itself as the foundation of security, SMITH moves trust into the architecture governing information, identities and cryptographic relationships.

Core principle

Security should remain dependable even when the communication channel cannot be fully trusted.

02 / The Challenge

What happens when the network carrying sensitive information cannot itself be trusted?

Conventional assumption

Security often inherits trust from the infrastructure.

Conventional architectures frequently depend on secure endpoints, controlled communication paths, trusted intermediaries or stable cryptographic relationships. When part of that infrastructure becomes compromised, unavailable or operationally uncertain, the assumptions supporting the security model may also begin to fail.

Trusted
Network
Trusted
SMITH starting point

Assume the transmission environment may be insecure.

SMITH begins from a stricter operational premise: the communication environment should not need to be intrinsically trusted for the security architecture to remain effective. Security mechanisms are therefore designed around the management of trust, information and cryptographic relationships rather than around confidence in the transport infrastructure itself.

Secure
Untrusted Hub
Secure
The design question

Instead of asking how to make every communication channel trustworthy, SMITH asks how the system can remain secure when some channels cannot be trusted.

03 / Conceptual Architecture

A high-level view of how SMITH relocates trust from the transport layer to the security architecture.

Security Governance Layer
Secure endpoint

Node A

Trusted system component managing protected identities, state and cryptographic relationships.

Secure endpoint

Node B

Operates within the same security logic without needing to trust the underlying transmission hub.

Secure endpoint

Node C

Participates in the architecture through managed security relations rather than transport assumptions.

Untrusted Transport Environment transmission hubs, relays, shared infrastructure or uncertain communication paths

Principle 01

Distributed trust

Trust is managed within the security architecture rather than inherited from the network itself.

Principle 02

Compartmentalisation

Security relationships can remain bounded and structured even when transport conditions vary.

Principle 03

Operational resilience

The architecture is conceived to remain meaningful under degraded, contested or uncertain communication conditions.

Reading the diagram

The diagram is intentionally conceptual. It illustrates the architectural logic of SMITH: secure nodes interact through a governing security layer while the communication environment below is treated as operationally useful, but not inherently trustworthy.

04 / Key Capabilities

Security conceived for distributed and uncertain environments.

Capability / 01

Security independent of transport trust

SMITH is designed around the principle that the communication infrastructure itself should not have to constitute the root of trust. This allows security to be considered separately from the reliability or trustworthiness of the underlying transmission environment.

Capability / 02

Dynamic security relationships

Rather than relying exclusively on static security relationships, SMITH provides an architectural basis for managing cryptographic relationships as system conditions and operational requirements evolve.

Capability / 03

Compartmentalised trust

Security relationships can be structured so that trust does not need to propagate indiscriminately across the complete system. This architectural separation is intended to reduce dependencies between components and limit the consequences of local compromise.

Capability / 04

Resilience under degraded conditions

SMITH is conceived for systems that may operate across contested, disrupted or operationally uncertain communication environments. The objective is to preserve meaningful security properties even when normal infrastructure assumptions cannot be maintained.

Architecture first

SMITH is not simply a new communication protocol. Its value lies in reconsidering where trust is placed, how security relationships are structured, and how those relationships can evolve during operation.

05 / Application Domains

Built for systems operating where communications cannot be taken for granted.

01 / Space

Space systems

Distributed spacecraft, payloads, ground infrastructure and mission networks may depend on communication paths with limited availability, changing topology or constrained trust.

02 / Defence

Defence networks

Contested and heterogeneous communication environments require security architectures capable of operating without assuming that every intermediary or transmission path remains trusted.

SMITH
03 / Infrastructure

Critical infrastructure

Energy, transport, industrial and distributed operational systems increasingly depend on interconnected digital infrastructure with complex and evolving trust boundaries.

04 / Distributed Systems

Distributed architectures

Autonomous platforms, remote assets and decentralised systems can require security models that remain effective across changing connectivity and operational relationships.

Common requirement

Across these domains, the engineering problem is similar: maintain robust security relationships while reducing dependence on the trustworthiness of the communication infrastructure itself.

06 / Technology Development

From security architecture toward operational integration.

Development approach

SMITH is being developed as an engineering architecture, not as an isolated theoretical concept. The development process progressively connects architectural principles with software implementation, controlled validation and integration into representative distributed systems.

Stage / 01

Architecture

Define the trust model, security relationships, system boundaries and operational assumptions that form the basis of the SMITH architecture.

Stage / 02

Prototype

Translate the architectural concepts into software and system-level implementations that allow key behaviours and security mechanisms to be exercised experimentally.

Stage / 03

Validation

Examine system behaviour under representative conditions, including changing connectivity, uncertain infrastructure and defined threat or degradation scenarios.

Stage / 04

Integration

Adapt the architecture to the interfaces, constraints and operational requirements of specific platforms, networks and application environments.

Engineering objective

The objective is not only to demonstrate a security concept, but to establish an architecture that can be progressively engineered, tested and adapted for real operational systems.

07 / Working with SMITH

Different pathways to bring SMITH into operational systems.

Engagement

SMITH can be explored in the context of specific platforms, communication architectures and operational requirements. YSTECH can engage with industrial, institutional and technology partners from early technical assessment through integration and commercialisation discussions.

01 / Integration

Technology Integration

Explore how the SMITH architecture could be incorporated into an existing or emerging system. The process can begin with interface definition, operational constraints and security requirements, followed by adaptation to the target architecture.

02 / Partnership

Strategic Partnership

Work jointly with YSTECH on technology maturation, demonstrators, validation activities or new application environments. Partnerships can combine domain expertise, operational knowledge and technology development around defined use cases.

03 / Commercialisation

Licensing & IP

Organisations interested in incorporating SMITH technology into products, platforms or services can discuss potential licensing and intellectual property frameworks with YSTECH. The appropriate model can be defined according to the intended application and integration pathway.

Start a discussion

Have a system where communications cannot be fully trusted? Talk to YSTECH.