Skip to main content

Introduction

Continuous Assurance for Heterogeneous Networks (CAHN) is a new technology that underpins network-of-networks, with novel identity models and zero-trust security. [1]

CAHN, delivers continuous assurance, by building on some innovative work that has been developed within NIST as part of the trusted network-layer onboarding program [2]

CAHN will develop new architectures working across networks. It will use advanced notions of identity and distributed credentials, combined with dynamic (AI) reasoning to dynamically infer trustworthiness and assurance. We will work with many different use case and endpoints, with use cases that include Digital Secure by Design hardware silicon to protect against memory vulnerabilities developed with ARM and University of Cambridge. [3][4]

Technical documentations​

The technical documentation is broken up into the following sections

  • D1.04 Requirements and use cases: a consolidated list of use cases and requirements that define the functionality and scope of the system, through its interaction with external users and the implied functionality
  • D1.06 Architecture: the technical documents that define how the different parts of the system work with each other
  • D3.01Base software components: in order to integrate wiht different network types, the primary CAHN objective, we need to carefully select the key components and identify the integration points. In this section we create the fine grained inventory.
  • D4.01 Base hardware components: the running network and the functioning software needs hardware components to run on. This section clearly identifies each component, the manufacture, model and any critical refinements needed.

Document status​

These documents are released as part of MS1 of the CAHN project and have been reviewed and approved by our project board.

Currently these documental are confidential. A subset of these document will be released as part of MS2 (CAHN website) and MS3 (CAHN SDK).

We anticipate some continuing changes as the project matures to reflect agile working practices and to incorporate the learnings from the detailed implementation work .