The emitter proof: who vouched for each record
An authentic Provantix export proves the export is what Provantix issued. It does not, on its own, prove that your emitter ever said any given record, because Provantix could in principle have written one. The emitter proof closes that gap. Each batch your emitter sends carries a seal: your emitter's own signature over the hash of every record in the batch. An auditor can check the seals offline and see that the emitter itself vouched for exactly these records.
The proof is separate from the question did Provantix issue this export? and answers a different one: did the emitter say it? Both are worth checking, and neither replaces the other.
What a seal is
A seal is a short statement your emitter signs with the same key it already uses for batches: the batch number, when the batch was made, how many records it holds, and the hash of each record in order. It holds no personal data, only hashes. Because a record's hash never contained a value that is later erased, the seal still verifies after a person's data is erased, and an erasure changes nothing the emitter signed.
Sealing is on by default from SDK 0.2.0. Nothing in your code changes.
What it proves, and what it doesn't
Proves, where the seal verifies: that the emitter, holding the key named in the export, vouched for each of these records at their place in the batch. A record Provantix edited no longer matches the hash the emitter sealed, and the verifier says so even when every other check passes and the export is genuinely signed by Provantix. A record dropped from a complete export is reported by name.
Does not prove:
- That the emitter reported everything it did. Completeness is a coverage question.
- That the host was uncompromised when it signed. A stolen emitter key can seal fabricated batches until the key is rotated; the key history bounds that window.
- That Provantix did not back-date an export. That is a separate protection, planned after this one.
Whose key vouches for it
The proof is only as independent of Provantix as the key it is checked against. The verifier always says which kind it used:
| Where the key came from | What the proof is worth |
|---|---|
| A key the auditor supplied, obtained from you rather than from Provantix | Independent of Provantix. The strongest result. |
| A customer-supplied key listed in a Provantix-signed export | Provantix attests the key. As strong as the export's signature, but not independent of Provantix. |
| A key listed in an export whose signature is absent or not checked | Proves nothing about who holds the key. |
| A key Provantix generated | Provantix generated the private key and showed it to you once; it is not kept afterwards. But because Provantix made it, a seal under it cannot show that your system, and not Provantix, was the one signing, so the proof is only Provantix's own attestation. Fine for a pilot or trial. |
| A key whose origin the export does not record | Said plainly, never guessed. |
This is why registering an emitter with your own key matters for production. With your own key the private key never leaves your service, and an auditor who gets the public key from you can check the proof without trusting Provantix.
Where an auditor gets the key
In order of strength:
- From you. You hold the public key because you generated the pair. Give your auditor
emitter-public.pemdirectly. This is the only source that makes the check independent of Provantix. - From Setup. Setup → your emitter → Download public keys gives a PEM file with the emitter's current and previous keys. The file says in its header that it comes from Provantix and what that means: it shows Provantix attests the keys, not that the proof is independent.
- From the export itself.
emitters.jsonlists the keys Provantix still holds for each emitter in the export, covered by the export's signature.
Provantix keeps the current and the previous public key of an emitter. A batch sealed under an older key lists the key's fingerprint, and the auditor needs to supply that key. Without it the verifier reports those records as sealed, key not supplied: not checked, not failed.
Checking it
Add the auditor's key file to any of the three verifiers. The command-line verifiers are in the public SDK repository (git clone https://github.com/provantix-tech/agent-sdk), under verifier/.
node verifier/verify-export.mjs <export-folder> --keys provantix-export-keys.json --emitter-keys emitter-public.pem
python3 verifier/python/verify_export.py <export-folder> --emitter-keys emitter-public.pem
On provantix.tech/verify, use Check the emitter's own seals and choose the key file.
The key file is PEM public keys one after another, or JSON: an array of PEM strings, or an object mapping an emitter id to its key. With the object form, a seal made with any other key for that emitter is a failure. With the other forms a seal is matched to a key by its fingerprint only, so a seal whose fingerprint matches none of your keys falls back to the key in the export and is not reported as independent.
The result is never a bare pass:
emitter proof: 412 of 415 records signed by the emitter's key
3 records are in batches the emitter did not seal (not covered, not failed)
key source: a key supplied by the auditor (independent of Provantix)
It also names records that failed their seal, sealed records missing from a complete export, and sealed records the platform says it refused or skipped at ingest. That last list is a statement by the platform, not signed by the emitter, and the verifier says so and names every index and reason. The Python verifier does not check the Provantix manifest signature, so it never reports a key as attested by Provantix.
Getting your emitters ready
- Upgrade the SDK to 0.2.0 and redeploy. Sealed and unsealed batches are accepted side by side, so you can upgrade one emitter at a time. A batch queued before the upgrade is sealed when the new SDK sends it, with the same records and the same batch number, so nothing queued is lost.
- Register production emitters with your own key. Setup → Register an emitter → Use your own key shows the two
opensslcommands. Keep a copy of the public key for your auditor. - Watch Setup. Each emitter shows its key, where the key came from, what that makes the proof worth, and whether it is sealing.
The deadline
Unsealed batches are accepted until the end of a notice period. Provantix emails your organization's admins the notice, and the date is 90 days from that notice; you do not have to ask for it or track it. Admins are reminded 30 and 7 days before, and told on the day refusal begins. From the date, a batch created without its seal is refused, and that emitter's telemetry pauses until its SDK is upgraded. Batches created before the date still land, and an upgraded SDK seals what it had queued. Pilot and trial sources are exempt. The date is shown on Setup for each emitter that has not moved, and as findings: Sealing deadline, paused telemetry and lost seals.
Limits you should know
- Old keys. Only the current and previous key are kept. See above.
- Emitters that do not seal show their records as not emitter-sealed, never as invalid.
- A hostile platform could list a key of its own. An auditor who relies on keys from the export is trusting Provantix for the key. Checking against the key you gave the auditor is what removes that trust.