The problem
The measures that were decided are not really in place, or nobody can prove that they work.
For organisations subject to NIS2
Under NIS2, declaring measures is not enough: Trusted Integration implements them and produces the evidence that they work, which you can show to the supervisory authority.
The objective
Measures that are really in place, put into service, and the proof that they work.
How it is measured
- Every deployment goes through security acceptance testing, recorded in signed minutes.
- Every migration has its cutover minutes and a planned rollback.
- The integration file gathers the evidence that the measures work.
- Run: Blooo leads the first measurement cycle, then hands over to the client or its provider.
What we do: Orchestrate
“Drive compliance and implementation through to proof.”
- Migrate: run the migration paths (cloud, legacy, PKI).
- Administer, at go-live only: initial configuration, roles, access, hardening.
- Deploy the measures and solutions the client has chosen.
- Integrate security into the information system and projects (DevSecOps).
Vendor neutrality: no resale, no commission. Blooo implements the solution the client has chosen.
Key deliverables
| Deliverable |
Who it is for |
| Migration plan, with cutover, rollback and sign-off |
CIO, operations teams |
| Go-live and handover file: security acceptance, operating documentation, skills transfer |
Operations teams, run provider |
| Deployment and security acceptance report |
CISO, CIO |
| Integration file and proof of operation |
CISO, auditors |
What Trusted Integration does not do
No run: no long-term operations, no maintenance in operational or security condition, no managed services. Blooo stops at go-live and hands over to the client or its provider.
The O³ method and the proof loop in detail