xCleared: Zero-Trust Classified Info Sharing

Fast Onboarding: 3 Acceleration Levels

Traditional classified information sharing requires manual PKI setup, security officer coordination, and multi-week clearance verification. Xcleared collapses this to 15 seconds with zero-click accept, 90 seconds with one-line CLI, and 10 minutes with deploy buttons.

// .env file
XCLEARED_INVITE_CODE=XCL-abc123

// Auto-accept on first use
import { createClassifiedDataManager } from '@private.me/xcleared';

const manager = createClassifiedDataManager();

const result = await manager.classify(data, {
  classification: 'TS',
  threshold: 2,
  requiredClearances: ['TS', 'TS']
});
//  Invite auto-accepted, data classified

# Install and initialize
npx @private.me/xcleared init

# Output:
#  Clearance DID generated
#  Saved to .env
#  Clearance registry configured
# Ready to classify data

# Classify your first data
npx @private.me/xcleared classify \
  --input ./intel-report.txt \
  --classification TS \
  --threshold 2 \
  --clearances TS,TS

The Problem

Classified information sharing between intelligence agencies and cleared contractors requires trust in individual clearance holders, but insider threats remain the top intelligence community risk.

The DNI’s March 2026 mandate for zero-trust classified sharing reflects decades of insider threat incidents. A single cleared individual with access to classified data can exfiltrate entire programs.

Current compartmentalization relies on access controls that privileged insiders can bypass. Need-to-know is a policy, not a cryptographic guarantee. SCI markings don’t prevent copying.

The Old Way

The PRIVATE.ME Solution

xCleared uses XorIDA threshold authorization where classified documents are split so that K-of-N clearance holders must cooperate to access them. No single individual holds enough data to reconstruct any classified document.

Classified documents are XorIDA-split across independent secure compartments. Reconstruction requires threshold cooperation of K clearance holders, each authenticated via DID identity and authorized via xLock push-auth.

Every reconstruction is HMAC-logged with clearance verification, purpose, and timestamp. The audit trail is itself XorIDA-split to prevent log tampering by insiders.

The New Way

How It Works

xCleared combines XorIDA classified document splitting with DID-authenticated clearance verification and threshold-authorized reconstruction.

Use Cases

Integration

import { ClassifiedVault } from '@private.me/classifiedsplit';

const vault = await ClassifiedVault.create({
  classification: 'TS/SCI',
  compartments: [compA, compB, compC],
  threshold: { k: 2, n: 3 }
});

Security Properties

Benchmarks

Performance characteristics measured on Node.js 22, Apple M2. xCleared enables classified document sharing with sub-10ms cryptographic overhead — network delivery dominates total latency.

Classified Sharing Architecture Comparison

Ship Proofs, Not Source

xCleared generates cryptographic proofs of correct execution without exposing proprietary algorithms. Verify integrity using zero-knowledge proofs — no source code required.

Use Cases

Honest Limitations

Five known limitations documented transparently. xCleared provides cryptographic infrastructure for classified sharing, not a replacement for accredited systems.

Cryptographic Proof of Correctness

This ACI's computations can be cryptographically verified by xProve — so regulators, auditors, and counterparties can confirm results without re-running the computation or accessing the underlying data.

Ready to deploy xCleared?

Talk to Ren, our AI sales engineer, or book a live demo with our team.