Records change
Monitor the files, directories and logs that matter, instead of attempting to capture everything indiscriminately.
Security teams can detect incidents. CERTIHASH preserves evidence. Every observation is cryptographically chained, signed by the host, and anchored to a public blockchain so the record can still be trusted months later.
$ curl -fsSLO https://app.certihash.live/downloads/certihash-verify.mjs $ curl -fsSLO https://app.certihash.live/downloads/certihash-verify.mjs.sha256 $ shasum -a 256 -c certihash-verify.mjs.sha256 || sha256sum -c certihash-verify.mjs.sha256 certihash-verify.mjs: OK $ node certihash-verify.mjs proof.json --issuer app.certihash.live ✓ EVENT_HASH_MATCHES ✓ EVENT_IN_BATCH_ROOT ✓ AGENT_SIGNATURE_VALID ✓ BATCH_IN_TENANT_ROOT ✓ ROOT_IN_ONCHAIN_OPRETURN ✓ ORG_SIGNATURE_VALID ✓ ORG_KEY_PINNED ✓ ANCHOR_IN_BLOCK anchored in block 967922 at 2026-09-22T20:10:38Z
CERTIHASH records changes to declared files, directories, accounts, startup state, SSH access and logs — then seals the resulting evidence so alteration is visible.
Monitor the files, directories and logs that matter, instead of attempting to capture everything indiscriminately.
Each record is hashed, linked to the one before it, and signed. Delete or alter something later and the chain exposes the break.
Merkle roots are written into Bitcoin transactions, giving the evidence a timestamp and an external point of reference you do not control.
A lightweight agent watches declared system surfaces. Ready-made policies cover ordinary Linux servers.
Each observation is hashed, linked to the prior record, and signed by the host that created it.
Chains are folded into Merkle roots and committed on-chain on the schedule your organisation chooses.
Export a portable proof for a single event: the record, signatures, Merkle path and blockchain anchor.
The verifier does not quietly convert uncertainty into success. A check that cannot run is reported as unable to run. An unpinned key is never counted as verified.
Proofs can be checked offline, against a block-header source you choose, with signing keys resolved independently from the issuer’s own domain.
CERTIHASH seals hashes of byte ranges rather than shipping log contents to a third party. That distinction matters on systems holding data that cannot simply travel.
Firewalls, EDR, SIEM, IAM and intrusion detection all have different jobs. CERTIHASH addresses what happens after: proving what changed, and whether the record itself remained intact.
A proof can be exported as a file and checked later by an auditor, regulator, customer, insurer, investigator or court, without relying on access to your internal console.
Sentinel Node was announced in 2022 as the first of a planned suite of enterprise security applications aligned with the NIST cybersecurity framework, developed with IBM Consulting on software design and development. The platform has since been rebuilt around one enduring principle: evidence should remain believable even when the party presenting it is not trusted.
We are placing a small number of free, time-boxed pilots with organisations that periodically need to demonstrate what changed on their systems — to an auditor, regulator, customer, insurer, investigator or court.
hello@certihash.live