SafeNetis — Cyber-Physical Security Platform
🇳🇱NL
🇫🇷Français🇬🇧English🇪🇸Español🇮🇹Italiano🇵🇹Português🇩🇪Deutsch🇳🇱Nederlands
Request a demo ↗

TRUST CENTER

Trust begins with what an organization chooses to make explicit.

SafeNetis documents architecture, data handling, maturity and current limitations with the same discipline used to represent operational evidence.

Transparency is not a disclaimer. It is a product principle: never confuse ambition, demonstration and validation.

GUIDING PRINCIPLENever confuse ambition, demonstration and validation.

01 · ARCHITECTURE PRINCIPLES

Engineer trust
into every layer.

Eight principles shape how SafeNetis collects, transforms, connects and presents information.

01

Edge-local

Collection, normalization and processing remain close to the observed environment.

02

Read-only by default

Connectors observe source systems without modifying them.

03

Least privilege

Each capability receives only the access required for its function and scope.

04

Connector isolation

Workers are segmented to limit the impact of failure or unexpected behavior.

05

Immutable logging

Important events are recorded in a chronology designed to preserve integrity.

06

Traceability

Sources, evidence, transformations, transitions and decisions remain connected to their origin.

07

Explainability

Results remain reviewable through the observations and rules that produced them.

08

Human control

Operators qualify situations, run investigations and document decisions.

02 · DATA

Context can move.
Control remains local.

The current architecture prioritizes processing close to sources and limits retention to what serves evidence and operations.

01SOURCESLocal systems
02EDGECollection · normalization
03CONTEXTEvidence · relationships
CLOUD NOT REQUIREDin the current architecture
Local processing preferred

Data is processed at the Edge whenever the use case and architecture allow it.

Referenced secrets

Manifests declare references; they are not intended to embed secrets.

Controlled retention

Retention periods and scope should remain limited, explicit and controllable.

No unnecessary raw retention

Raw payloads are not retained without an identified operational or evidentiary need.

No mandatory cloud transfer

The current architecture does not require data transfer to a cloud service.

03 · MATURITY

Three states.
No ambiguous claims.

Every capability is presented according to the evidence actually available.

STATE 01 · CONTROLLED LAB

Demonstrated in the controlled laboratory.

Executed and observed within documented test conditions.

CONTROLLED EVIDENCE
STATE 02 · VALIDATION

Preparing for hardware validation.

Ready to be tested against defined target hardware and environments.

QUALIFICATION REQUIRED
STATE 03 · HORIZON

Vision or roadmap.

Direction without a claim of availability or completed validation.

DOCUMENTED INTENT

04 · WHAT SAFENETIS DOES NOT CURRENTLY CLAIM

Clarity about limits
protects trust.

These positions establish an honest reading contract between what exists today, what still requires validation and what belongs to the vision.

01 · NOT CURRENTLY CLAIMED

Certification

SafeNetis currently claims no product or organizational certification.

02 · NOT CURRENTLY CLAIMED

Official ONVIF compliance

No official ONVIF compliance is currently claimed.

03 · NOT CURRENTLY CLAIMED

Production validation

Current capabilities are not presented as production validated.

04 · NOT CURRENTLY CLAIMED

Universal detection

No universal detection guarantee is made; coverage depends on sources, access and validation.

05 · NOT CURRENTLY CLAIMED

Active response

SafeNetis does not claim automated active response against observed systems.

06 · NOT CURRENTLY CLAIMED

Every vendor

The platform is not claimed as validated across every manufacturer and device.

07 · NOT CURRENTLY CLAIMED

CloudGateway

No operational CloudGateway is claimed in the current architecture.

A FOUNDATION FOR PROGRESS

Being precise about where we stand is essential to building what comes next.

Every demonstration presents capabilities with their scope, maturity status and remaining validation work.

Request a demo ↗