H Hilt

For digital-asset firms

You signed the NYDFS certification.

Hilt is the runtime evidence behind a NYDFS Part 500 certification. You can produce the policy; the evidence behind your signature is thinner. Hilt watches data movement on the signing cluster at the kernel, resolved to a real identity, off the signing path and without ever reading the key.

See the platform How the collector, identity resolution, and response layer fit together. Book a walkthrough See the detection chain in a guided technical session. Why Hilt The gap the rest of the stack structurally cannot cover.

The evidence behind your April 15 signature

You can produce the policy. What is thinner is the evidence that the controls behind your signature actually held while data moved.

The same move arrives from three directions, and the access model works as designed in all three:

  • A paid-off operator. An authorized support operator reads a key store new to them and ships it out. No resignation letter, no exit interview to wait for, only bytes already off the box.
  • A blind signer. Signers approve what they cannot see through an interface that lied between operator and host. No credential stolen, no rule broken, and the chain has no rollback.
  • A compromised job. A popped dependency or stolen SSH key on a job you stood up on purpose, pushing the keystore outbound over a tunnel. You add more of these jobs every quarter.

Why your current stack cannot produce that record

Posture tools show where the keys sit and who could reach them, not that a process just read the key store and shipped bytes over an SSH tunnel: at rest, not in motion. Endpoint DLP watches laptops, mail, and browser uploads, and never sees the signing cluster where the key actually lives, because server egress is never proxied.

Hilt watches the movement at the kernel, off the signing path, metadata only, single-tenant on your own hardware.

The proof runs on your hardware. Bring your kernel and we will bring the teardown.