NELSE — Rules into realityNELSE — Rules into reality

NELSE Trust Center

Security is part ofthe evidence chain.

NELSE separates legal reasoning from identity, access, infrastructure, evidence and resilience controls. Enterprise claims are scoped to the architecture and evidence available for the actual deployment — not inferred from a logo or a target certification.

Control areas

Identity & least privilege

User identities, service identities and privileges are separated. Access is designed around explicit roles and least privilege.

Fail closed

Critical missing permissions, dependencies or required human review should not silently become an allowed state.

Data boundaries

Business data, evidence, metadata and public verification artefacts are treated according to their role and sensitivity.

Encryption & secrets

Encryption, secret management and key handling are deployment controls; the exact enterprise profile is confirmed for the selected architecture.

Evidence integrity

Version, digest, event and proof references support later verification without treating the UI as the source of truth.

Resilience & replay

Backups, historical artefacts and replay capability are different controls and are tested according to the selected service profile.

Deployment architecture

Hosting, network isolation and regulated-hosting requirements are scoped to the deployment rather than claimed universally.

Human accountability

Legal, professional and risk judgements remain attributed to accountable roles when the process requires them.

Enterprise integration

Fit the trust model to the deployment.

SSO

OIDC / SAML according to the selected enterprise deployment and identity architecture.

Provisioning

SCIM / provisioning requirements are confirmed during enterprise design rather than presumed globally.

Tenant boundaries

Organisation and role separation are part of the access-control design.

Service identities

Machine-to-machine calls use explicit service identity and scoped permissions.

Subprocessors

Relevant subprocessors and contractual data-processing terms are documented for the service scope.

Regulated hosting

HDS or other regulated-hosting requirements are addressed according to the workload and contractual perimeter.

Assurance boundary

No badge without evidence.

NELSE does not present ISO 27001, SOC 2, HDS or another external certification as obtained unless the relevant certificate, organisation, scope and validity can actually be evidenced. Architecture targets, customer requirements and certification trajectories remain distinct from external certification status.

Bring us your case

One real workflow. One explicit perimeter.

Describe the operating problem. We prepare the relevant product, deployment programme and integration path around your actual scope.