Trusted Architecture

The problem

The documented architecture is not the one that exists. Technical choices are made far from the risks and the governance they should serve.

For organisations subject to NIS2

The technical measures NIS2 expects (access control, encryption, business continuity, supply chain security) are designed into the architecture instead of being bolted on afterwards.

The objective

A target architecture designed from the risks and the governance, which management can decide on with full knowledge: scenarios compared, recommendations prioritised, residual risks accepted.

How it is measured

• The gaps in the existing architecture are recorded for each of ANSSI’s 19 themes.
• Every architecture choice is linked to the risks it treats and the policies it applies.
• Residual gaps are measured for each scenario, then accepted or treated by management.
• The file is approved by the client.

What we do: Organise

“Turn the diagnosis into living governance and a target architecture.”

We design or review the security architecture and tie it to the identified risks and policies: security architecture and security by design, Zero Trust, identity and access management (IAM/PAM), PKI, cloud, decentralised architectures and secure embedded applications. Optionally, the security of industrial systems (OT), following IEC 62443 and ANSSI recommendations.

Key deliverables

Deliverable	Who it is for
Security architecture file covering ANSSI’s 19 themes: gaps and security opinions	CISO, CIO, architects
Compared scenarios: advantages, limits and effort	CISO, CIO, architects
Recommendations per scenario, with priority and effort, and residual gaps	CISO, CIO
Summary for management: the decisions to make and the residual risks	Management

Blooo designs, the client validates.

What Trusted Architecture does not do

No deployment: implementation is Trusted Integration’s job.