Solutions

Attest signs documents and records evidence so that anyone can verify it without trusting DataHubz. Signers use a passkey, documents are encrypted in the browser, and every completed record is anchored on Horizen, with zero-knowledge proofs verified on zkVerify.

• Document signing

  Passkey signatures with Face ID or a fingerprint. Signers need no account and no password.

• End-to-end encryption

  Documents are encrypted in the browser before upload. Attest stores only data it cannot read.

• Signed copies that prove themselves

  Each party receives the same sealed copy, with a certificate, an audit trail and an embedded verifier.

• Receipts, certificates and Proof Cards

  Timestamped receipts for any record, and credentials issued as W3C Verifiable Credentials.

• Zero-knowledge proofs

  Prove that a party signed an agreement on a date without revealing the document. Verified on zkVerify.

• Integrations API and SDK

  Platforms register organizations, record events and receive webhooks. The SDK is open source.

Rubro runs authorized penetration tests and security assessments from the legal paperwork to the final report. Scope and authorization are enforced by the platform, and the evidence it produces can be recomputed by an auditor.

• Authorization enforced in code

  Statement of work, rules of engagement and authorization letter come first. No tool runs outside the signed scope or window.

• Client-controlled stop

  The client can halt all testing at once. Resuming requires both parties to sign.

• Findings mapped to controls

  CVSS 3.1 and MITRE ATT&CK, with recommendations mapped to NIST CSF 2.0, NIST 800-53 r5, CIS v8.1 and ISO 27001:2022.

• Protected evidence

  Encrypted, write-once, object-locked storage, with a hash-chained audit log and Merkle inclusion proofs.

• Client portal

  Scope, findings, coverage, retests and deliverables, in English and Spanish.

• Completion certificates

  Issued on Attest, with a zero-knowledge proof that no findings remain open.