Skip to content
EMBIby Móholt
EMBISECby Móholt

Operational continuity

Classified records.
Network optional.

Labelled case & records management that keeps working when the link drops — and reconciles when it returns.

Inspect the evidence. Then plug in.

What it is

A sovereign case and records layer for classified work: STANAG 4774 labels and 4778 bindings on every record, a tamper-evident audit chain, and a device-authoritative offline node (EMBISEC-L) for vessels, vehicles and sites. Icelandic and NATO-standard classification profiles run today.

What it plugs into

Secure-exchange and cross-domain products (labelled records in and out) · C2 and situational-awareness tools (the accountable case behind the picture) · intelligence delivered as DCAT / Dataspace Protocol data products · ACP-121 signals filed to bundles.

EVIDENCE PACK · BUILD 2026.09 · ed25519:9f3a…c21eSIGNED
release-manifest.jsonimage digest ✓ · git ✓ · SBOM ✓SIGNATURE VALID
sovereignty-manifest.yamlhosting ISL · custodians: customer · egress declared0 DRIFT
STANAG 4774 / 4778label round-trip · binding verified offlinePASS
declared records41/41 sha-256 fixity · registry gaplessPASS
audit chain1 412 entries re-hashed · prev_hash linksPASS

STATUS · in evaluation with Icelandic public-sector users · not yet accredited · TRL 6 / 5 / 4 (EMBI / EMBISEC / EMBISEC-L) · crypto & cross-domain guards: partner components

Let’s talk

We’re looking for partners and our first customers. We welcome conversations with stakeholders about sovereign, secure case and records management — from control over data and hosting to secure handling, traceability and operational continuity.

Tell us about your needs, explore a partnership or arrange a short demonstration.

Let’s talk →
Download the handout (PDF) ↓
The printed event card, front: the headline and the EMBISEC-L console
Móholt ehf. · Reykjavík, Iceland · Sanitised excerpts, fictional exercise data (NG26).bjarni@moholt.is

How to explain it

The spoken version.

“This is a records system for classified work that assumes the network will fail. Every case, every record, every signal is labelled to STANAG 4774, hashed, and audit-chained on the device itself, so when the link drops the operator keeps registering and the device stays authoritative. When the link returns it reconciles and relays the queue — nothing lost, nothing unlabelled, and an archivist can still find it in seven years. We are in trials, not accredited; we bring the records layer, partners bring the crypto and the guards.”

Is this accredited?

No. TRL 6 on the records core, in trials with Icelandic public-sector users; accreditation is the next step and we are looking for the partner that carries it.

Who does the crypto and cross-domain?

Not us, by design. We integrate with the partner’s guard and HSM and never claim that layer.

Is NG26 real?

No, fictional exercise data; the workflow, the label handling and the chain are real and can be shown on a laptop.

Words to keep consistent

bundle
= case in the EMBISEC-L military profile
record
= declared document
signal
= formal message (ACP-121) filed to a bundle
device-authoritative
= the local device is the system of record while offline
reconcile
= merge and relay the queue when the link returns
REL
= releasability
NR
= NATO RESTRICTED
DTG
= date-time group (141830Z SEP 26)
EMBISEC on the site →EMBISEC-L on the site →