Documentation›Air‑gapped
Integrations

Air‑gapped

Evaluate inside an isolated network and carry out only a signed result. The code and the data never leave.

Before you start

  • The CertOne engine (certone command) inside the enclave, provided with your CertOne access.
  • An admin user to register the enclave's public key.
  • A member API key on the connected side, to deliver results.

1. Create and register a source key

Inside the enclave
certone result keygen -o enclave.pem --key-id plant-enclave-01
# writes enclave.pem (private, stays in the enclave) and enclave.pub.pem (public, to register)

In the console, open Developer Hub, then Source keys. Enter the same key id, a name and the content of enclave.pub.pem, then select Register public key. The private key never leaves the enclave.

Use the same --key-id when you register and when you sign. A result signed with an unregistered or revoked key is refused.

2. Evaluate, sign and deliver

Shell
# Inside the enclave
certone check . --registry "$CERTONE_REGISTRY" --fail-on high -o report.json --no-fail
certone result sign report.json --project . --key enclave.pem --key-id plant-enclave-01 \
  -o result.signed.json

# On the connected side, after carrying result.signed.json out
export CERTONE_API_KEY=ck_...
certone-agent deliver result.signed.json --api https://platform.certkor.ai

The signature covers the report, the project's fingerprint, the engine version and the signing time.

What you see

Output
certone-agent: signed result accepted (signature verified): scan 61b0..., verdict FAIL
  • The result appears in the console as run at source, marked as verified by signature.
  • Delivering the same result again is safe; it returns the same scan.
  • deliver exits 0 when the result is accepted and 2 when it is refused.

How it gates

Inside the enclave, certone check exits 3 on a failing verdict. The example uses --no-fail so the result is signed and delivered either way; stop the release on the verdict in your own pipeline.