Bring every source into one working picture, keep each source’s markings, and let analysts and AI work side by side while people make every call that matters. Assessments meet your tradecraft standard, and each one reaches only those cleared to receive it.
Where the work gets stuck today.
The products and services that do the work.
SEE IT AT WORK
Expert packs carry the analytic standard and the marking scheme your organization follows. Your own rules sit on top, and no later layer can loosen them.
How expert packs workSHARING WITH ALLIES AND PARTNERS
Products carry the markings of the scheme your packs define, and where you connect your own key service, it decides who opens each file, at every open. Files partners send you open under your grant.
Marking packs cover NATO, UK and US classification, CUI and the Traffic Light Protocol. Once your marking pack maps them, export jobs write ADatP-4778.2 bindings and IC-ISM sidecars beside each file.
Releases, exports and downloads can leave wrapped as ZTDF, the Zero Trust Data Format, by your own OpenTDF platform, or protected by Microsoft Purview. Your policy can require it from a marking level up.
Your OpenTDF platform decides each time a file is opened, even after it has left, and is asked again before a report page or an assistant’s answer shows its content. Its access records come back, matched to each file.
ZTDF and Purview files open under your own grant, or wait until you grant it. OpenPGP and S/MIME files open with your keys, signatures are checked, and damaged files are repaired with the loss counted.
Transmittal records and traces can carry an ML-DSA-65 signature beside ECDSA. Connections to the web app, the API, the relay and SFTP use hybrid X25519 and ML-KEM-768 key exchange where the other side supports it.
A version for a wider release list removes what it may not see and is proven to keep every judgment, likelihood and number unchanged. Each copy is numbered, recorded and recallable.
ZTDF wrapping and post-quantum signatures are off until your organization’s policy turns them on. nanoTDF files are recognized and held.
One picture across sources, without losing their rules
People in charge of every judgment and release
Partner versions ready when the product is
Every copy recorded, and recallable
As a managed service in the United States, in your own cloud or data center, disconnected, in a government enclave with smart-card sign-in, or on a forward node at the tactical edge. Classified work runs on your accredited infrastructure. Tell us about your environment and we’ll walk through the options.
Models only receive what your rules allow for their marking, and the model that writes never sees raw rows. Every request is checked before it leaves.
Yes. Analytic standards and marking schemes are expert packs; your experts can read, test and extend them.
Yes. Products leave in the partner’s marking scheme with ADatP-4778.2 bindings and IC-ISM sidecars, and can be wrapped as ZTDF by your own OpenTDF platform so your key service decides every open.
Records and traces can carry ML-DSA-65 signatures beside ECDSA, and connections use hybrid ML-KEM-768 key exchange wherever the other side supports it. Every signature names its algorithm.
Encrypted files open with your keys, passwords or grant, or wait with the reason. Damaged files are repaired automatically and what was lost is counted. Hostile files are held and never parsed.