Skip to Content
THE FOUNDATION

Trust Core


The computation engine that reconstructs technical reality from configuration evidence.

No endpoint agents. No traffic capture. No manually maintained inventories as source of truth.

Trust Core reads what your infrastructure is configured to do — not what it reports about itself. Configuration sources that already exist in every regulated organization (firewalls, routers, cloud environments, CMDB exports, IPAM registrations, logging platforms) are the inputs.

THE FOUNDATION

Trust Core


The computation engine that reconstructs technical reality from configuration evidence.

No endpoint agents. No traffic capture. No manually maintained inventories as source of truth.

Trust Core reads what your infrastructure is configured to do — not what it reports about itself. Configuration sources that already exist in every regulated organization (firewalls, routers, cloud environments, CMDB exports, IPAM registrations, logging platforms) are the inputs.

HOW IT WORKS

Four computation stages

Trust Core converts configurations into a normalized, dependency-aware model of your enterprise infrastructure.

01

Configuration
Reading

What it does

Reads actual configurations from firewalls, routers, cloud environments, CMDB exports, IPAM, and logging platforms. Not reports — the configurations themselves.

What it prevents

Prevents conclusions from being drawn from what systems report about themselves rather than what they are configured to do.

02

Topology
Reconstruction

What it does

Reconstructs the actual infrastructure topology: which systems exist, which paths between them are possible, which segmentation is active, and where topology deviates from architecture design.

What it prevents

Prevents architectural deviations from remaining invisible between audit cycles.

03

Dependency
Validation

What it does

Validates which systems depend on which others, based on configured routes, firewall rules, and service dependencies. This dependency graph is the input for all further computation.

What it prevents

Prevents dependency drift from remaining undetected until a service fails.

04

Deviation
Detection

What it does

Compares computed reality against three reference points: architecture design, CMDB, and policy frameworks. Discrepancies are computed facts, not alerts.

What it prevents

Prevents deviations from propagating undetected across governance boundaries. Generates remediation items at the €1 detection point.


WHAT COMPUTATION SEES

What Trust Core sees that Observation misses.​


01
Security zone registered, not active
→
Zone exists in inventory but is not enforced in any path. Risk is assumed lower than it is.
02
Firewall policy: direct object instead of group
→
Policy works today but bypasses intended governance and control inheritance.
03
CMDB: no dependency | graph: a path exists
→
A real communication path exists that inventory does not record.
04
Audit control green, evidence absent
→
Control marked complete, but no evidence supports that it is operating as designed.
05
SIEM alert: medium severity | infrastructure: critical blast radius
→
Alert looks minor in isolation but the affected path reaches crown-jewel systems.

​

THE MISSING LAYER

Existing platforms are not inadequate. The reconciliation layer is missing.

SIEM, CMDB, GRC, CSPM and FAIR tooling remain essential inputs. Each sees part of the picture. Trust Core computes what they collectively reveal.

THE MISSING LAYER

Existing platforms are not inadequate. The reconciliation layer is missing.

SIEM, CMDB, GRC, CSPM and FAIR tooling remain essential inputs. Each sees part of the picture. Trust Core computes what they collectively reveal.

PLATFORM GAPS

The gap each platform cannot bridge.

SIEM events icon

SIEM

Events

Design purpose

Correlates security events.

Gap

Paths that have never generated an event are structurally invisible.

CMDB icon

CMDB

Assets & relationships

Design purpose

Registers assets as reported.

Gap

Topology cannot be reconstructed from registration alone.

compliance GRC icon

GRC

Control declarations

Design purpose

Documents control declarations.

Gap

Technical functioning of controls cannot be derived from declarations.

CSPM cloud icon

CSPM

Cloud configuration

Design purpose

Scans cloud configurations.

Gap

Cross-source dependency reconciliation requires an external computation layer.

FAIR tooling icon

FAIR tooling

Financial risk quantification

Design purpose

Models risk from assessment inputs.

Gap

Survey-based risk parameters cannot reflect current configuration state.

Five platforms. Five partial views. One computation layer that makes them coherent.​

Download whitepaper